The legendary Windows XP key: what Microsoft Bob had to do with it

Dave Plummer, who worked on Windows Product Activation on the operating-system side, shared his recollections of the famous Windows XP key beginning with FCKGW. He distinguishes his work on OS integration and protection from the mathematics used to validate product keys.

Why corporate customers needed volume keys

Large corporate customers needed to install Windows on many computers, including offline machines. According to Plummer, special Volume Media paired with a volume key allowed them to skip ordinary activation on each computer. These were licensing channels, not a claim that XP had only two editions.

Microsoft Bob’s unexpected role

The volume media contained a special data block of about 10 MB. Plummer says he used Microsoft Bob disc data, compressed and encrypted several times, for checking the media against the key. Activation code was not hidden inside Bob; Bob data was used in the XP media check.

A leak before the retail launch

Plummer recalls that XP reached manufacturing on 24 August 2001, ahead of its 25 October retail launch. Roughly five weeks before launch, Devils0wn distributed a corporate image with a working key. The key was valid, rather than a mathematical crack.

He considers an early recipient of the final media a plausible source, but does not know who leaked it. His account does not establish responsibility for any particular company.

What Microsoft blocked

Microsoft later blacklisted product identifiers associated with leaked keys. Plummer describes FCKGW as belonging to a 640-range Product ID; 640 is not a count of other blocked keys. Microsoft documentation confirms that publicly leaked volume keys could prevent installation of XP SP1 and later service packs or access to automatic updates.

The Microsoft Bob details are attributed to Plummer’s recollections. Microsoft documentation independently confirms that keys must match installation media and that leaked keys could face restrictions. The story illustrates how a convenient deployment mechanism became a problem when a genuine key and matching image escaped.

Additional official source: Microsoft Learn, How to change the Volume Licensing product key: https://learn.microsoft.com/en-us/troubleshoot/windows-server/licensing-and-activation/change-volume-licensing-product-key

Image: Дэйв Пламмер, скриншот публикации в X

Translation editors: Соловьев В., Пеков А.