Unlock Your Windows Product Key: Command Prompt & PowerShell Guide

Table of Contents

Understanding your Windows product key is essential for activation, reinstallation, and managing your software licenses. Depending on how you acquired your Windows license, the product key might be stored in different locations. For many modern computers, particularly those with pre-installed Windows (OEM licenses), the key is embedded directly in the computer’s BIOS or UEFI firmware. For retail licenses, the key is typically entered during installation and linked to your system or Microsoft Account, with information stored within the Windows Registry. Retrieving this key can be necessary for various reasons, such as reinstalling Windows or transferring a retail license to new hardware (where permissible).

Traditionally, OEM computers came with a Certificate of Authenticity (COA) sticker displaying the product key. However, this practice has largely been discontinued. Manufacturers now embed the key digitally into the firmware, making it automatically detectable by the Windows installation process on that specific machine. While convenient for initial setup, this change means the key isn’t immediately visible on a sticker. Fortunately, Windows provides built-in command-line tools like Command Prompt and PowerShell that can query system information, including the embedded product key. These methods are reliable and work across different Windows versions, primarily Windows 11 and 10, and often earlier versions like Windows 8.

It’s important to distinguish between license types. A Retail license is purchased separately and is generally tied to the individual who bought it. This allows for potential transferability to different hardware, subject to Microsoft’s licensing terms. Conversely, an OEM (Original Equipment Manufacturer) license is pre-installed by the computer manufacturer and is permanently tied to that specific machine’s hardware. The commands we will explore are particularly effective at retrieving the original OEM key embedded in the firmware, although they can sometimes retrieve retail keys stored in a similar manner or linked through specific system properties.

How to Find Windows 11/10 Product Key Using Command Prompt¶

The Command Prompt remains a powerful utility for system administration in Windows. To retrieve the product key embedded in your system’s firmware, you can use a specific command line interface (CLI) tool called Windows Management Instrumentation Command-line (WMIC). This tool allows you to perform administrative tasks and query information about your system through WMI. Accessing certain sensitive system information, like the product key, requires elevated privileges. Therefore, you must run the Command Prompt as an administrator.

To begin, open the Start menu and search for “Command Prompt”. Right-click on “Command Prompt” in the search results and select “Run as administrator”. If prompted by User Account Control (UAC), click “Yes” to allow the application to make changes to your device. Once the elevated Command Prompt window opens, you will see a black window with a prompt typically starting with C:\WINDOWS\system32>. This indicates you are running with administrative rights.

Now, type the following command exactly as shown and press the Enter key:

wmic path softwarelicensingservice get OA3xOriginalProductKey

Let’s break down this command:
* wmic: This invokes the Windows Management Instrumentation Command-line tool.
* path softwarelicensingservice: This specifies the WMI class we want to query. SoftwareLicensingService contains information related to the Windows licensing status and product keys.
* get OA3xOriginalProductKey: This is the action we want to perform. We are asking WMIC to get the value of the OA3xOriginalProductKey property from the SoftwareLicensingService class. The OA3xOriginalProductKey property specifically holds the original product key injected into the firmware by the OEM during manufacturing (often referred to as OA 3.0 activation).

Upon executing the command, the system will query the firmware for the embedded key. If a key is found in the BIOS/UEFI firmware, it will be displayed directly below the property name OA3xOriginalProductKey. The output will typically look like this:

OA3xOriginalProductKey
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

The sequence of letters and numbers starting with XXXXX represents your 25-character Windows product key. This key is the one originally associated with your hardware.

It’s important to note that this command specifically retrieves the key stored in the firmware. If your system was originally activated with this key but later upgraded (e.g., from Windows 8 to 10) or activated with a different retail key, the key displayed here will be the original OEM key, not necessarily the one currently active if a different key was used. This method is most reliable for finding the key on systems where Windows came pre-installed by the manufacturer.

If the command runs but displays a blank line or an error, it might indicate that no key is embedded in the firmware, which is common for systems built or assembled by the user, or those originally licensed via Volume Licensing or purely digital licenses not tied to OA 3.0 activation. In such cases, the product key might be stored differently, potentially linked to your Microsoft Account or recorded elsewhere.

Here is a quick summary of the command and expected output format:

Command	Description	Expected Output
wmic path softwarelicensingservice get OA3xOriginalProductKey	Retrieves the OEM product key from BIOS/UEFI firmware	OA3xOriginalProductKey [Your 25-character Key]

Using Command Prompt is a straightforward and effective way to access this specific piece of system information. It requires no external tools and leverages built-in Windows capabilities. Ensure you transcribe the command accurately to avoid errors.

Get Windows 11/10 License Key Using PowerShell¶

PowerShell is another powerful command-line shell and scripting language built on the .NET Framework. It offers more advanced capabilities compared to the traditional Command Prompt, especially for system management and automation. Similar to the Command Prompt method, PowerShell can also query the Windows Management Instrumentation (WMI) or the newer CIM (Common Information Model) to retrieve system information, including the embedded product key. Running PowerShell with administrative privileges is also required for accessing this licensing information.

To open an elevated PowerShell window, right-click on the Start button (or press Windows key + X) to open the WinX menu. Select “Windows Terminal (Admin)” or “Windows PowerShell (Admin)”. Confirm the User Account Control prompt if it appears. You will see a blue- 배경 window with a prompt, indicating you are running PowerShell with administrative rights.

In the PowerShell window, type the following command and press Enter:

(Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey

Let’s break down this PowerShell command:
* Get-WmiObject: This is a PowerShell cmdlet used to retrieve WMI objects. WMI provides a standard way to access management information from various parts of the operating system and hardware.
* -query 'select * from SoftwareLicensingService': This part specifies the WMI query. We are selecting all properties (*) from the SoftwareLicensingService class. This class contains detailed information about the Windows licensing service, including license status, activation details, and properties related to the product key.
* ( ... ): The parentheses group the result of the Get-WmiObject query.
* .OA3xOriginalProductKey: After retrieving the SoftwareLicensingService object, we access a specific property of that object using the dot notation. OA3xOriginalProductKey is the property that stores the original product key embedded in the system’s firmware (BIOS/UEFI), similar to the Command Prompt method.

When you execute this command, PowerShell retrieves the SoftwareLicensingService object and then extracts the value of the OA3xOriginalProductKey property. If the key is present in the firmware, PowerShell will display the 25-character product key directly in the output.

XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Similar to the Command Prompt method, this command specifically targets the key stored in the firmware (OA 3.0). If your system uses a different type of license (retail, volume, digital license not tied to firmware), this command might not return a key or might show a blank output. It is most effective for retrieving the factory-installed OEM key.

PowerShell offers more flexibility and can retrieve more detailed information about your licensing status. As mentioned in the original text, you can run the following command to get a comprehensive list of properties from the SoftwareLicensingService object:

Get-CimInstance -query 'select * from SoftwareLicensingService'

This command uses Get-CimInstance, the newer cmdlet for interacting with CIM (which is replacing WMI in modern Windows versions). It queries the same SoftwareLicensingService information and displays all available properties and their values. This output includes various details about your current license state, like the license status, grace periods, and other identifiers, though not necessarily the full currently active product key if it’s a retail key stored differently or a digital license. The OA3xOriginalProductKey property within this output will show the firmware key if present.

Here is a summary of the PowerShell command for the firmware key and the detailed information command:

Command	Description	Expected Output
(Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey	Retrieves the OEM product key from BIOS/UEFI firmware using WMI	[Your 25-character Key]
Get-CimInstance -query 'select * from SoftwareLicensingService'	Retrieves all licensing service properties using CIM (more detailed info)	A list of properties and values, including OA3xOriginalProductKey if available

PowerShell provides a robust way to query system information. Using Get-WmiObject or Get-CimInstance with the SoftwareLicensingService class is the standard method for retrieving licensing details programmatically. The OA3xOriginalProductKey property is the specific target for accessing the key embedded during manufacturing.

Understanding Where Your Product Key is Stored¶

The location and type of your Windows product key significantly influence how you can retrieve it and what you can do with it. As discussed, the two primary storage locations are the system’s firmware (BIOS/UEFI) and the Windows Registry.

Firmware (BIOS/UEFI): This is where OEM product keys are typically embedded on modern computers. When a manufacturer pre-installs Windows, they use a process (like OA 3.0) to inject a unique product key into the system’s firmware. This key is permanently associated with that specific motherboard. When you install or reinstall Windows on this machine, the installer automatically reads this key from the firmware and uses it for activation, provided you install the correct edition of Windows (e.g., Windows 11 Home vs. Pro) that matches the embedded key. The Command Prompt and PowerShell commands using OA3xOriginalProductKey are designed to retrieve this specific key from the firmware. This key is ideal for reactivating Windows on the original machine if you need to reinstall the operating system. It generally cannot be legally transferred to another computer.

Windows Registry: For retail licenses, or sometimes after upgrades, the product key or a derived activation ID is stored within the Windows Registry. However, Microsoft has implemented measures to prevent easy retrieval of these keys directly from the Registry in plain text. The key information is often encrypted or stored in a way that doesn’t reveal the original 25-character key directly through simple Registry viewing. This is why directly looking in the Registry keys like DigitalProductId requires decoding algorithms, which are complex and not easily performed with standard commands. The Command Prompt and PowerShell commands shown in this guide specifically target the firmware key (OA3xOriginalProductKey) and generally do not retrieve a retail key stored only in the Registry or associated with a digital license.

Digital Licenses: With Windows 10 and 11, Microsoft introduced the concept of digital licenses. A digital license is an activation method that doesn’t require you to enter a product key. Your Windows installation is activated based on your hardware configuration or linked to your Microsoft Account. If your Windows copy is activated via a digital license linked to your Microsoft Account, you generally don’t need the 25-character product key for reinstallation on the same hardware or on new hardware if transferring (for retail digital licenses). Simply signing in with your Microsoft Account after installation on the appropriate hardware will reactivate Windows. The commands retrieving the OA3xOriginalProductKey will still show the original firmware key if one exists, but it might not be the key currently being used for activation if you upgraded or used a different license type.

Understanding these differences is crucial. The methods using Command Prompt and PowerShell with OA3xOriginalProductKey are best suited for users of OEM machines trying to find the original pre-installed product key. If you have a retail license or your system uses a digital license, these commands may not yield the key you are looking for, or the key they retrieve might not be the one currently activating your system.

Limitations and Alternatives¶

While the Command Prompt and PowerShell methods using OA3xOriginalProductKey are effective for retrieving the OEM key embedded in firmware, they have limitations. They primarily target keys stored via the OA 3.0 process in BIOS/UEFI. They typically won’t retrieve:

• Retail keys purchased separately and entered during installation.
• Volume Licensing keys used in large organizations.
• Product keys associated purely with a digital license not tied to firmware (e.g., free upgrade from Windows ⅞).
• Keys on older hardware that predates the widespread adoption of embedding keys in firmware.

For scenarios where the command-line methods don’t work or don’t provide the desired key (like a currently active retail key), you might need to consider alternative approaches:

• Third-Party Software Key Finders: There are numerous free and paid third-party software tools designed to scan your system and retrieve product keys for Windows, Microsoft Office, and other software. These tools often employ more sophisticated techniques, including decoding Registry values or accessing other system information sources that the simple command-line methods do not. Popular examples include NirSoft’s ProduKey, Magical Jelly Bean KeyFinder, and ShowKeyPlus. When using third-party tools, always download them from reputable sources to avoid malware. These tools can often recover the currently installed key, even if it’s stored encrypted in the Registry.

• VB Script: As mentioned in the original article, it is possible to use VBScript (Visual Basic Script) to retrieve product keys. VBScript can interact with WMI and COM objects, potentially allowing access to product key information stored in the system. However, writing and executing VBScripts requires a bit more technical knowledge than running a simple command, and the scripts that can effectively decode the currently installed key from the Registry are often complex.

• Microsoft Account: If your Windows 10 or 11 digital license is linked to your Microsoft Account, the easiest way to manage activation, especially after hardware changes, is through your account online or via the Activation troubleshooter in Windows Settings. You won’t need the 25-character key in this case.

• Original Purchase Records: For retail licenses, your product key is usually provided on a sticker, a card in the product packaging, or in a confirmation email from an online purchase. Checking your original purchase records is often the most reliable way to find a retail key if it wasn’t linked to a Microsoft Account digital license.

• System Manufacturer: If you have an OEM system and the command-line methods fail, contacting the computer manufacturer’s support might be an option. They may be able to provide assistance in recovering the key associated with your specific hardware, although this is not always guaranteed.

Choosing the right method depends on the type of license you have and where it’s stored. For finding the original factory-installed key on most modern pre-built PCs, the Command Prompt or PowerShell methods are excellent and require no extra software.

What to Do After Finding Your Key¶

Once you have successfully retrieved your Windows product key using Command Prompt, PowerShell, or an alternative method, you can use it for several purposes:

1. Reinstallation: If you need to reinstall Windows on the same machine where the OEM key was found, having the key is useful, although often the installer will automatically detect it from the firmware. However, if you are using generic installation media or performing a clean install on a system that previously had a different Windows edition, manually entering the key might be necessary during or after setup.
2. Activation: If Windows somehow becomes deactivated (e.g., after a significant hardware change, though digital licenses handle this better now), you can use the retrieved key to reactivate it through the Windows Settings > Update & Security > Activation section.
3. Documentation: It’s always a good idea to keep a record of your product key in a safe place, separate from the computer itself. This could be a note, a text file stored on cloud storage, or even a physical copy. While digital licenses reduce the reliance on the key string, having it can be helpful for troubleshooting or in situations where the automatic activation process doesn’t work as expected.
4. Transferring License (Retail Only): If you found a retail product key and wish to transfer it to a new computer, you must first uninstall the key from the old computer. The original article mentions a post on how to uninstall a product key. This typically involves using the slmgr.vbs /upk command in an elevated Command Prompt or PowerShell. After uninstalling it from the old machine, you can then use the key to activate Windows on the new computer, subject to Microsoft’s licensing terms (which usually permit one active installation per retail key). OEM keys, remember, cannot be transferred.

Having your product key readily available can save you time and frustration if you encounter activation issues or need to reinstall Windows. The command-line methods provide a quick and easy way to retrieve the most common type of key found on modern pre-built systems.

Conclusion¶

Retrieving your Windows 11 or Windows 10 product key doesn’t have to be a daunting task. For most modern computers that came with Windows pre-installed, the product key is embedded in the system’s firmware (BIOS/UEFI) and can be easily accessed using built-in command-line tools. Both the Command Prompt, utilizing wmic path softwarelicensingservice get OA3xOriginalProductKey, and PowerShell, using (Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey, provide quick and effective methods to retrieve this original OEM product key.

These methods are particularly valuable for finding the key on systems where the traditional Certificate of Authenticity sticker is absent. While they primarily target the firmware-embedded key, understanding the type of license you have (Retail vs. OEM) and where it is likely stored (Firmware vs. Registry/Digital License) is key to knowing which retrieval method is appropriate for your situation. For retail keys or digital licenses, alternative methods like checking your Microsoft Account, purchase records, or using third-party key finder tools might be necessary.

Knowing how to find your product key empowers you to manage your Windows license effectively, facilitating reinstallation, activation, and troubleshooting. Whether you prefer the simplicity of Command Prompt or the flexibility of PowerShell, Windows provides the tools you need right at your fingertips.

Have you tried these methods to find your Windows product key? Did you encounter any issues, or did you find a different method more effective for your system? Share your experiences and questions in the comments below!