pbraren's Posts

Coming up on 9 years now, and this issue is apparently still happening regularly, even on the very latest Workstation 12.1.1. Sure had hoped a smoother fix would become a feature of Workstation.
I fixed it, here's how: 1) Re-download the Technology Preview July 2014: VMware-workstation-full-e.x.p-1946049.exe from here: https://my.vmware.com/group/vmware/get-download?downloadGroup=W... See more...
I fixed it, here's how: 1) Re-download the Technology Preview July 2014: VMware-workstation-full-e.x.p-1946049.exe from here: https://my.vmware.com/group/vmware/get-download?downloadGroup=WKST-TP-JULY-2014 2)  ran the above exe, installer, when prompted (as pictured below), I chose "Remove", and it worked this time, without error 3)  then, without even needing to reboot, I was able to proceed with the upgrade, by simply running VMware-workstation-full-11.0.0-2305329.exe and I'm now on VMware Workstation 11, the GA edition. Glad this worked out, hoping this post will help other beta testers that may run into the same issue. I'll go ahead and mark this question as answered now.
Tried moving the installer to a different local drive (D:), unfortunately, it didn't help, same issue.
Ah, I should elaborate on item #6 above. Uninstall fails with the same message (as the subject line), so I cannot do a simple uninstall of the Technology Preview July 2014 and I don't have ver... See more...
Ah, I should elaborate on item #6 above. Uninstall fails with the same message (as the subject line), so I cannot do a simple uninstall of the Technology Preview July 2014 and I don't have version 10 or any other version also installed.  Here's a screenshot: I put up this post, just in case others have run into this, and even better, if somebody has figured out a more elegant way to upgrade, as I was hoping to avoid a messy manual uninstall: VMware KB: Cleaning up after an incomplete uninstallation on a Windows host and I'm not in a big hurry at the moment to fix this. I realize there are creative old tricks, like reinstalling what you got (if I have a copy of the beta installer still laying about), but again, holding off, hoping this is a known issue, with a workaround.
I'm using Windows 8.1 64 bit, with all the latest Windows Update patches. Anybody else seeing this problem? Found a workaround? It fails with that same message (pictured above) when I ru... See more...
I'm using Windows 8.1 64 bit, with all the latest Windows Update patches. Anybody else seeing this problem? Found a workaround? It fails with that same message (pictured above) when I run the "Software Updates" wizard from within the Technology Preview run the VMware-workstation-full-11.0.0-2305329.exe download, as it begins the install routine, it first goes to uninstall the beta code run the VMware-workstation-full-11.0.0-2305329.exe in Windows 8 or Windows 7 Compatibility mode run the VMware-workstation-full-11.0.0-2305329.exe as Administrator (while logged into to Administrator account) rename (to re-enable debug) C:\Program Files (x86)\VMware\VMware Workstation\vmware-vmx-debug.exe-ORIGINAL back to C:\Program Files (x86)\VMware\VMware Workstation\vmware-vmx-debug.exe as described here TinkerTry IT @ home |  How to disable debug mode in VMware Workstation Technology Preview 2014 for a serious speed boos… when trying to use "Programs and Features", Uninstall/Change If there was an uninstaller to run from C:\Program Files (x86)\VMware\VMware Workstation I'd run it, but there isn't. Any ideas? Interesting that the built-in Windows 8.1 troubleshooting wizard has this to say
As for the July 2014 Tech Preview folks like me, no updates (nor would I expect one), so we just stick with the workaround, until upgrading to Workstation 11 GA version in December. Thank yo... See more...
As for the July 2014 Tech Preview folks like me, no updates (nor would I expect one), so we just stick with the workaround, until upgrading to Workstation 11 GA version in December. Thank you for your attention to this matter!
Making the edit to Workstation's config.ini file seems to fix Player as well.
Thank you Steve78! Your method of adding the line vmmon.disableHostParameters = "TRUE" to the config.ini file worked like a champ, even in the VMware Workstation Technology Preview July 20... See more...
Thank you Steve78! Your method of adding the line vmmon.disableHostParameters = "TRUE" to the config.ini file worked like a champ, even in the VMware Workstation Technology Preview July 2014, described here: http://www.tinkertry.com/microsoft-kb2919355-may-prevent-your-vmware-workstation-or-player-vms-from-starting-heres-the-fix/
Had this circumstance hit me (yet again), this time after a laptop was running a VM, and the laptop wasn't shut down properly. Same fix for this very old issue, even on VMware Workstation 10.  De... See more...
Had this circumstance hit me (yet again), this time after a laptop was running a VM, and the laptop wasn't shut down properly. Same fix for this very old issue, even on VMware Workstation 10.  Decided to record video and write a short post about this simple fix: www.tinkertry.com/how-to-resolve-this-virtual-machine-appears-to-be-in-use-error-in-vmware-workstation
Yes, according to Process Explorer, it is C:\Program Files (x86)\VMware\VMware Workstation\vmware-authd.exe that is spiking the CPUs. Doublechecking services.msc, this matches th... See more...
Yes, according to Process Explorer, it is C:\Program Files (x86)\VMware\VMware Workstation\vmware-authd.exe that is spiking the CPUs. Doublechecking services.msc, this matches the properties of the service, which can be stopped by this command: net stop VMAuthdService net start VMAuthdService but only if running as administrator, so not a viable workaround for me. These laptops that are normally both used day-to-day logged in as user (not administrator), one with a well behaving vmware-authd.exe, the other not.
I did try the gpedit to check "__vmware_user__" suggestion from earlier in this thread, didn't work for me. Neither did uninstall/reboot/reinstall.
Having same issue. I'm on 6.5.1 build 126130, using Vista 64 bit, and every 5 seconds both CPU cores spike to about 70% for about 2 seconds, as it writes yet another vmauthd ID 100 event to th... See more...
Having same issue. I'm on 6.5.1 build 126130, using Vista 64 bit, and every 5 seconds both CPU cores spike to about 70% for about 2 seconds, as it writes yet another vmauthd ID 100 event to the log. This happens when no VMs are running or when VMs are running. The second I stop the VMware Authorization Service, the problem stops. But then I can't start virtual machines, so not a great workaround. I have an entirely identical machine, with an identical OS (cloned with the same base Vista x64/VMware Workstation 6.0), created a year ago. Both were upgraded to 6.5, then to 6.5.1 build 126130, at the same time. But only one of the two has the issue. And the one with the issue boots an identical VM about 20% slower. Read many posts spanning many years, not finding root cause explanation or a fix that has worked for me. Any ideas?
Here's a link to a now-answered, by "oreeh" and "Virtually", closely related thread where ESXi and ESX 3.5 Update 2 are working inside VMware Workstation. See: ESXi3.5 Update 2 Build 1102... See more...
Here's a link to a now-answered, by "oreeh" and "Virtually", closely related thread where ESXi and ESX 3.5 Update 2 are working inside VMware Workstation. See: ESXi3.5 Update 2 Build 110271 (Aug 13) on Workstation 6.5 BETA (build 99530) - problem with powering on VMs "Error You may not power on a virtual machine in a virtual machine" http://communities.vmware.com/message/1037127
Workstation 6.0.3 is now out, will try again soon, but I doubt the behavior will change any. Here's the changes in 6.0.3:
VMware Workstation internal monitor error *** vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897 Please report this problem by selecting menu item Help > VMware on the Web > ... See more...
VMware Workstation internal monitor error *** vcpu-0:ASSERT vmcore/private/physMem_shared.h:38 bugNr=131897 Please report this problem by selecting menu item Help > VMware on the Web > Request Support, or by going to the Web page "http://www.vmware.com/info?id=8&logFile=D%3a%5cDocuments%5cMy%20Virtual%20Machines%5cESX%203%2e5%5cvmware%2elog&coreLocation=D%3a%5cDocuments%5cMy%20Virtual%20Machines%5cESX%203%2e5%5cvmware%2dcore%2egz". Please provide us with the log file (D:\Documents\My Virtual Machines\ESX 3.5\vmware.log) and the core file (D:\Documents\My Virtual Machines\ESX 3.5\vmware-core.gz). If the problem is repeatable, please select 'Run with debugging information' in the Options panel of Virtual Machine Settings. Then reproduce the incident and file it according to the instructions. To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly. We will respond on the basis of your support entitlement. We appreciate your feedback, -- the VMware Workstation team.
I'm running 64 bit Vista, with 4GB of memory and VT enabled on dual cores (Lenovo T61p) fyi.
A while back, a few of us figured out how to get the USB key with 3i beta (given away at VMworld) to run inside VMware Workstation: http://communities.vmware.com/message/754336#754336 Now tha... See more...
A while back, a few of us figured out how to get the USB key with 3i beta (given away at VMworld) to run inside VMware Workstation: http://communities.vmware.com/message/754336#754336 Now that ESX 3.5 is out, I see threads starting up about installing on a SCSI drive inside VMware Workstation: http://communities.vmware.com/thread/116639?tstart=0 I cloned the 3i VM in Workstation, then with that clone, I added a SCSI disk and mounted the iso of the GA level of ESXS 3.5. After accepting is offer to change the disk type, I was able to then install and run ESX 3.5 from within the VM just fine. I've attached a copy of my working vmx file. Only tested for a few minutes, and a few gotchas already: when I downloaded a virtual appliance right from its welcome page, it crashed ESX when the virtual appliance was powered on when I pointed another Workstation VM (XP), one that had VIC 2.0.2 U2, I uninstalled, then pointed browser to bridged-networking IP of ESX 3.5 and installed new VIC 3.5, but it came up with an error at the end. However, it actually seemed to work fine, launched from desktop icon it created. I hope this helps steer others in the right direction, and the speed/responsiveness was far better than I ever had the 3i working fyi. Next steps, make another W2K3SP2 VM and install SQL 2005 and VirtualCenter 2.5 with VUM...also inside VMware Workstation (for portability and training and demonstration purposes at bandwidth constrained customer sites, and for "fun")