Generic install key being detected as OEM key

Coke Robot

New Member
Pro User
Gold Member
Messages
5,707
Well hello all!

I'm having a strange issue with a laptop I'm trying to get back up and running. It's a Toshiba laptop that came with Windows 8 with it, obviously UEFI and an embedded key. The person that was using it said it started to act up a week before it fully crashed. Afterwards, it wouldn't boot up, it would either BSOD with an error code I found pertaining to a graphics driver error, or stay on a blue screen with nothing on it and then restart and go through an endless Automatic Repair loop with no success. I check the logs and Windows checked EVERYTHING but couldn't find the issue why it wasn't booting. Did chkdsk, bootrec repair, offline sfc scan, STD scan, tried refresh/reset but the drive was apparently locked, couldn't do a system restore as there weren't any restore points, tried doing startup repair four times; nothing worked.

So I decided it would have to be wiped and reinstalled with 8.1. Thought it would be an easy process. I used the vbs script to show the OEM key to activate Windows once I was up and running with 8.1. OK, but for some reason the key looked familiar. Keyed in the key, it didn't work. So I wiped that hard drive with Windows 8.0, ran the vbs script, SAME key of Windows 8 Pro as before. Odd. I already tried converting the 8.1 Core OEM I previously installed to 8.1 Pro and tried that key, still nothing.

Then I checked the key on the interwebs, XKY4K-2NRWR-8F6P2-448RF-CRYQH, the reason why it looked so familiar is because it's a generic install key for Windows 8/8.1! This isn't the OEM key at all!

I deploy Windows with a custom 8.1 .wim image and have used this several times already and I THINK I might have that key used originally to install Windows into my virtual machine I have going for it. My thinking was that I might have used sysprep one too many times, but that doesn't explain why even with the plain Windows 8 AND 8.1 Core images why the key that's being detected is a generic install key.

So this is potentially a major problem and haven't even encountered this issue at all. I can't find a lick of information about something like this anywhere.

Any suggestions or advice are appreciated as always!
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
vbs ?

Is this the vbs script you used ?

http://www.eightforums.com/tutorials/27129-product-key-find-windows-8-a.html

View attachment ShowKey v1.3.vbs

screenshot_90.jpg
 
Last edited by a moderator:

My Computer

System One

  • OS
    Windows 8.1.1 Pro with Media Center
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Gateway
    CPU
    AMD K140 Cores 2 Threads 2 Name AMD K140 Package Socket FT1 BGA Technology 40nm
    Motherboard
    Manufacturer Gateway Model SX2110G (P0)
    Memory
    Type DDR3 Size 8192 MBytes DRAM Frequency 532.3 MHz
    Graphics Card(s)
    ATI AMD Radeon HD 7310 Graphics
    Sound Card
    AMD High Definition Audio Device Realtek High Definition Audio USB Audio Device
    Monitor(s) Displays
    Name 1950W on AMD Radeon HD 7310 Graphics Current Resolution 1366x768 pixels Work Resolution 1366x76
    Screen Resolution
    Current Resolution 1366x768 pixels Work Resolution 1366x768 pixels
    Hard Drives
    AMD K140
    Cores 2
    Threads 2
    Name AMD K140
    Package Socket FT1 BGA
    Technology 40nm
    Specification AMD E1-1200 APU with Radeon HD Graphics
    Family F
    Extended Family 14
    Model 2
    Extended Model 2
    Stepping 0
    Revision ON-C0
    Instruction
    Browser
    Opera 24.0
    Antivirus
    Avast Internet Security
Yep, that is exactly the .vbs script I used. To make sure it wasn't the script being weird, I ran it on my machine and it showed the key that I do have installed and activated so it's not that.

I'm thinking, this is really out there on a limb, that somehow the generic key is flashed into the BIOS. I literally ran four different SKUs of Windows 8, 8.0 Core, 8.0 Pro, 8.1 Core, and 8.1 Pro; but ALL showed the same generic install key as what's in the system. All of them were the base images as well so that clears out my custom sysprepped 8.1 image.

Also, I tried the Belarc system advisor and it showed no key installed for Windows 8.0.

This is the oddest issue I've ever seen happen with Windows 8 by far. Cake may be awarded to this.

I'm going to try and make a bootable USB drive of Windows 8 Core and do it that route. Maybe the DISM deployment might be going weird...
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
Hey Andy,

Did you already try doing a clean install of Windows 8 at boot to see if it may detect the embedded Windows 8 key?

It'll only detect the key if the OS is for the exact same edition the key is for.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
Yep. I rewiped the hard drive each time and deployed a clean install image of each different version of Windows to check. Normally with new PCs that 8.0 installed, Windows 8 will detect the key and be happy and won't prompt for a key. Except every time I ran 8.0 on the laptop, I was prompted for the key.

The laptop came preinstalled with Windows 8.0 Core. Running even with that accompanying OS didn't take the key nor show the correct key but the generic installer key.

I'll post back when I try making the USB install drive and doing it that route, but I need to run out and get a couple flash drives! Them prices are cheap! :geek:
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
Shot in the dark here, any chance if a hardware switch was done or BIOS update gone wrong?
 

My Computer

System One

  • OS
    windows 8.1 Update 1 Pro 64bit
    System Manufacturer/Model
    Pavillion H8-1202
    CPU
    I7-2600 @ 3.4 GHz
    Motherboard
    PEGATRON
    Memory
    8 GB
    Graphics Card(s)
    NIVDIA GeForce GT 520
    Sound Card
    Realtek ALC656GR CODEC
    Monitor(s) Displays
    Samsung SyncMaster S22B350
    Screen Resolution
    1920X1080 32 bit color
    Hard Drives
    Samsung 850 EVO SSD 500GB
    Keyboard
    Razer Blackwidow Ultimate 2013
    Mouse
    Logitech M510
No hardware I'm aware of was changed since it's a laptop, and I doubt a BIOS update was even done since the laptop in question is used for simple tasks.
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
Yep. I rewiped the hard drive each time and deployed a clean install image of each different version of Windows to check. Normally with new PCs that 8.0 installed, Windows 8 will detect the key and be happy and won't prompt for a key. Except every time I ran 8.0 on the laptop, I was prompted for the key.
If it is prompting for the key during the install, that means the embedded key doesn't match the version of Windows that you are attempting to install. If you want to truly see what the embedded OEM key is, you have to install a copy of Windows 8.0 that will simply install without prompting you to enter any key.

I've been able to use the DVD's provided by Dell with my Dell's in my office and my Acer's. I can also use my MSDN copy without it asking me for a key during install.
 

My Computer

System One

  • OS
    Windows 7
    System Manufacturer/Model
    Self-Built in July 2009
    CPU
    Intel Q9550 2.83Ghz OC'd to 3.40Ghz
    Motherboard
    Gigabyte GA-EP45-UD3R rev. 1.1, F12 BIOS
    Memory
    8GB G.Skill PI DDR2-800, 4-4-4-12 timings
    Graphics Card(s)
    EVGA 1280MB Nvidia GeForce GTX570
    Sound Card
    Realtek ALC899A 8 channel onboard audio
    Monitor(s) Displays
    23" Acer x233H
    Screen Resolution
    1920x1080
    Hard Drives
    Intel X25-M 80GB Gen 2 SSD
    Western Digital 1TB Caviar Black, 32MB cache. WD1001FALS
    PSU
    Corsair 620HX modular
    Case
    Antec P182
    Cooling
    stock
    Keyboard
    ABS M1 Mechanical
    Mouse
    Logitech G9 Laser Mouse
    Internet Speed
    15/2 cable modem
    Other Info
    Windows and Linux enthusiast. Logitech G35 Headset.
OK, I figured it out! Using the bootable UEFI USB install drive with Windows 8 Core worked. It didn't prompt for keys and activated right off the bat and NOW I have the proper key to use for the new 8.1 image I'll deploy and activate.

Now this begs the question, what went wrong? I was using DISM to deploy the plain vanilla .wim files from the Windows 8 Core and Pro as well as 8.1 Core and Pro and none of them worked and must have had the generic key associated with the .wim files. None of what I tried out were any custom images I made, all MSDN images. It was a simple command of DISM /Apply-Image /ImageFile:D:\install.wim /index:1 /ApplyDir:W:\.

Very strange...this is the first time in the few dozen deployments I've done with Windows 8 that this has ever happened...
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
I believe that for it to detect the embedded OEM key the installation needs to be done at boot.
 

My Computer

System One

  • OS
    64-bit Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Custom self built
    CPU
    Intel i7-8700K OC'd to 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G7 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO PRO M.2,
    8TB WD MyCloudEX2Ultra NAS
    PSU
    OCZ Series Gold OCZZ1000M 1000W
    Case
    Thermaltake Core P3
    Cooling
    Corsair Hydro H115i
    Keyboard
    Logitech wireless K800
    Mouse
    Logitech MX Master 3
    Internet Speed
    1 Gb/s Download and 35 Mb/s Upload
    Browser
    Internet Explorer 11
    Antivirus
    Malwarebyte Anti-Malware Premium
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    APC SMART-UPS RT 1000 XL - SURT1000XLI,
    Galaxy S23 Plus phone
This is true, but I've done DISM deployment on several Windows 8 UEFI PCs and this is the first time anything like this has happened.

Usually my deployment process involves my custom image that was installed in a VM with a generic installer key. I sysprep that image with an unattend.xml file but with no product key whatsoever slipstreamed in, and is set to start up at OOBE. Then, after the target hard drive is set up, I use DISM to deploy the custom image, boot the target PC to WinPE and apply boot files, restart it, and let it do its jazz. With Windows 8 PCs and 8.0, there wasn't any issues with activation and the embedded keys. Going to 8.1 required pulling the key and manually entering it in. I've done this many times now and it's gone screwy for the first time ever.
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model
    ASUS
    CPU
    AMD FX 8320
    Motherboard
    Crosshair V Formula-Z
    Memory
    16 gig DDR3
    Graphics Card(s)
    ASUS R9 270
    Screen Resolution
    1440x900
    Hard Drives
    1 TB Seagate Barracuda (starting to hate Seagate)
    x2 3 TB Toshibas
    Windows 8.1 is installed on a SanDisk Ultra Plus 256 GB
    PSU
    OCZ 500 watt
    Case
    A current work in progres as I'll be building the physical case myself. It shall be fantastic.
    Cooling
    Arctic Cooler with 3 heatpipes
    Keyboard
    Logitech K750 wireless solar powered keyboard
    Mouse
    Microsoft Touch Mouse
    Browser
    Internet Explorer 11
    Antivirus
    Windows Defender, but I might go back on KIS 2014
Back
Top