thewul's Posts

Thank you! Matter solved, after the gpedit step. Upto a certain level I am fairly familiar with gpedit, registry settings and whatever-above-newbie-level kind of stuff. I am sure though, if you were to show this kind of 'solutions' to others, probably 9 out of 10 (smartphone addicts) wouldn't know what this is about in the first place   Anyway, as said, matter solved. Everything working fine. Thanks again!

  Thank you very much indeed. Okay, I guess this may mean: 1. Update the VM's (3x Windows 10): Windows - check for updates 2. Remove the snapshots 3. Then copy the entire folder containing the 3 VM's to a new folder 4. Rename that one 5. Install VMware Player and use the VM's from the new folder Wondering whether it may be useful to still keep the Pro version installed.  

Up front: Sorry for the delay. Thank you very much. I truly appreciate your attempt to help, really! I gave it a few tries, nothing happened. A command window flashes but nothing happened, nothing was created or whatever. I'll create a new Windows 10 VM from scratch. Let the matter rest. As for the backup, okay, thanks. Will do that in future.  

Thank you both! Truly appreciated to point me into the right direction. Went over to "HowTo: Recreating a .vmx from the vmware.log file", downloaded the  log2vmx.cmd file. Dragged the oldest available vmware.log file onto it, a new .vmx file was created. Windows started with automatic repair, diagnosing, etc.  After a number of screens it ended up in "Automatic Repair couldn't repair your PC"   Bad luck. Regretfully I will have to create a new VM. See if I could find screenshots of the desktop of what I have installed and all. Actually I have 3 Windows 10 VM's. Two contain an updated Windows 10 x64 only, i.e. no programs installed, clean installs only. Number 1: is a local install, with username: 'UserX', number 2: is one using my Microsoft Outlook-account, but no programs installed. These, I created them once, folder created date says 2015, but actually I hardly ever use them. The 3rd one, with applications, crashed beyond repair. Think I will delete the folder of the 3rd one (with the crashed VM),  and continue with the 2nd one. Indeed, I create snapshots only, trying to leave just the last one in place. After trying/testing a program I restore the snapshot. As for backup: frankly I would not know what exactly to backup... Never created a backup of the VM's. (Within the 'crashed VM' folder there are 7 vmdk files (112GB), within the 2nd VM: 3 vmdk files, 70GB) Am I supposed to backup all of them? As said, no idea. Thanks again!  

@wila  THANK you so much indeed! This was driving me crazy. English not being my native language, I was really puzzled as to how to explain the problem, that's to say, in just a few words, so I could properly search for it. Could not get into the settings of Edge (see attachment), hence I needed to enter the "edge://settings/system" from your screenshot so as to get to the 'Hardware acceleration' thing... Did a re-install/update of VM Tools, checked out the 3D settings of the host-video card, etc. Anyway, thanks again, really super! p.s. VMware Workstation v15.5.x on Windows 10 x64 latest version.

Sorry for the delay. Thank you very much indeed. Indeed, I could get this split traffic to work properly (also whilst using vmware-vmx.exe). Maybe I'll try to install ExpressVPN within a VM some time future, right now, I guess I keep it 'simple' and accept the reduced bandwidth when running VMware using ExpressVPN (using host adapter). Thanks again.

Thank you very much indeed. Actually I tried to figure this out myself, but could not find the relevant article in whatever PDF. Could you give me a hint. Note: I checked out VMware Workstation Pro Documentation Thanks again.  

This is an old thread, I know. FWIW and should other users run into the same problems some time in future, I'd still like to add my comments. Up front there is an important thing to note. I always use the two small batch files on my desktop:  1st one launches VMware Workstation, the 2nd one exits/closes VMware Workstation, There is also a direct shortcut to vmware.exe  on my desktop (I should and will remove that) Today I coincidentally tried to launch VMware Workstation using the direct shortcut (to vmware.exe) and indeed also got this error. ("VMware Workstation failed to start the VMware Authorization Service. You can try manually starting the VMware Authorization Service. If this problem persists, contact VMware support.") So I searched for a solution here and it seems that I should repair/re-install the application... I then noticed I used the wrong button to launch VMware and launched it using the batch file. That went fine! One might consider using batch files. Batch files are located with the VMware Workstation folder and a shortcut to desktop start_vmware.bat sc config VMUSBArbService start= demand net start VMUSBArbService sc config VMAuthdService start= demand net start VMAuthdService sc config VMwareHostd start= demand net start VMwareHostd sc config VMnetDHCP start= demand net start VMnetDHCP sc config "VMware NAT Service" start= demand net start "VMware NAT Service" netsh interface set interface "VMware Network Adapter VMnet1" ENABLED netsh interface set interface "VMware Network Adapter VMnet8" ENABLED d: cd VMware start vmware.exe (note: d: and cd VMware : in my case VMware Workstation is installed in d:\vmware, so adjust this to your own situation) stop_vmware.bat taskkill /F /IM "vmware-tray.exe" net stop VMwareHostd sc config VMwareHostd start= disabled net stop VMUSBArbService sc config VMUSBArbService start= disabled net stop VMAuthdService sc config VMAuthdService start= disabled net stop VMnetDHCP sc config VMnetDHCP start= disabled net stop "VMware NAT Service" sc config "VMware NAT Service" start= disabled netsh interface set interface "VMware Network Adapter VMnet1" DISABLED netsh interface set interface "VMware Network Adapter VMnet8" DISABLED (note: the stop_vmware.bat is to stop all vmware processes) please also see  disable auto-start VM workstation services/processes Set the batch file to run as administrator. This has been working fine for years. Again, just FWIW -