WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Workstation / Workaround for sorry this product can not be installed inside of a virtual machine for early VMware Hypervisors

Workaround for sorry this product can not be installed inside of a virtual machine for early VMware Hypervisors

04.12.2023 by William Lam // 3 Comments

While continuing my exploration trip down memory lane with early VMware Hypervisors such as VMware GSX Server, VMware Server and VMware Workstation, I came across the following error message when attempting to install these hypervisors within a Windows VM:

Sorry this product can not be installed inside of a virtual machine

I guess this would make sense given the ability to run a Hypervisor (Nested Virtualization) within a VM would not be possible for many more years later and this check seemed like a good way to prevent users from having a bad user experience, however it prevent me from continuing.


After a bit of digging and researching, I came to find that there was a workaround for this by inserting a special Windows registry key that would bypass the check. The key would be an empty REG_BINARY called InstallInVM under the path HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Misc as shown in the screenshot below.


You can also add the Windows registry key by using the following registry script:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Misc]
"InstallInVM"=hex:

After adding the new registry key, you will need to reboot the system before the change goes into effect and now you can install these early VMware Hypervisors which have these pre-checks.

More from my site

  • VMware 1.0, GSX Server 1.0, Server 1.0 and Workstation 3.0 - Trip down memory lane
  • Quick Tip - Virtualized Intel VT-x/EPT or AMD-V/RVI is not supported on this platform for VMware Workstation
  • Pre-release Microsoft OS/2 2.0 on ESXi
  • Heads Up - Performance Impact with VMware Workstation on Windows 11 with Intel Hybrid CPUs
  • Quick Tip - Microsoft Windows 11 Eval Images for VMware Hypervisors

Categories // Workstation Tags // GSX Server, server, workstation

Comments

  1. *protectedAlfons Ruiz says

    03/18/2025 at 12:29 am

    Hi Willian, Thank you I installed GSX over VM Windows 2003, however when i tried to power up the vm -for Novell 4- over GSX and it appears this message "You may not power on VMware GSX in a virtual machine". Did you power on vm over a GSX over a ESX host? Regards

    Reply
    • William Lam says

      03/18/2025 at 9:56 am

      Yes, for my setup ESXi was used as the bare-metal Hypervisor and then GSX ran on top as a regular VM. Did you apply the workaround on your Windows 2003 VM?

      Reply
      • *protectedAlfonso Ruiz Montilla says

        03/18/2025 at 1:09 pm

        Yes, I did it, i added the registry entry that allowed me to install GSX but not to run a vm.

        Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...