New
#11
prophat: change ownership before permissions.
prophat: change ownership before permissions.
To change file ownership you must be logged as member of administrators group.
Regarding help request - it should include more info; workarounds tried, detailed description of failing action and exact text of error msg or screenshot needed.
In the case the "cannot change file ownership" problem persists, I recommend to create another thread as it is not directly related to vmware.
Just FWIW only ...
I, myself, initially skipped/forgot the step: "grant Full Control permissions to Administrators, click OK"
My mistake, of course, but Windows did not allow change permissions then.
I needed to do that step and it worked fine. Maybe you skipped that step as well?
I am not an expert, just my 2cents only...
-
Hi there
@Danielx64
I think VMWare says that V14 isn't compatible with later versions of Windows --- either keep older versions of Windows, run VMWare on a Linux host with latest versions of Windows as a VM or use the FREE VMplayer at 15.5 release level program.
Actually when something doesn't work (I'm not having a go at you BTW) it helps people to possibly find a solution if there is one to state the release / build of the product(s) that are giving trouble including the Host build e.g the Windows release level -- run winver to get that info easily.
Seems fairly clear to me -- software sometimes needs to be updated when the OS is significantly changed. It's annoying at times but that's a fact of life with things I.T (or any technology --- who uses typewriters any more !!.)
Cheers
jimbo
tfwul: The sequence must be Ownership - Permissions - Rename, nothing else works.
Danielx64: Waste of time to argue with... You Know Who :)
This happened to me with V15 and I signed up just so I can download the older file.
However I found if you simply rename this file vmware will start again but may break other things.
I do not recommend any modification to sysmain.sdb as it's part of the Compatibility Assistant and may leave you broken and/or vulnerable. Upgrading to 15.5 solved the issue.
Is this going to be the official MS position, so the older vmware software will "never" work again?