icedterminal · October 15, 2025 03:12 · Oct 11, 2020 · Oct 10, 2020 · Oct 10, 2020 · Oct 5, 2020
diff --git a/vmxfile.md b/vmxfile.md
@@ -16,7 +16,7 @@ Manually edit the VMX file. Add the lines below. If already present, simply chan
 - `mce.enable = "TRUE"` Enables Machine Check Exception (MCE). Helpful to find errors in a VM.
 - `vhu.enable = "TRUE"` Enables nested virtualization
 - `SMBIOS.reflectHost = "TRUE"` Enables host to guest hardware reflection.
-- `hypervisor.cpuid.v0 = "FALSE"` Tricks the OS into thinking it is not running in a virtualized environment.
+- `hypervisor.cpuid.v0 = "FALSE"` Removes the CPU flag `-hypervisor` thus the OS thinks it is not running in a virtualized environment.
 
 Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If your task manager looks like the image on the right, your VM status is masked.
 

diff --git a/vmxfile.md b/vmxfile.md
@@ -8,7 +8,7 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
     - Virtualize CPU Performance Counters
     - Virtualize IOMMU
 3. Install Windows 10 in VM.
-4. Install VMWare tools.
+4. Optionally install VMWare tools for some performance gains or features.
 5. *Clean* shutdown Windows 10 VM.
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.

diff --git a/vmxfile.md b/vmxfile.md
@@ -1,6 +1,6 @@
 # Hide VM Identification in VMWare (Stealthy)
 
-Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.html) 16.x, Windows host and guest, using an Intel CPU.
+Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.html) 16.x, Windows host and guest in UEFI mode, using an Intel CPU.
 
 1. Create a Windows 10 VM.
 2. Edit VM settings [Processor section](https://i.imgur.com/nMaN01l.png). Enable (tick) these:
@@ -18,21 +18,27 @@ Manually edit the VMX file. Add the lines below. If already present, simply chan
 - `SMBIOS.reflectHost = "TRUE"` Enables host to guest hardware reflection.
 - `hypervisor.cpuid.v0 = "FALSE"` Tricks the OS into thinking it is not running in a virtualized environment.
 
-Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If your task manager looks like the image on the right, your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
+Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If your task manager looks like the image on the right, your VM status is masked.
 
 Incorrect |  Correct
 --- | ---
 ![wrong](https://i.imgur.com/5MyBUYz.png) | ![right](https://i.imgur.com/hgfmXx8.png)
 
-You can also change device names with `regedit` under `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum` to appear as a real device in Device Manager. Jim Browning has a [simple tutorial video](https://youtu.be/6TM45vNI4Qc?t=91). While this isn't a thourough demonstration, it shows you what to do. You should rename every device that includes the words "VMWare" or "Virtual". You can even go a step further and edit the `.inf` files that corrolate to the driver. Windows pulls some information from this file to display provider, date and version. To find the INF name, double click the device in Device Manager. Click the *Details* tab. Select *Inf name* in the *Property* drop down menu. You'll find the file at `C:\Windows\INF`.## Explained
+You can also change device names with `regedit` under `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum` to appear as a real device in Device Manager. Jim Browning has a [simple tutorial video](https://youtu.be/6TM45vNI4Qc?t=91). While this isn't a thourough demonstration, it shows you what to do. You should rename every device that includes the words "VMWare" or "Virtual". You can even go a step further and edit the `.inf` files that corrolate to the driver. Windows pulls some information from this file to display provider, date and version. To find the INF name, double click the device in Device Manager. Click the *Details* tab. Select *Inf name* in the *Property* drop down menu. You'll find the file at `C:\Windows\INF`.
+
+*However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods. VMWare, and other VM software for that matter, stamp devices as vritual at a low level. There are so many ways to detect if an OS is isolated virtually. You can try the tools and methods below if you need more hardening against detection.
+
+- http://www.trapkit.de/tools/scoopyng/
+- https://sectechno.com/sems-anti-sandbox-anti-virtual-machine-detection-tool/
+- https://www.vmray.com/cyber-security-blog/a-pafish-primer/
 
 ## Other VMs
 
 No I do not know how to do this with other VMs nor do I care to invest time trying them. If you use VBox, QEMU, Fusion, Parallels or KVM, you'll have to figure that out on your own. I'm sure Google can help.
 
 ## Warnings
 
-**DO NOT** use the above method to test unstrusted software. If you want to do this, you need to disable (untick) the performance options first...
+**DO NOT** use the above method to test unstrusted software. If you want to do this, don't install VMWare guest tools, you need to disable (untick) the performance options first...
 
 - Virtualize Intel VT-x/AMD-V
 - Virtualize CPU Performance Counters

diff --git a/vmxfile.md b/vmxfile.md
@@ -12,27 +12,39 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
 5. *Clean* shutdown Windows 10 VM.
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.
-```
-mce.enable = "TRUE"
-vhu.enable = "TRUE"
-SMBIOS.reflectHost = "TRUE"
-hypervisor.cpuid.v0 = "FALSE"
-monitor_control.virtual_rdtsc = "FALSE"
-monitor_control.restrict_backdoor = "TRUE"
-isolation.tools.getPtrLocation.disable = "TRUE"
-isolation.tools.setPtrLocation.disable = "TRUE"
-isolation.tools.setVersion.disable = "TRUE"
-isolation.tools.getVersion.disable = "TRUE"
-isolation.tools.hgfs.disable = "TRUE"
-```
+
+- `mce.enable = "TRUE"` Enables Machine Check Exception (MCE). Helpful to find errors in a VM.
+- `vhu.enable = "TRUE"` Enables nested virtualization
+- `SMBIOS.reflectHost = "TRUE"` Enables host to guest hardware reflection.
+- `hypervisor.cpuid.v0 = "FALSE"` Tricks the OS into thinking it is not running in a virtualized environment.
+
 Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If your task manager looks like the image on the right, your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 
 Incorrect |  Correct
 --- | ---
 ![wrong](https://i.imgur.com/5MyBUYz.png) | ![right](https://i.imgur.com/hgfmXx8.png)
 
-You can also change device names with `regedit` under `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum` to appear as a real device in Device Manager. Jim Browning has a [simple tutorial video](https://youtu.be/6TM45vNI4Qc?t=91). While this isn't a thourough demonstration, it shows you what to do. You should rename every device that includes the words "VMWare" or "Virtual". You can even go a step further and edit the `.inf` files that corrolate to the driver. Windows pulls some information from this file to display provider, date and version. To find the INF name, double click the device in Device Manager. Click the *Details* tab. Select *Inf name* in the *Property* drop down menu. You'll find the file at `C:\Windows\INF`. 
+You can also change device names with `regedit` under `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum` to appear as a real device in Device Manager. Jim Browning has a [simple tutorial video](https://youtu.be/6TM45vNI4Qc?t=91). While this isn't a thourough demonstration, it shows you what to do. You should rename every device that includes the words "VMWare" or "Virtual". You can even go a step further and edit the `.inf` files that corrolate to the driver. Windows pulls some information from this file to display provider, date and version. To find the INF name, double click the device in Device Manager. Click the *Details* tab. Select *Inf name* in the *Property* drop down menu. You'll find the file at `C:\Windows\INF`.## Explained
 
 ## Other VMs
 
-No I do not know how to do this with other VMs nor do I care to invest time trying them. If you use VBox, QEMU, Fusion, Parallels or KVM, you'll have to figure that out on your own. I'm sure Google can help.
+No I do not know how to do this with other VMs nor do I care to invest time trying them. If you use VBox, QEMU, Fusion, Parallels or KVM, you'll have to figure that out on your own. I'm sure Google can help.
+
+## Warnings
+
+**DO NOT** use the above method to test unstrusted software. If you want to do this, you need to disable (untick) the performance options first...
+
+- Virtualize Intel VT-x/AMD-V
+- Virtualize CPU Performance Counters
+- Virtualize IOMMU
+
+...and then manually edit the VMX file. Add the lines below.
+```
+monitor_control.virtual_rdtsc = "FALSE"
+monitor_control.restrict_backdoor = "TRUE"
+isolation.tools.getPtrLocation.disable = "TRUE"
+isolation.tools.setPtrLocation.disable = "TRUE"
+isolation.tools.setVersion.disable = "TRUE"
+isolation.tools.getVersion.disable = "TRUE"
+isolation.tools.hgfs.disable = "TRUE"
+```
diff --git a/vmxfile.md b/vmxfile.md
@@ -31,7 +31,7 @@ Incorrect |  Correct
 --- | ---
 ![wrong](https://i.imgur.com/5MyBUYz.png) | ![right](https://i.imgur.com/hgfmXx8.png)
 
-You can also change device names with `regedit` to appear as a real device in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
+You can also change device names with `regedit` under `HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum` to appear as a real device in Device Manager. Jim Browning has a [simple tutorial video](https://youtu.be/6TM45vNI4Qc?t=91). While this isn't a thourough demonstration, it shows you what to do. You should rename every device that includes the words "VMWare" or "Virtual". You can even go a step further and edit the `.inf` files that corrolate to the driver. Windows pulls some information from this file to display provider, date and version. To find the INF name, double click the device in Device Manager. Click the *Details* tab. Select *Inf name* in the *Property* drop down menu. You'll find the file at `C:\Windows\INF`. 
 
 ## Other VMs
 

diff --git a/vmxfile.md b/vmxfile.md
@@ -25,7 +25,7 @@ isolation.tools.setVersion.disable = "TRUE"
 isolation.tools.getVersion.disable = "TRUE"
 isolation.tools.hgfs.disable = "TRUE"
 ```
-Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If you task manager looks like the image on the right, your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
+Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If your task manager looks like the image on the right, your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 
 Incorrect |  Correct
 --- | ---

diff --git a/vmxfile.md b/vmxfile.md
@@ -4,9 +4,9 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
 
 1. Create a Windows 10 VM.
 2. Edit VM settings [Processor section](https://i.imgur.com/nMaN01l.png). Enable (tick) these:
-  - Virtualize Intel VT-x/AMD-V
-  - Virtualize CPU Performance Counters
-  - Virtualize IOMMU
+    - Virtualize Intel VT-x/AMD-V
+    - Virtualize CPU Performance Counters
+    - Virtualize IOMMU
 3. Install Windows 10 in VM.
 4. Install VMWare tools.
 5. *Clean* shutdown Windows 10 VM.

diff --git a/vmxfile.md b/vmxfile.md
@@ -3,10 +3,10 @@
 Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.html) 16.x, Windows host and guest, using an Intel CPU.
 
 1. Create a Windows 10 VM.
-2. Edit VM settings Processor section to look like the image below
-
-  ![image](https://i.imgur.com/nMaN01l.png)
-
+2. Edit VM settings [Processor section](https://i.imgur.com/nMaN01l.png). Enable (tick) these:
+  - Virtualize Intel VT-x/AMD-V
+  - Virtualize CPU Performance Counters
+  - Virtualize IOMMU
 3. Install Windows 10 in VM.
 4. Install VMWare tools.
 5. *Clean* shutdown Windows 10 VM.
@@ -25,15 +25,13 @@ isolation.tools.setVersion.disable = "TRUE"
 isolation.tools.getVersion.disable = "TRUE"
 isolation.tools.hgfs.disable = "TRUE"
 ```
-Power on VM. Check Task Manager
+Power on VM. Check Task Manager. If your task manager looks like the image on the left, something went wrong or you made a mistake. Try again. If you task manager looks like the image on the right, your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 
 Incorrect |  Correct
 --- | ---
 ![wrong](https://i.imgur.com/5MyBUYz.png) | ![right](https://i.imgur.com/hgfmXx8.png)
 
-Your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
-
-Change device names with `regedit` to appear as real in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
+You can also change device names with `regedit` to appear as a real device in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
 
 ## Other VMs
 

diff --git a/vmxfile.md b/vmxfile.md
@@ -25,15 +25,11 @@ isolation.tools.setVersion.disable = "TRUE"
 isolation.tools.getVersion.disable = "TRUE"
 isolation.tools.hgfs.disable = "TRUE"
 ```
-Power on VM. Check Task Manager. If you see this,
+Power on VM. Check Task Manager
 
-![wrong](https://i.imgur.com/5MyBUYz.png)
-
-Something went wrong. Check your VMX file or try again.
-
-If you see this,
-
-![right](https://i.imgur.com/hgfmXx8.png)
+Incorrect |  Correct
+--- | ---
+![wrong](https://i.imgur.com/5MyBUYz.png) | ![right](https://i.imgur.com/hgfmXx8.png)
 
 Your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 

diff --git a/vmxfile.md b/vmxfile.md
@@ -37,4 +37,8 @@ If you see this,
 
 Your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 
-Change device names with `regedit` to appear as real in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
+Change device names with `regedit` to appear as real in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
+
+## Other VMs
+
+No I do not know how to do this with other VMs nor do I care to invest time trying them. If you use VBox, QEMU, Fusion, Parallels or KVM, you'll have to figure that out on your own. I'm sure Google can help.
diff --git a/vmxfile.md b/vmxfile.md
@@ -25,6 +25,16 @@ isolation.tools.setVersion.disable = "TRUE"
 isolation.tools.getVersion.disable = "TRUE"
 isolation.tools.hgfs.disable = "TRUE"
 ```
-Power on VM. Check Task Manager.
+Power on VM. Check Task Manager. If you see this,
+
+![wrong](https://i.imgur.com/5MyBUYz.png)
+
+Something went wrong. Check your VMX file or try again.
+
+If you see this,
+
+![right](https://i.imgur.com/hgfmXx8.png)
+
+Your VM status is masked. *However*, there are other ways to check for a VM. Software that wants to determine if you are, can still do it by other means. This method takes care of most common detection methods.
 
 Change device names with `regedit` to appear as real in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
diff --git a/vmxfile.md b/vmxfile.md
@@ -4,6 +4,7 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
 
 1. Create a Windows 10 VM.
 2. Edit VM settings Processor section to look like the image below
+
   ![image](https://i.imgur.com/nMaN01l.png)
 
 3. Install Windows 10 in VM.

diff --git a/vmxfile.md b/vmxfile.md
@@ -4,7 +4,7 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
 
 1. Create a Windows 10 VM.
 2. Edit VM settings Processor section to look like the image below
-  - ![image](https://i.imgur.com/nMaN01l.png)
+  ![image](https://i.imgur.com/nMaN01l.png)
 
 3. Install Windows 10 in VM.
 4. Install VMWare tools.

diff --git a/vmxfile.md b/vmxfile.md
@@ -2,12 +2,13 @@
 
 Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.html) 16.x, Windows host and guest, using an Intel CPU.
 
-1. Install Windows 10 VM.
-2. Install VMWare tools.
-3. *Clean* shutdown Windows 10 VM.
-4. Edit VM settings Processor section to look like the image below
+1. Create a Windows 10 VM.
+2. Edit VM settings Processor section to look like the image below
+  - ![image](https://i.imgur.com/nMaN01l.png)
 
-![image](https://i.imgur.com/nMaN01l.png)
+3. Install Windows 10 in VM.
+4. Install VMWare tools.
+5. *Clean* shutdown Windows 10 VM.
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.
 ```

diff --git a/vmxfile.md b/vmxfile.md
@@ -11,13 +11,10 @@ Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.h
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.
 ```
-vhv.enable = "TRUE"
-SMBIOS.reflectHost = "TRUE"
-vvtd.enable = "TRUE"
-vpmc.enable = "TRUE"
-hypervisor.cpuid.v0 = "FALSE"
 mce.enable = "TRUE"
 vhu.enable = "TRUE"
+SMBIOS.reflectHost = "TRUE"
+hypervisor.cpuid.v0 = "FALSE"
 monitor_control.virtual_rdtsc = "FALSE"
 monitor_control.restrict_backdoor = "TRUE"
 isolation.tools.getPtrLocation.disable = "TRUE"

diff --git a/vmxfile.md b/vmxfile.md
@@ -1,6 +1,6 @@
 # Hide VM Identification in VMWare (Stealthy)
 
-Tested using WorkStation 16.x, Windows host and guest, using an Intel CPU.
+Tested using [WorkStation Pro](https://www.vmware.com/products/workstation-pro.html) 16.x, Windows host and guest, using an Intel CPU.
 
 1. Install Windows 10 VM.
 2. Install VMWare tools.
@@ -11,14 +11,11 @@ Tested using WorkStation 16.x, Windows host and guest, using an Intel CPU.
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.
 ```
-vmci0.present = "TRUE"
-hpet0.present = "TRUE"
-virtualHW.productCompatibility = "hosted"
 vhv.enable = "TRUE"
 SMBIOS.reflectHost = "TRUE"
 vvtd.enable = "TRUE"
 vpmc.enable = "TRUE"
-hypervisor.cpuid.v0 = “FALSE”
+hypervisor.cpuid.v0 = "FALSE"
 mce.enable = "TRUE"
 vhu.enable = "TRUE"
 monitor_control.virtual_rdtsc = "FALSE"

diff --git a/vmxfile.md b/vmxfile.md
@@ -1,6 +1,6 @@
 # Hide VM Identification in VMWare (Stealthy)
 
-Tested using Windows host and guest using an Intel CPU.
+Tested using WorkStation 16.x, Windows host and guest, using an Intel CPU.
 
 1. Install Windows 10 VM.
 2. Install VMWare tools.

diff --git a/vmxfile.md b/vmxfile.md
@@ -9,7 +9,7 @@ Tested using Windows host and guest using an Intel CPU.
 
 ![image](https://i.imgur.com/nMaN01l.png)
 
-Manually edit the VMX file. Add the lines below. If already present, simply change the value.
+Manually edit the VMX file. Add the lines below. If already present, simply change the value. VMWare will rearrange the order once the VM is booted.
 ```
 vmci0.present = "TRUE"
 hpet0.present = "TRUE"
@@ -21,7 +21,13 @@ vpmc.enable = "TRUE"
 hypervisor.cpuid.v0 = “FALSE”
 mce.enable = "TRUE"
 vhu.enable = "TRUE"
-isolation.tools.hgfs.disable = "FALSE"
+monitor_control.virtual_rdtsc = "FALSE"
+monitor_control.restrict_backdoor = "TRUE"
+isolation.tools.getPtrLocation.disable = "TRUE"
+isolation.tools.setPtrLocation.disable = "TRUE"
+isolation.tools.setVersion.disable = "TRUE"
+isolation.tools.getVersion.disable = "TRUE"
+isolation.tools.hgfs.disable = "TRUE"
 ```
 Power on VM. Check Task Manager.
 

diff --git a/vmxfile.md b/vmxfile.md
@@ -1,6 +1,11 @@
-Tested using Windows host and guest.
+# Hide VM Identification in VMWare (Stealthy)
 
-Install Windows 10 VM. Install VMWare tools. *Clean* shutdown Windows 10 VM. Edit VM settings Processor section to look like the image below
+Tested using Windows host and guest using an Intel CPU.
+
+1. Install Windows 10 VM.
+2. Install VMWare tools.
+3. *Clean* shutdown Windows 10 VM.
+4. Edit VM settings Processor section to look like the image below
 
 ![image](https://i.imgur.com/nMaN01l.png)
 
@@ -18,4 +23,6 @@ mce.enable = "TRUE"
 vhu.enable = "TRUE"
 isolation.tools.hgfs.disable = "FALSE"
 ```
-Power on VM. Check Task Manager. 
+Power on VM. Check Task Manager.
+
+Change device names with `regedit` to appear as real in Device Manager. https://www.youtube.com/watch?v=6TM45vNI4Qc
diff --git a/vmxfile.md b/vmxfile.md
@@ -1,6 +1,7 @@
 Tested using Windows host and guest.
 
-Install Windows 10 VM. Install VMWare tools. *Clean* shutdown Windows 10 VM. Edit VM settings Processor section to look like the image
+Install Windows 10 VM. Install VMWare tools. *Clean* shutdown Windows 10 VM. Edit VM settings Processor section to look like the image below
+
 ![image](https://i.imgur.com/nMaN01l.png)
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value.

diff --git a/vmxfile.md b/vmxfile.md
@@ -1,7 +1,7 @@
 Tested using Windows host and guest.
 
 Install Windows 10 VM. Install VMWare tools. *Clean* shutdown Windows 10 VM. Edit VM settings Processor section to look like the image
-[!image](https://i.imgur.com/nMaN01l.png)
+![image](https://i.imgur.com/nMaN01l.png)
 
 Manually edit the VMX file. Add the lines below. If already present, simply change the value.
 ```

diff --git a/vmxfile.md b/vmxfile.md
@@ -0,0 +1,20 @@
+Tested using Windows host and guest.
+
+Install Windows 10 VM. Install VMWare tools. *Clean* shutdown Windows 10 VM. Edit VM settings Processor section to look like the image
+[!image](https://i.imgur.com/nMaN01l.png)
+
+Manually edit the VMX file. Add the lines below. If already present, simply change the value.
+```
+vmci0.present = "TRUE"
+hpet0.present = "TRUE"
+virtualHW.productCompatibility = "hosted"
+vhv.enable = "TRUE"
+SMBIOS.reflectHost = "TRUE"
+vvtd.enable = "TRUE"
+vpmc.enable = "TRUE"
+hypervisor.cpuid.v0 = “FALSE”
+mce.enable = "TRUE"
+vhu.enable = "TRUE"
+isolation.tools.hgfs.disable = "FALSE"
+```
+Power on VM. Check Task Manager.