Q: Win10Pro VM Guest install / "Bios" Activation key?

[motoridersd]

Thanks for the guide. I followed it, but I'm getting an error in the logs about the product name and manufacturer:

Feb 03 11:53:15 monitor1 pveproxy[9126]: vm 100 - unable to parse value of 'smbios1' - format error
product: value does not match the regex pattern
manufacturer: value does not match the regex pattern
Feb 03 11:53:24 monitor1 pvestatd[955]: vm 100 - unable to parse value of 'smbios1' - format error
product: value does not match the regex pattern
manufacturer: value does not match the regex pattern
Feb 03 11:53:27 monitor1 pvedaemon[9923]: vm 100 - unable to parse value of 'smbios1' - format error
manufacturer: value does not match the regex pattern
product: value does not match the regex pattern
Feb 03 11:53:27 monitor1 pveproxy[10690]: vm 100 - unable to parse value of 'smbios1' - format error
product: value does not match the regex pattern

The devices I have are HP and there are spaces and dashes, but I don't know why it would be complaining. Here's an example of the smbios1 line, with some things masked:

smbios1: uuid=14ba2180-2678-16ea-980c-eae1d74cee07,manufacturer=Hewlett-Packard,product=HP ProDesk 600 G1 DM,serial=FUA42435AL

When running the installer with that line (and the acpi one with the slic_table), I wasn't asked what version of Windows to install or to put in a product key, but after install, Windows says it is not activated.

 

[LnxBil]

Sure, there are spaces in the name. Try to add all the values via the GUI, the data will then be base64 encoded and will therefore work.

 

[kenm]

I know this post is a little old but I thought I'd add something I found that caused a problem and the solution may help others. I had a working Win10 VM but when I went into VM Options and made a change, the "smbios1:" entry was removed from the VM config, which caused the VM to hang at boot. I further noticed that the "SMBIOS settings (type 1)" field on the VM Options screen was blank. I went into Edit and add UUID, Manufacturer, Product, and Serial info to that field and then the VM config worked again. Also noticed that a "base64=1" parameter had been added and the strings saved in the VM config had been encoded.

This is with PVE 8.0.3 and Win10Pro 22H2, in case that matters.

 

[rlegit]

Just wanted to comment that SLIC and MSDM were available on my 10th gen Intel, but only MSDM worked. On an 11th gen Intel, I don't have SLIC at all.

 

[eleanor]

Just wanted to add that this worked great and only took a few minutes.

• for "Product" you should enter your "Product Name" from the dmidecode step. I also had many spaces in my product name and did not use quotes or apostrophes, and it worked fine.

Thanks for the guide!

 

[pinux]

Tim! Thank you!
It works like a charms, I was able to install Win11 Pro fully licensed without a hitch.
Thanks for the guide!

 

[devop4ever]

Hi,
Is it possible to recognize if slic table has Windows product key or hasn't, because for my secod hand mini-pc this trick failed? From Nirsoft's Produkey software ran on virtualized Windows 10 there is no product key, what clears out why windows is not activated. But pc should have one, because as far as I know it was not sold without windows (Fujitus ESPRIMO Q556) and I did fresh install of Windows already without entering any key before decided to use Proxmox.
I checked about ten times my configuration so my mistake is excluded I think. Any clues?

Edit: it worked with first solution by @fortitechsolutions - thanks

cat /sys/firmware/acpi/tables/MSDM > slic_table

instead of

cat /sys/firmware/acpi/tables/SLIC > slic_table