VMware Workstation Pro Question

So do you need a license to get proper support for TPM and Secure Boot functions with VMware Workstation Pro ?

The Free for Personal Use doesn’t seem to have these functions.

And of course it seems you can’t just go to the vmware web site any longer to purchase a license or it is not easy to find, but I will keep searching.

As far as I’m aware there isn’t a licensed version of workstation anymore. Installing the latest version should give you all the features. Though I haven’t played with vTPM and secure boot specifically, I do have a Windows 11 NVMe drive in my laptop that I can boot as a VM in workstation without issue.

1 Like

There is a licensed version - but man if you don’t spend big money, you won’t get it. In practical terms, the free version of Pro now includes all the features.

You need to go to the Broadcom portal to download it. There is this guide (link to the link to the guide) here: https://www.reddit.com/r/vmware/comments/1d4syd2/i_made_a_guide_for_downloading_vmware_through/

It’s bad that you need a guide to navigate that awful portal.

1 Like

Thanks everybody for the feedback :wink:

OK, after some further testing I think I found out what is happening.

IF you create a new VM you can enable both the vTPM and the Secure Boot functions.

However you can’t seem to enable these on an existing VM, this was my intent.

Trying to get my current Win 10 Pro VM to have these functions enabled.

I created a new Win 11 Pro VM and was able to enable both these functions.

I also noticed something showing up for my current Win 10 Pro VM,
Upgrade the Virtual Machine.

Anybody know what this function does ?

Yeah, as you’ve discovered, TPM/secure boot is an “on VM creation” thing, probably to stop people screwing themselves (by toggling the option and then having a VM that won’t boot).

If you have to, and are willing to reinstall the OS you can create a new VM and attach the VMDK disk files (or copies of them) to it during virtual disk set up.

Upgrading the virtual machine updates the virtual hardware to the latest/later VMware spec. This means potentially better performance with the hypervisor, typically higher resource limits, but in some cases the virtual hardware may be incompatible with older operating systems (e.g., the emulated virtual NIC for example may be a newer model of card that the OS may not support - but this is something i’ve never seen in real life despite using vmware for 25 years plus).

In general: upgrade the virtual hardware unless you’re running something really old, especially if you have the virtual machine guest tools installed into the guest OS (and you really should - either the version installed from within workstation if supported, or the open-vm-tools package if open source and not directly supported by VMware).

Thanks for the clarification.

1 Like

Also, potentially you could manually edit the virtual machine’s .vmx file to change between secure boot and not.

VMware will likely not support you on this (but good luck getting “support” out of Broadcom anyhow), but you may be able to find documentation on the things to tweak.

the VMX file is basically the configuration file for the VM, its just plain text. IF you are willing to experiment, back it up and if you find the lines to add/change, you could try that.

Sucks they deprecated Shared VM’s in ver16.

Well after my shift ends, I suspend the VM guest and then manually backup the folder into a date stamped archive.

So I guess I could try playing with it, but since my company wants folks to get updated to Windows 11 Pro, I’ve decided on creating a new VM with this and will migrate data and apps over.

But I could still play around with it even after the migration process is complete, at least for my own knowledge :wink:

1 Like

If you’re migrating to Windows 11 Pro (as a host?), maybe check out Hyper-V on Win11 (as Pro includes it).

The console is less buggy, its one less thing to install, one less license, less third party driver(s) in your host and VM, etc.

It doesn’t have right-click/clone as standalone Hyper-V, but you can drive it with PowerShell.

VMware finally gave me the shits (well, again) and I’ve abandoned it (again) because the most recent update broke NAT for VMnetwork. And it’s been broken since march. Particularly salty because I spent the time/effort to upgrade my working version, screwing around with 24 hr wait to get authorised to download (despite being a long term paid customer of Workstation Pro), etc.

Seriously, Broadcom? Bridged VM Networking works, but its not the point…

@thro

My HOST is already running Windows 11 Pro, this is a guest OS I use for work mainly and some testing.

I was also wondering of the Hyper-V option could work too.

The company I work for is willing to send me a notebook that is underpowered of course :frowning:

When I first got an asset from the OLD company back in 2010 it was some P4, Socket 478 machine on the 865 chipset.

I have it stored away as my VM is so much faster :wink: