VMware Workstation Unrecoverable Error: (vcpu-0) - virtual-machine

When using VMWare Workstation 16.2, if we try to create Windows VM, we get the following error when starting the Virtual Machine.
VMware Workstation unrecoverable error: (vcpu-0)
Exception 0xc0000005 (access violation) has occurred.
A log file is available in "C:\Users\name\Documents\Virtual
Machines\Windows_Server_2019\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.
There are no official communication from VMWare at this moment.

This issue appears to be caused by the setting that allows VMWare to work alongside Hyper-V. There are two fixes, if you want to use Hyper-V along with your VMWare solution, we need to set the core count and processor count to 1.
This should solve the issues, but this isn't ideal.
The other option is to disable Hyper-V. I came across this when I was trying to run Faceit-AntiCheat Client. It needs Hyper-V to be disabled. If we follow the following steps we can disable Hyper-V and the VM should work fine.
Click Start and search for Command Prompt
Right-click on Command Prompt and then click Run as administrator
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue
Then type: "bcdedit /set hypervisorlaunchtype off" Press enter
Then type:reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f Press enter again.
Restart your computer
Now you should be able to start the VM with the desired number of processors.

I did not get the same results.
I ran the bcdedit and reg add with confirmation that it "worked", it did not. I also set the processor to 1/1 after reset.
VMWare 16.2 Windows 10 and Windows Server 2019 clients (both updated and working on another system with NVIDA graphics card
specs below
[System Summary]
Item Value
OS Name Microsoft Windows 11 Pro
Version 10.0.22000 Build 22000
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc.
System Model Precision 7560
System Type x64-based PC
System SKU 0A69
Processor 11th Gen Intel(R) Core(TM) i7-11850H # 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.7.0, 12/10/2021
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 03DXD2
BaseBoard Version A00
Platform Role Mobile
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume3
Locale United States
Hardware Abstraction Layer Version = "10.0.22000.1"
User Name BAE0004233\GXP
Time Zone US Mountain Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.2 GB
Available Physical Memory 23.2 GB
Total Virtual Memory 36.2 GB
Available Virtual Memory 25.9 GB
Page File Space 5.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured Hypervisor enforced Code Integrity
Virtualization-based security Services Running Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Related

How do I this fix VERR_VMX_MSR_ALL_VMX_DISABLED in Virtual-Box?

After installing windows 98 in virtualbox, I clicked 'start' button. Then it showed me an error:
Failed to open a session for the virtual machine windows 98.
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
You need virtualization Technology enabled in the Bios
Reboot your machine
Press F10 to enter BIOS.
Security-> System Security
Enable Virtualization Technology (VTx) and Virtualization Technology
Save and start the machine.
Failed to open a session for the virtual machine windows 98.
There are different approaches to solve this, try whichever works for you
1
open windows features win+R --> then optionalfeatures
Disable Hyper-V (if it is available on your machine)
Enable "Virtual Machine platform"
Enable "Windows Hypervisor platform"
Disable "Windows Sandbox" (if available on your machine)
Restart the machine
2
Windows Subsystem for Linux (WSL) feature was enabled.
Disabling it solved it for me.
Restart the machine.
3
If it still doesn't work:
Open Powershell command prompt as admin and then run the following command:
bcdedit /set hypervisorlaunchtype off
Restart the machine
View the full answer:
Unable to launch Ubuntu18.04 on VirtualBox [VERR_NEM_VM_CREATE_FAILED]

Cannot connect tot Win10 Pro x64 VM with enhanced session

If I use basic session, everything works fine, but when I connect in enhanced mode, login prompt is not appearing.
Guest OS: Win 10 Pro x64 Build 18990.vb_release.190921-1704
RDP services are enabled.
Event Log for RemoteDesktopServices-RDPCoreTS/Operational shows a error:
'Failed GetConnectionProperty' in CUMRDPConnection:QueryProperty at 3318 err=[80004001] (RemoteFX module)
Host OS: Win 10 Pro x64 1903 (18362.418)
Hper-V Version: 10.0.18362.1
I disabled RemoteFX in Guest OS with policies, how it is described here, but still no success.
I had the same problem until I stumbled across this Microsoft thread where someone said, "disabling Windows Hello on the VM did the trick for some reason."
Go to Settings -> Accounts -> Sign-in options. Turn off the setting for "Only allow Windows Hello sign-in for Microsoft accounts on this device (Recommended)". Then reboot the VM and enhanced sessions should work.

After my Windows 10 update (July 2018) I cannot start my Hyper V VM: Bootdisk not found

I have applied some windows updates on both my host (Windows 10) and my Hyper-V guest (Windows 10). After rebooting the hyper-v VM cant boot anymore displaying the message that there is no active boot item for booting from UEFI.
After some trail and error, the solution was to reinstall hyper-v on my windows 10 host.
Ensure that hardware virtualization support is turned on in the BIOS settings
Configure networking for the Hyper-V environment to support external network connections. Also ensure that a virtual switch has been created and is functional
Remove all security software and AV
System and drivers are up-to-date.
Also, try to use PowerShell command-line to enable Hyper-V.
Install-WindowsFeature –Name Hyper-V -ComputerName <computer_name> -IncludeManagementTools -Restart

Instance Deploy fails when using LVM

When I provision a single VM where the golden image has an LVM configuration inside, we get a failure:
* vsphere_virtual_machine.vm_1: 1 error(s) occurred:
* vsphere_virtual_machine.vm_1: Customization of the guest
operating system 'ubuntu64Guest' is not supported in this
configuration. Microsoft Vista (TM) and Linux guests with Logical
Volume Manager are supported only for recent ESX host and VMware
Tools versions. Refer to vCenter documentation for supported
configurations.
This seems to be a message returned from Vmware but we are not sure what to do. Why did it fail?
The error returned is a VSphere generic error message, not related to LVM specifically. The real error is caused by either:
VMware Tools not being installed (guest OS customizations require
VMware Tools)
Unsupported guest OS. A list of compatible operating systems can be found here
Please make sure that you have VMware Tools installed in your template and that the guest OS is on the list of supported operating systems.
In order to skip the customization step for unsupported operating systems, use the skip_customization argument on the virtual machine resource.

Preload USB.inf and with VID/PID for hardware product (USB-HID) - Windows XP

Description of the problem:
Insert USB-HID Device (Barcode scanner) on a clean Windows XP Machine.
After windows loads the USB-HID Driver.
Windows XP pops a dialog box asking the user to reboot the machine. (This is the problem)
Scenario:
Remotely Deploy a software package to talk to these devices. (no hardware at this point)
Remotely reboot machines.
Hardware is added to each machine. (no reboot)
Investigation:
Windows adds a control class referencing the "usb.inf" file.
Windows adds a device class referencing the control class.
Windows adds a enumerates the device referencing the device and HIDClass.
I believe what needs to be done is to "Pre-load" or "Pre-install" the driver, but we do not provide the INF files (provided via usb.inf).
Our other drivers utilize dpinst to handle installation on a different driver interface (btw this procedure does work for the desired behavior), but we are providing those INF / CAT / SYS files.
Is it possible to leverage SetupCopyOEMInf to perform this function?
What other avenues could be pursued to pre-load/pre-install this driver?
As it turns out, the problem was connecting to a device before it had enumerated its sub devices, locking the device tree, which caused the 'please reboot windows' dialog to appear when the last device enumerated.