I have Windows 10 x64 build 19041 installed on VMWare Workstation 15.5.1. The build is running fine and the updates download successfully but whenever I go to reboot I get the Windows Startup troubleshooting screen. The Startup repair fails and you are left with the only option to turn off your VM. Once turned off it will reboot back to 19041.
No errors I can find so I am looking for: a) Is anyone else having this issue and b) any troubleshooting tips.
Thank You
I am all of a sudden this morning getting an error "VMware Workstation unrecoverable error: (vcpu-1)" when powering my vmware. Below is the complete error
VMware Workstation unrecoverable error: (vcpu-1). I have attached the error logs. Any help will be appreciated.
Exception 0xc0000006 (disk error while paging) has occurred.
A log file is available in "E:\vmware.log".
You can request support.
To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
You can also run the "vm-support" script in the Workstation folder directly.
Does anybody know any of the details of this software?
I found already the solution with Windows Compatibility Administrator to get VMWare running after Windows 10 1903 update and I also found further tips to get clients running again (disable 3D accelerator etc.) under various forums. The discussion is running more than half a year, but I DID NOT FIND any official comment from vmware on this issue and even worse I didn ot find any option to get support within "My VMWare" (what a joke) ...
So the idea is - support your current customers !!!
Hi Friends,
I want to run 3 servers on a home-based PC, would it bet the best option to use VM Ware. Or should I take another approach?
The premature end "Rolling back action:" is reported in other discussions, and I couldn't find a solution until now.
The steps I've followed are:
a. I updated my Windows 7 (64-bit) with Windows update
b. I uninstalled VC++ 2015-2019 Redistribution packages
c. I uninstalled and removed all previous VMware software, files and registry entries
d. I uninstalled and removed all previous hcmon software, files and registry entries
e. I fixed the hcmon driver issue using the EnableHCMON registry entry fix
f. I install VMware Workstation 15.5 and it fails rolling back the install, with no explicit reasons
Please find attached the corresponding installation log file.
In vmmsi log file, I found:
Action 20:31:36: VM_InstallVmmon. Installing the vmx driver.
MSI (s) (74:C0) [20:31:36:684]: Executing op: CustomActionSchedule(Action=VM_InstallVmmon,ActionType=3073,Source=BinaryData,Target=VMInstallVmmon,CustomActionData=5;Win7)
MSI (s) (74:FC) [20:31:36:684]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIACDC.tmp, Entrypoint: VMInstallVmmon
CustomAction VM_InstallVmmon returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 20:31:36: InstallFinalize. Return value 3.
And this is the pertinent bit from the msi*.log file:
MSI (s) (D8:2C) [08:28:10:538]: Executing op: ActionStart(Name=VM_InstallVmmon,Description=Installing the vmx driver.,)
Action 8:28:10: VM_InstallVmmon. Installing the vmx driver.
MSI (s) (D8:2C) [08:28:10:540]: Executing op: CustomActionSchedule(Action=VM_InstallVmmon,ActionType=3073,Source=BinaryData,Target=VMInstallVmmon,CustomActionData=5;Win7)
MSI (s) (D8:34) [08:28:10:542]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI26E0.tmp, Entrypoint: VMInstallVmmon
CustomAction VM_InstallVmmon returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 8:28:11: InstallFinalize. Return value 3.
I had a previous old version that this installer attempted to update. Then when it rolled back, it removed the NEW version, AND the old version. (DOH!).
I've rebooted and tried again, same response. I've deleted all the previous files that I could find in the usual places, and I found a document talking about doing a manual clean of the registry, and I did THAT as well. Still no go.
Any help appreciated!
Since ESXi is a more or less supported guestOS I never had any problems with unstable virtual SCSI-disks.
Cant they the same about virtual NVME-disks.
Looks like they are less stable than SCSI-disks.
So if you consider testing NVME disks in nested ESXi VMs better use SCSI-disks if you want stable datastores.
I noticed this a couple of times recently that NVME based datastores come and go.
Neither the nested ESXis (6.0, 6.7 and higher) nor Workstation reacted with error messages.
The datastores became unavailable but the t10............. device node disappeared from /dev/disks.
Reactivating them after the datastores disappear did not work from the ESXi side.
But they usuallyy come back when the ESXi gets completely powered off once.
A reboot alone seems to work less often.
I have 3 DVD devices in my system. Whenever I enable them VM the guest OS does not like it and hangs for multiple minutes at a time. I have had to revert the CD/DVD drives to an .iso file on my host to keep the guest from hanging. I don't know how to fix this, but I can replicate this easily if I attempt to allow one of my drives to interact with the guest.
Hi,
Running Windows 10 Enterprise 2019 LTSC guest VM which is Windows 10 version 1809 and have what all other are saying with the incredibly slow boot-up. However, after letting the system get through its 100% CPU usage for about 6-10 minutes, the CPU drops to very low levels and the VM runs fine and fast! No BSOD or other issues. Just the boot-up process with version 1809 of Windows 10 regardless whether it is Enterprise LTSC, Enterprise or Pro.
My VMware is Workstation Pro 15.5.1 build-15018445. Host is Windows 10 Pro (64-bit)
From what I have read, it appears there will be no real answer from either Microsoft or VMware as they need to deal with Microsoft which seems to have "dropped" the issue. Is this about right?
Chris
Hello Community - I have a VM, that has a bridged network connection, that is available via port 80 and 443. I recently moved it to a new host (same Workstation version but newer update) on the same subnet but for some reason the VM cannot be reached via port 80 anymore. It works just with port 443. Anyone know if there are anything in the Workstation settings that may be stopping port 80 from working? Does the firewall settings on the host matter? Thanks!
Hi
I want to install VMware-Workstation-Full-15.5.1-15018445 on debian stable 10 ; but error happened and stop process :
$ sudo ./VMware-Workstation-Full-15.5.1-15018445.x86_64.bundle [sudo] password for ali: Extracting VMware Installer...done. Rolling back VMware Player Setup 15.5.1 Deconfiguring... [# ] 1%
[2020-02-08 13:10:28,108]
[2020-02-08 13:10:28,109]
[2020-02-08 13:10:28,109] Installer running.
[2020-02-08 13:10:28,109] Command Line Arguments:
[2020-02-08 13:10:28,109] ['/tmp/vmis.GxziIs/install/vmware-installer/vmware-installer.py', '--set-setting', 'vmware-installer', 'libconf', '', '--install-component', '/tmp/vmis.GxziIs/install/vmware-installer', '--install-bundle', '/home/ali/Downloads/temp/./VMware-Workstation-Full-15.5.1-15018445.x86_64.bundle', '']
[2020-02-08 13:10:28,167] System installer version is: 3.0.0.15018445
[2020-02-08 13:10:28,167] Running installer version is: 3.0.0.15018445
[2020-02-08 13:10:28,167] Opening database file /etc/vmware-installer/database
[2020-02-08 13:10:29,206] Could not locate installer App Control.
[2020-02-08 13:10:29,378] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,385] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,391] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,398] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,408] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,435] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,443] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,447] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,453] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,460] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,534] Kernel release string 4.19.0-6-amd64
[2020-02-08 13:10:29,539] Found Linux kernel version (4, 19, 0)
[2020-02-08 13:10:29,554] Glibc brand string ldd (Debian GLIBC 2.29-9) 2.29
[2020-02-08 13:10:29,560] Found glibc version (2, 29)
[2020-02-08 13:10:29,654] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,658] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,663] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,669] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,674] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,694] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,699] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,704] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,711] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,723] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,741] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,747] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,752] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,757] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,767] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,785] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,791] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,796] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,803] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,809] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,831] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,838] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,843] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,848] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,858] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,872] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,877] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,882] destination /tmp/tmp618w_jgm/.installer/11.0.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,888] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:29,898] destination /tmp/tmp618w_jgm/.installer/11.0.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,913] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:29,920] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:29,925] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:29,932] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:29,939] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,029] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,035] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,040] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,046] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,053] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,070] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,077] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,089] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,094] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,100] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,168] destination /tmp/tmp618w_jgm/.installer/1.17.0/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,173] destination /tmp/tmp618w_jgm/.installer/1.17.0/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,179] destination /tmp/tmp618w_jgm/.installer/1.17.0/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,191] destination /tmp/tmp618w_jgm/.installer/1.17.0/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,199] destination /tmp/tmp618w_jgm/.installer/1.17.0/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,216] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,223] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,228] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,232] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,236] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,258] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,263] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,268] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,273] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,280] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,310] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/systemType.py already exists, overwriting.
[2020-02-08 13:10:30,316] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/update.py already exists, overwriting.
[2020-02-08 13:10:30,322] destination /tmp/tmp618w_jgm/.installer/15.5.1/__init__.py already exists, overwriting.
[2020-02-08 13:10:30,328] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/versions.py already exists, overwriting.
[2020-02-08 13:10:30,333] destination /tmp/tmp618w_jgm/.installer/15.5.1/include/initscript.py already exists, overwriting.
[2020-02-08 13:10:30,340] destination /tmp/tmp618w_jgm/.installer/15.5.1/vmware-workstation.py already exists, overwriting.
[2020-02-08 13:10:30,411] b'Not running in a virtual machine.\n'
[2020-02-08 13:10:30,411] b''
[2020-02-08 13:10:30,416] Running on a real machine!
[2020-02-08 13:10:30,496] b'1048576\n'
[2020-02-08 13:10:30,497] b''
[2020-02-08 13:10:30,500] Cannot use vmware-app-control to shut down open VMs, defaulting to fallback message.
[2020-02-08 13:10:30,503] Ignored execution error: [Errno 2] No such file or directory: '/etc/init.d/vmware': '/etc/init.d/vmware' when running command: [path('/etc/init.d/vmware'), 'stoppable']
[2020-02-08 13:10:30,522] b''
[2020-02-08 13:10:30,523] b''
[2020-02-08 13:10:30,739] This system has KVM enabled. You cannot run VMs with KVM enabled.
[2020-02-08 13:10:33,162] No release file found...
[2020-02-08 13:10:34,302] destination /usr/lib/vmware/setup/vmware-config already exists, overwriting.
[2020-02-08 13:10:34,328] Integrity Error: Adding file /usr/lib/vmware/setup/vmware-config with mtime 1581154834, fileType 0, and uid 8.
[2020-02-08 13:10:34,328] [vmware-player-setup 15.5.1] Installation failed, rolling back installation.
[2020-02-08 13:10:34,375] Top level exception handler
Traceback (most recent call last): File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 31, in decorator return func(*args, **kwargs) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 478, in Add cur = self._db.execute(statement, (path, mtime, fileType, component)) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 233, in execute return self._db.execute(query, args)
sqlite3.IntegrityError: UNIQUE constraint failed: files.path
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/transaction.py", line 398, in RunThreadedTransaction txn.Run() File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/transaction.py", line 78, in Run self.get()() File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/common.py", line 138, in Show i.Execute(txn.temp, onProgress) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/install.py", line 389, in Execute db.files.Add(filePath, fileMtime, dest.fileType.id, uid) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 33, in decorator raise IntegrityError(str(e))
vmis.core.errors.IntegrityError: UNIQUE constraint failed: files.path
[2020-02-08 13:10:34,399] Rollback failed
Traceback (most recent call last): File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 31, in decorator return func(*args, **kwargs) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 478, in Add cur = self._db.execute(statement, (path, mtime, fileType, component)) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 233, in execute return self._db.execute(query, args)
sqlite3.IntegrityError: UNIQUE constraint failed: files.path
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/transaction.py", line 398, in RunThreadedTransaction txn.Run() File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/transaction.py", line 78, in Run self.get()() File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/common.py", line 138, in Show i.Execute(txn.temp, onProgress) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/install.py", line 389, in Execute db.files.Add(filePath, fileMtime, dest.fileType.id, uid) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/db.py", line 33, in decorator raise IntegrityError(str(e))
vmis.core.errors.IntegrityError: UNIQUE constraint failed: files.path
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/transaction.py", line 446, in RunThreadedTransaction resolveResults = Resolve([], common.repository.installed, [], db.database) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/dependency.py", line 1421, in Resolve positiveGraph.constructLinks(installed) File "/tmp/vmis.GxziIs/install/vmware-installer/vmis/core/dependency.py", line 385, in constructLinks raise exception
vmis.core.errors.UnsatisfiedDependency: Component vmware-vmrc-app 10.0.6 has unsatisfied dependency: vmware-usbarbitrator>=17.3.0
why ?!
Hi All,
I updated my Windows 10 Host to the latest updates and using VmWare workstation 15 pro. After the update the host and guests machine are no longer connected, I did inspect the ipconfig and noticed that the default gateway is not there. I did try to run VmWare setup file and repair but this did not work. Also did try to edit the Virtual network editor and create new NAT network but no luck
What should I do next ?
Regards,
Hello
I would like to restrict the user from changing all settings of a VM in Workstation Pro 15. I used the built in feature Access Control - Restrictions, but when I do so, I still can change some settings. For example the network settings of the VM.
Is there something I am doing wrong? Or is there any other possibility to block a user from changing the configuration of the VM?
Thanks Michael
I'd like to test a software that's using Open CL in a VM, but I'm currently getting an error that Open CL is not installed in the VM.
After finding some articles through Google I'd like to ask what's necessary to have Open CL run in a VM. Is it possible at all?
NB: I'm using an NVIDIA GTX-980 graphics card on my host machine.
I'm working rather keyboard centered, i.e. I'm using keyboard shortcuts whenever I can. Moreover, I'm working in Fullscreen mode most of the time.
Sometimes, by accident, a VM loses focus and focus is given to the host inadvertently. This probably happens when the mouse pointer moves near the VMware Workstation toolbar when I release the mouse and put my hand on the keyboard.
When this happens, I, for instance, inadvertently open File Explorer on the host instead of the guest or shut down the host instead of the VM. I tend to believe this is a serious issue, because sometimes unsaved work is lost.
VMware: Can you please register two sound events with Windows on the host OS for accessibility reasons:
There's no need to preset these sound events with a sound. Me and other interested users can assign some appropriate sounds ourselves.
Here's how it's done:
I know there have been several threads on this in the past - but most now seem inactive. TL;DR version is Ryzen CPUs (Zen, Zen+ and Zen2) have a bug in an old (Pentium Pro days), poorly documented x86 instruction set called VME. Some people say the issue was fixed by a microcode update and resolved in Ryzen 2000 and newer - but I have a 3700x and still cannot get Windows 98 to run properly as it did on my old Xeon workstation. The primary work-around mentioned - disabling 32-bit protected mode storage drivers - doesn't work for me either. The other workaround discussed, downgrading to Workstation 12.x, isn't an option either since I'm running Win10 1909. I've also not been successful in trying to mask the VME instruction set in the CPUID.
Has anyone been successful with getting Windows 95 or 98 to run on Workstation 15.5 on AMD Ryzen CPUs?
I recently upgraded from VMWare Workstation 14 Pro to 15 Pro. I am receiving the following error message: "Transport (VMDB) error -14: Pipe connection has been broken." How do I resolve this?
"VMware Workstation unrecoverable error: (mks)
Exception 0xc0000005 (access violation) has occurred.
A log file is available in "D:\VMWare Images\Windows 10 x64 - Sentinel SQL Server\vmware.log".
You can request support.
To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
You can also run the "vm-support" script in the Workstation folder directly.
We will respond on the basis of your support entitlement."
I am seeing the above error occur whenever I open a specific virtual machine. I have tried numerous snapshots and it occurs in all of them. I looked in the log file and it seems to be attempting to update VMWare tools when the problem occurs.
Host and virtual machine are both running Windows 10 (1909) with all latest updates.
Any help would be appreciated.
Ralph Allebach
Hello All,
I am doing the testing of 3D native apps and customer demands to execute test in headless mode/run in background.
I have evaluated many other products from that VMware workstation has option to run in headless mode but main problem is that to run the 3D native apps needs NVIDIA graphics card. Which is not getting pass through from the host machine to guest machine due to which 3D native app is working improperly. So basically I want to know how to pass through GPU/NVIDIA graphics card from Host machine to Guest machine in VMWare workstation?
Hoping for quick reply with better solution.
Thanks & Regards,
Kunal Gajbhiye
QA Consultant
Dassault Systemes Global Services, Pvt. Ltd.