I tried to go to 6u1 some months ago and that failed too. Yesterday afternoon I tried to go from 6.0 to 6.0u2 and I continue to get the 1603 error message with the vcsservicemanager.msi installation/update.
I have contacted VMware support, and have an open case for this. But, I was hoping someone here will have encountered this issue and came up with a solid fix/resolution.
For the record, before I tried this time I did take a snapshot, then stopped all the VMware services (except for VMware tools). I logged in with an account with local administrative rights.
The server this is running on is 2012 R2 (a VM). I'm wondering if there's a Windows update that the cause. IF there's an update that's known to conflict with the update installs, I'd love to know. The VM that this is running on was originally running vCenter 5.5. I went through the upgrade when 6.0 came out (waited about a month before installing 6.0).
Attaching vminst.log and vim-vcs-msi.log files. The pkgmgr-comp-msi.log file is too large at 75MB.