ProductKey = "Installed Key: " & ConvertToKey(DigitalID) ProductID = "Product ID: " & objshell.RegRead(Path & "ProductID") ProductName = "Product Name: " & objshell.RegRead(Path & "ProductName") Path = "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\"ĭigitalID = objshell.RegRead(Path & "DigitalProductId")ĭim ProductName,ProductID,ProductKey,ProductData Set objshell = CreateObject("WScript.Shell") You can use the following script stored as script2.vbs Option Explicit Here's what happens when I run this tool on my PC, which does not have an embedded Windows 10 license key in the BIOS as I built the PC myself and used a regular retail key: They do, however, recognize the OEM license key. After activation, Microsoft's activation servers will then know the hardware fingerprint of the computer but not before. OEM PC manufacturers, such as the one that made the OP's computer, work with Microsoft to embed the license key in the BIOS, which is how Windows is able to activate itself even if you wiped your new PC to do a clean install of Windows before connecting it to the Internet. This will be a very quick process and will guarantee a stable system.Īfter performing a clean install using a 4+ GB flash drive, Windows will automatically activate itself online almost immediately.
I would personally just do a completely clean install of Windows 10 and then manually reinstall the applications and import the data from your backup. The OEM license key is embedded in your BIOS and will be detected automatically by Windows. You won't need need to manually enter the license key. It's likely that I'll need the new machine's Windows 10 key. How can I get the key from the partitions (if it's there at all) while booting from a Linux image? I'm not sure if it's stored in the BIOS (it came with Windows 10 preinstalled) or somewhere on the partitions. It's likely that I'll need the new machine's Windows 10 key.
Now the machine's still stuck in the loop and decided to try and repair it externally using a bootable Windows 10 image. I tried resetting the machine (whilst keeping my files), but this failed halfway through.
I tried:īooting from the console and running: sfc /scannowīoth seemed to have completed successfully, but now the machine would get stuck in a startup repair loop. The new machine would boot, but the wireless network drivers were not recognized and later found out (to the best of my knowledge) they couldn't be installed. What followed was a medium-sized nightmare. I dd-ed the new machine's partitions to an external drive: /dev/nvme0n1p1Īnd afterwards move my current partitions to the new machine.
I got a new laptop it came with an existing Windows installation, but I wanted to migrate my current backup to the new machine.
0 kommentar(er)
