You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
Disclaimer: I don't understand any of this beyond what I read on the internet while trying to solve my immediate problems.
The script currently copies only the SLIC table from the host to the virtual machine. This stackexchange answer suggests copying both the SLIC and MSDM tables as a single file. I tried this, by first running the script, then overwriting the contents of the SLIC.BIN file it created using the cat command from that answer. After that, I started the Windows installation, and once it was installed, I tried slmgr /xpr, which said: "Windows(R), Professional edition: The machine is permanently activated.", without my having taken any further action. Notably, I hadn't done any of the slmgr commands listed in the README, nor did I have to select "I do not have a product key" at any point during the install.
The naive inference is that copying the MSDM table avoided the need for those other steps, but I'll leave interpretation to you, just reporting my experience. :)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Disclaimer: I don't understand any of this beyond what I read on the internet while trying to solve my immediate problems.
The script currently copies only the SLIC table from the host to the virtual machine. This stackexchange answer suggests copying both the SLIC and MSDM tables as a single file. I tried this, by first running the script, then overwriting the contents of the SLIC.BIN file it created using the
cat
command from that answer. After that, I started the Windows installation, and once it was installed, I triedslmgr /xpr
, which said: "Windows(R), Professional edition: The machine is permanently activated.", without my having taken any further action. Notably, I hadn't done any of theslmgr
commands listed in the README, nor did I have to select "I do not have a product key" at any point during the install.The naive inference is that copying the MSDM table avoided the need for those other steps, but I'll leave interpretation to you, just reporting my experience. :)
The text was updated successfully, but these errors were encountered: