How to Find Your Windows 10 and 11 Product Key Using CMD

If you need to reinstall Windows or transfer your license to a new PC, you will need your 25-character product key. Instead of searching for old emails or physical stickers, you can instantly extract your product key directly from your computer's motherboard using the Command Prompt.

Here is the fastest way to find it:

Step 1: Open Command Prompt as Administrator

To access license data stored in the BIOS/UEFI, Windows requires "high-level" permissions.

1. Press Win + S on your keyboard to open the Search bar.

2. Type cmd in the search box.

3. Right-click on Command Prompt and select Run as administrator. Click Yes if a system window asks for permission.

---

Step 2: Enter the WMIC Command

Now you need to enter a specific command that tells the system to display the original key from the hardware.

1. Copy this exact text: wmic path softwarelicensingservice get OA3xOriginalProductKey

2. Go to the black window (Command Prompt).

3. Right-click anywhere inside the window to paste the command.

4. Verify that you see the full text and that the window title says "Administrator".

---

Step 3: Copy Your Product Key

After you press the Enter key, the system will process the request and show your unique code.

1. Hit the Enter key on your keyboard.

2. Your 25-digit Windows product key will appear on the next line in the format: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.

3. Highlight it with your mouse, press Ctrl + C to copy, and save it in a safe place.

---

Important Note

This method works best for computers that came with Windows pre-installed (OEM licenses). If the command returns a blank line, your license is likely Digital, meaning it is tied to your Microsoft account. In this case, you don't need a physical key — just log in to your account after reinstallation.

---

Related Articles:

• How to Change System Language in Windows 10 and 11

• How to Access the Hidden Power User Menu in Windows

---

Disclaimer: This guide is for informational purposes only. Proceed at your own risk. The author is not responsible for any system errors or data loss.