![]() ![]() He has been using computers for 20 years - tinkering with everything from the UI to the Windows registry to device firmware. Nick Lewis is a staff writer for How-To Geek. It also lets you save it as a text file, so you can reference it later. When you double-click the VBS script, you'll get a small popup that displays your Windows product key. Set fso = CreateObject( "Scripting.FileSystemObject") UserName = objshell.ExpandEnvironmentStrings( "%UserName%")įName = "C:\Users\" & UserName & "\Desktop\WindowsKeyInfo.txt " Set objshell = CreateObject( "wscript.shell") If Last = 0 Then KeyOutput = insert & KeyOutputĬonvertToKey = Mid(KeyOutput, 1, 5) & "-" & Mid(KeyOutput, 6, 5) & "-" & Mid(KeyOutput, 11, 5) & "-" & Mid(KeyOutput, 16, 5) & "-" & Mid(KeyOutput, 21, 5) KeyOutput = Replace(KeyOutput, keypart1, keypart1 & insert, 2, 1, 0) KeyOutput = Mid(Maps,Current+ 1, 1) & KeyOutput If vbYes = MsgBox(ProductData & vblf & vblf & "Save to a file?", vbYesNo + vbQuestion, "BackUp Windows Key Information") thenĭim isWin8, Maps, i, j, Current, KeyOutput, Last, keypart1, insert ProductData = ProductName & vbNewLine & ProductID & vbNewLine & ProductKey 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 don't even need to know it -assuming you're installing the same edition of Windows the PC came with, it should automatically activate and work without you needing to enter a key. The key for the version of Windows the PC comes with is stored in the computer's UEFI firmware or BIOS. Embedded in your PC's UEFI firmware: Many newer PCs that come with Windows 8, Windows 10, or Windows 11 use a new method.This system was common for Windows 7 PCs. The one in the registry and key-viewer application is a red herring. The actual key is on a certificate of authenticity (COA) sticker on your PC or its power supply. If your PC uses this, the product key on your PC - the one stored in the registry, and the one key-viewer applications display - will be different from the actual key your PC needs. Printed on a sticker: Some PCs use a technology called "System Locked Pre-installation," or SLP.Crucially, you'll need to grab it from your operating system before you begin reinstalling Windows or it could be deleted if you format your hard drive. You can extract this product key, and - often - enter it when reinstalling Windows on your PC. Stored in software on your PC: When you (or your PC manufacturer) installs Windows, Windows stores its product key in the registry.The key you need will be in one of three places: Please note there are two different numbers for both of the instructions, not sure if they are related to the license numbers though, but they are not the same (with # md5 is a8f1283303838b4d3bd943775e463239 and with the # command line is 9ddc171d00df98cbf8b4b0d8469ce90a).Where Can You Find Your Windows Product Key? I don't know how to interpret the instructions you provided (below) : md5(2.plist) = a8f1283303838b4d3bd943775e463239Ĭp 2.plist /Library/Preferences/ or download it in library by command lineĬurl -sSL -o /Library/Preferences/2.plist After doing this, I tried to opened the office applications again and now they just open a microsoft window for the sign in. Therefore I proceeded to use the Microsoft_Office_License_Removal tool that was also provided here. Then I opened the office applications, but there were asking for sigining in and activation. I wonder if having this file also here would create any conflict with the licensing. I noticed there is another file named .plist. Then I moved the file to /Library/Preferences folder while authenticating it. txt file while changing the extension from ".txt" to ".plist". I opened the raw data plist file you provided and downloaded as a. Official Link - Office 2016 Volume License 16.16.10.Install Office2016 for mac with Office Suite Install, but DO NOT RUN OFFICE AFTER INSTALLED To check it, you can see details in this comment () Office 2016 16.11 for macOS VL2 license The Serializer.pkg in this gist is signature by Microsoft Corporation Official. Here is the official download link for Microsoft_Office_License_Removal tool. If you alaways been asked for 'Sign in' and still requires activation, please try to remove Office license files on a Mac. Run Microsoft_Office_2019_VL_Serializer and it will automatic activate Office 2019 Microsoft_Office_2019_VL_Serializer.pkg official link.Microsoft_Office_2019_VL_Serializer.pkg in this gist.Manual download and install Microsoft_Office_2019_VL_Serializer.pkg ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |