Change XP CD License Type


Recommended Posts

With Windows XP, there are three main types of licenses (Retail, Volume License, and OEM) for some Windows XP versions. With each type of CD, you can only use a product key that matches the CD. For example, if you own an OEM computer from a large company such as Dell, you cannot use a legally purchased XP CD from a store like best buy to perform a re installation of XP onto the OEM computer. Microsoft licensing is archaic, however luckily the difference between the license types is in an editable file. However with XP, you need to have the same type of CD to use this Process (So if you want to create an XP Pro OEM copy, you need any XP Pro OEM disc). To do this process, you need to follow these few steps.

1. Finding your ?Channel ID?

This is the number that determines what type of license the XP Disc is set to accept. We can determine this by inserting the disc (or mounting the ISO) on a computer, and then opening the folder ?I386? and look at the file called ?setup.ini? which should look similar to this

[Pid]

ExtraData=786F687170637175716954806365EF

Pid=76487000

The ?Pid? is the information we are interested in, and you should write it down for the next step. ?76487? are the first 5 characters which describe the locale, which in this case is ?English? (Media Center, XP Pro Royalty OEM, XP Pro SP2 retail and XP Pro Volume license). The main thing we are interested in is the last 3 characters which are ?000? describes the channel ID which in this case is ?Other / Retail / Upgrade / Evaluation?. We need to change these last 3 characters, in this case we are going to create an OEM CD and change the last 3 characters to ?OEM?. Here?s a short list of the Channel ID?s you can switch windows to. If you want to read more about the Channel ID?s, I suggest you check out the following site http://wiki.lunarsoft.net/wiki/Product_IDs

? 000 : Other (includes some retail, upgrade and evaluation versions)

? 006 : MS or Partner promotions

? 009 : Not for resale ? bundle

? 011 : Upgrade (XP Home?)

? OEM : OEM (This does not specify royalty or normal OEM)

? 270 : Volume License

? 335 : Retail

? 640 through 652 : Volume License

2. Changing your Channel ID

The first step to changing your Channel ID is to have an ISO image of the XP CD on your hard drive, and you must do this step before continuing. Most CD/DVD burning software offers an option to burn a copy of a CD to an image file. In order to proceed you also need have a HEX editor, I recommend XVI32 from this page http://www.chmaas.handshake.de/delphi/free...xvi32/xvi32.htm

After installing your HEX Editor, open up the ISO file. Hit CTRL+F in XVI32 and type the name of the PID from the first step and type OK. Your screen should now look like the below screen. (attached)

Modify the ?Pid=? value to have the last 3 characters to have the correct Channel ID, so if we wanted to create an OEM CD we would need to change ?000? to ?OEM?. It shouldn?t be necessary to change the first 5 characters

3. Saving and burning

You can save the file by pressing CTRL+S. It?s now safe to burn this image file with your favorite CD burning software. You should now be able to use a different license type and continue installing XP like you would with any other disc.

post-303202-1249566832.jpg

Link to comment
https://www.neowin.net/forum/topic/807478-change-xp-cd-license-type/
Share on other sites

For example, if you own an OEM computer from a large company such as Dell, you cannot use a legally purchased XP CD from a store like best buy to perform a re installation of XP onto the OEM computer....

I'm sorry, what? You say you can't just go and buy an XP CD and install it? Please explain...

I'm sorry, what? You say you can't just go and buy an XP CD and install it? Please explain...

This is more for people doing work that need to have multiple types of CD's on hand. For example, a PC Technician that fixes peoples computers. You would follow the licensing requirements, each PC would have a license. Let's say you have a customer with an older PC that has a Windows XP Pro w/ SP1 Retail copy, and all you have is an OEM disc. You can use this method to use your OEM Disc (Likely with sp3 slip streamed and all the good stuff) to install XP with a retail product key.

Also, this doesn't work with OLP (VLK) discs.

And, as Fish said, what you wrote about installing a retail CD on a Dell is nonsense. Of course you can.

I converted a VLK copy (have a volume licensing agreement with Microsoft) to an OEM copy, but haven't tried converting an OEM copy to VLK copy. Used this method to reinstall XP on computer that are surplus and being sold with using the OEM key when I couldn't find an OEM disc (besides stupid IBM / HP recovery discs).

  • 2 years later...

I made a small batch file that will replace key OEM files in the I386 folder of the CD that will allow the use of the corresponding OEM key so I carry a single copy of XP on a flash drive and just select the needed OEM and I'm all set. This flash drive goes everywhere with me.

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

    • No registered users viewing this page.
  • Posts

    • Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!