Restore CD's and Vista Product Keys


Recommended Posts

You all know the recovery CD's that come with new computers? They don't contain the windows product key do they, since when you do a recovery it won't prompt for a windows key? Where is the product key stored then if not on the CD? Will it prompt for a key if all partitions have been erased, such as the hidden "toshiba" partition or something like that?

Just a quick question :) Thanks for the info

Link to comment
https://www.neowin.net/forum/topic/587659-restore-cds-and-vista-product-keys/
Share on other sites

Hello RGSPro,

Yes, new computers usually come with a recovery CD containing the operating system. The product key itself isn't really "stored" on the CD. It's actually a sticker on the case of a PC or under a laptop. Also, running a repair installation requires a valid Windows product key. The Windows setup will prompt for a product key even if the partition has been formatted.

The product key sticker usually looks like this:

xp_key.jpg

Hi RGSPro,

I understand what you're saying now. Usually, the recovery CD contains an image of the HD when it shipped (factory settings). The advantage to that is you can easily restore the default factory settings without any hassle. You won't have to manually install drivers and applications one by one which makes things simple for the end user. The drawbacks include the inability to select which applications you want to be installed, and the lack of driver flexibility. Changing components can often cause the recovery CD drivers to fail.

Anyway, I doubt your recovery CD uses SLP (System Locked Preinstallation). It's merely a preactivating procedure used by manufacturers before the operating system is distributed, meaning that the activation process is done as soon as you boot up the machine. Keep in mind SLP discs still require a unique product key, but recovery discs don't.

I believe that the product key is actually in the cmos chip. When the os installs it checks the cmos and picks up the key from there. You cannot use another companies oem install disk since the software on the disk only picks up the key for that particular brand.

This is why I use the latest Dell Windows XP disk from Dell when I re-install XP on an older Dell that came with XP. Instead of the customers original XP which may not have any Service Paks, I can now get SP 2 already installed. This only works by matching a Dell Home with a machine that came with Home and a Professional disk on a computer that came with Pro. Same with MCE.

This is the way it worked on XP, and I assume it is the same on Vista.

I believe that the product key is actually in the cmos chip. When the os installs it checks the cmos and picks up the key from there. You cannot use another companies oem install disk since the software on the disk only picks up the key for that particular brand.

This is why I use the latest Dell Windows XP disk from Dell when I re-install XP on an older Dell that came with XP. Instead of the customers original XP which may not have any Service Paks, I can now get SP 2 already installed. This only works by matching a Dell Home with a machine that came with Home and a Professional disk on a computer that came with Pro. Same with MCE.

This is the way it worked on XP, and I assume it is the same on Vista.

Thats rubbish, XP and Vista OEM look for a certain string in the BIOS that matches the required string on the installation CD.

On an XP CD they "real product key" is stored in the winnt.sif file in the i386 directory.

What it is, is a unattended install file configured to automatically enter the product key.

Further editing of the winnt.sif file will allow you to automatically answer all the install questions so you just pop in the disc and wait for it to finish.

On a "royalty" OEM machine the COA sticker has a dummy key which is deactivated.

The key is a volume key that only works if the OEMBIOS files on the CD find a qualifying motherboard.

---

Something similar exists for Vista.

I know its not the same system as XP.

I know there there are volume keys and systems are activated if the motherboard qualifies.

I have hear that unlilke the old system spoofing the existence of a qualifying motherboard is easy and is how most people pirate vista.

When I start having to reinstall OEM Vista boxes I will probably have to learn how the new system locked preactivation system works.

---

I have seen restore CDs that were nothing more or less than XP install CDs modified to install additional software and drivers, like you would create for your self. Others are backup images similar to what you would create using True Image and one click restore.

If there is an i386 folder then its definitely a custom install CD.

Again XP knowledge that might not carry over to Vista!

I believe that the product key is actually in the cmos chip. When the os installs it checks the cmos and picks up the key from there. You cannot use another companies oem install disk since the software on the disk only picks up the key for that particular brand.

This is why I use the latest Dell Windows XP disk from Dell when I re-install XP on an older Dell that came with XP. Instead of the customers original XP which may not have any Service Paks, I can now get SP 2 already installed. This only works by matching a Dell Home with a machine that came with Home and a Professional disk on a computer that came with Pro. Same with MCE.

This is the way it worked on XP, and I assume it is the same on Vista.

Actually, SLP enabled discs check for a text string in the BIOS. If it finds a match then the user is not prompted to activate Windows XP. I'd say you're using a standard Dell OEM disc.

BTW CD Key is 100% not on the CMOS or stored anywhere in the BIOS on both XP and VISTA.

And if it a royalty OEM the CD key on the sticker is 100% factory disabled. You can call to have it activated if needed.

It is always on the Disc in some form or another (install CD w answer file or backup image of installed OS).

My old compaq laptop- model 2105us, came with a 4 disc recovery set as well as an XP home install disc. Depending on what I wanted, I could use the recovery disc set or I could use the XP install disc.

In the first case, the version of XP installed was an OEM version, and the recovery wiped all partitions off the drive and reinstalled everything from a compressed image spanning those 4 discs and was pre-activated- no need to contact Microsoft to start using it or installing updates. In the second case, which was the equivalent of a retail XP home disc- right down to the file sizes and date and time stamps (on the few dozen files I checked), I had all the normal XP installation options and had to input the key from the COA and go online or phone Microsoft to activate it- it was not an invalidated / inactive / disabled key- it activated over the Internet the first time I used it.

My experience is that computer companies have various ways to provide recovery options. Some provide install discs for everything- OS and software, some provide recovery discs like I mentioned above, and some have hidden partitions that use a special CD to copy the recovery partion over to the main partition. Sometimes, different computers from the same manufacturer use different methods as well.

Often, the recovery software looks for specific strings in the BIOS like system make or model or the like, chipset type, etc., and if that information is not found, or doesn't match what the software expects, aborts the recovery. That is why you most likely cannot use a Dell recovery disc set on an HP or other computers, and sometimes can't use a Dell set on a different Dell.

Technically, the install key is not stored anywhere on the hard drive or in the system on any XP or Vista computer, unless you've typed it in and saved a text file or something. The registry contains what is an encrypted version of it so it cannot be easily copied and used on another computer. If I remember correctly, this is why major hardware changes require re-activation since hardware devices are used to generate the encrypted key and changing certain devices or changing devices too often cause the key to be recalculated and require re-validation.

Thats rubbish, XP and Vista OEM look for a certain string in the BIOS that matches the required string on the installation CD.

Uh, isn't that what I said? And since you can use ANY Dell disk on any Dell computer how does the product key MATCH the key on the machines sticker if you use a disk from a different Dell machine?

Ipso facto, it must be on the bios chip.

At least thats what the NE Regional Director of Microsoft told me a couple of years back at a MS event.

Uh, isn't that what I said? And since you can use ANY Dell disk on any Dell computer how does the product key MATCH the key on the machines sticker if you use a disk from a different Dell machine?

Ipso facto, it must be on the bios chip.

At least thats what the NE Regional Director of Microsoft told me a couple of years back at a MS event.

Sorry, but that doesn't make any sense. If the key on the COA is in the BIOS, then every BIOS must have the same key for the same version of Windows. But I have seen multiple Dell computers, each with different keys on the COA sticker- some Win2k, some XP home, some XP Pro, some Vista, that would NOT let a Dell recovery installation run from a different computer.

By logical conclusion, that fact itself- 'ipso facto' if you will, means the key is NOT in the BIOS.

Maybe there is a sting in the BIOS, some hardware identifier that the recovery looks for that allows it to run?

Sorry, but that doesn't make any sense. If the key on the COA is in the BIOS, then every BIOS must have the same key for the same version of Windows. But I have seen multiple Dell computers, each with different keys on the COA sticker- some Win2k, some XP home, some XP Pro, some Vista, that would NOT let a Dell recovery installation run from a different computer.

By logical conclusion, that fact itself- 'ipso facto' if you will, means the key is NOT in the BIOS.

Maybe there is a sting in the BIOS, some hardware identifier that the recovery looks for that allows it to run?

I don't understand your reasoning. Every network card has a different mac address number. It is quite easy to merely install a unique product key into the bios.

What everyone here is missing is that different Dell disks, at least on XP, when installed on a different machine than they came with, still show the product key that is on the case once you have installed XP and used a utility like Keyfinder to see the product key. Therefore the product key MUST be in the hardware of the machine. And the bios, being made of eeeprom is the perfect place.

I routinely turn generic OEM CDs into Royalty OEM CDs, at least several times a month, its faster than requesting a CD from the manufacturer.

---

In the factory all the computers with XP Home get the same SLP key.

Then they slap a COA sticker on with a unique key.

On a Royalty OEM CD the SLP volume key is stored in the in the winnt.sif file in the i386 folder.

winnt.sif is a text file that when present in the i386 folder or on a floppy, will automate parts or all of the install process including entering a the product key.

The System Locked Preactivation part happens when XP first runs.

The Royalty OEM CD has special files (named OEMBIOS.*). XP will automatically use these files to see if you have installed on a recognized motherboard.

If you have then windows XP will automatically activate without having to contact MS.

There is no special code stored in the BIOS. Instead XP judges the BIOS based on the OEMBIOS files. Usually it looks for a specific string "DELL" for instance at a specific location.

If you hacked your BIOS to make it say "DELL" at that location then you can pirate XP by simply using a DELL install CD, and it will 100% fool Microsoft.

Of course simply overwriting a specific of your BIOS with the string "DELL" would make your computer an expensive paper weight.

A very accomplished assembly language programmer with way too much time on your hands could rewrite the BIOS to move the code around and make room for the insertion.

Its been done, but for the same skill and effort you could probably earn enough money to buy a dozen legal copies of XP.

-----

The SLP keys for each version of XP (Home, Pro, MCE) are universal. You can use a Dell Key on a HP for instance.

The OEMBIOS are often universal within a brand. So an OEMBIOS file for a new Dell usually works on all previous dells.

The key on the sticker is disabled by default. Otherwise people could just copy them in the stores.

However if you install from a CD that isn't setup to use SLP, or you change motherboard so that SLP will no longer work you can call and ask Microsoft to enable that key.

If you installed using an SLP key, but the OEMBIOS didn't match the motherboard you have to change keys.

---

I have unmodified copies of Home, Pro and MCE 2005 on my hard drive.

I use a batch file to retrieve the OEMBIOS file from hard drive of the royalty OEM computer.

I then add these to the i386 folder.

I open winnt.sif and uncomment the slp product key for the proper version of windows and copy it to the i386 folder.

I burn the CD with nero, making sure to get the boot image settings right.

I now have a royalty OEM install CD and when I don't have to answer any questions during the install process and when XP automatically activates the first time it boots.

The product key on the COA sticker never gets used.

If I just replaced the motherboard with one not from the original manufacture I would have to change to the COA sticker on the product key to call Microsoft.

This isn't something I am guessing about. This is something I work with every time I do a clean install on a Royalty OEM system.

(Royalty means MS lets them make their own customized install CDs and pay a royalty fee)

Sorry if the post is long and rambling.

Edited by Codesmith
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!