create a txt file and put the following in: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 rename it to : update.reg and execute it. Windows xp will be reconized as Windows pos ready
more info This is what I have found on this: "Use notepad to copy the following and save as .reg file - and then run it (double-click the file). ========== Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion] "FeaturePackVersion"="SP3" [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS] "Installed"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES] "Installed"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 =========== Restart your computer, and make sure WindozeUpdate service is running. You will see there are updates for you to install! And your XP PC will continue to receive MS patches until the year 2019. This is for 32-bit XP. There is a different method for 64-bit version of XP (by spoofing Windows 2003 server). This trick works because for the purposes of WindowsUpdate, it makes WU think you're running POS2009 (Point Of Service 2009) which is basically XP for cash registers and other "point-of-service" PC's. Microsoft provides update support for POS2009 until 2019."
I'm glad : Will these updates make XP 'safe' to go on the internet? . . My machines are old , so why would I want to update the OS when the machine boots fine into WinXP -- just do not go onto the internet in XP in the future. . At present I installed a RHEL clone (SL) in dual-boot on all of my machines that go onto the internet , but it would be useful sometimes to use WindOS.
"These changes give your PC the ability to continue to receive updates, patches and fixes directly from Microsoft via Windows Update until the year 2019"...so I would say "yes"! M$'s Official Comment: neowin.net/news/microsoft-warns-against-registry-hack-that-allows-windows-xp-updates (C/P I am forbidden to link!!!)
Ive forgotten the name of what it is- but one of the things is XP is best to use when trying to hack up a program. Seen a dude reverse engine the activation process on a program.
MS just wants people to pay for Windows 8 that's all. Of course they would say that. We all know better.
Huge, HUGE THANKS for sharing this information. Got my first updates since April-2014. (winXP-SP3 PRO) PS Does it matter which one of the three possible types of string parameters the FeaturePackVersion should actually be? (I made it the REG_SZ type)
Hah, looks like I did it the hard way. I was approaching it from trying to "change" the operating system to a different edition, with the difficult offline registry hack to the ProductSuite that crashed more often than it worked. The simpler one reported by theregister and other sources works good enough for now.
Well that's not entirely true, Windows embedded POS is Windows XP yes but it has a bunch of components removed from it. This means that those components will not receive updates so you can't say that it will be safe for sure. You are better off installing Windows embedded POS if you want to continue running XP as then you don't have to worry about any compatibility issues and unsupported components. forums.mydigitallife.net/threads/40191-Windows-Embedded-POSReady-2009 lol can't post links to threads inside their own forums cause less than 10 posts so copy/paste
The latest I got from another forum was that XP became "non genuine" (after a week) and would not update...I will see how it goes on my old set-up?!
Also found this from omeHomeGuy: "There are ABSOLUTELY NO OTHER REPORTS of other systems experiencing WGA failures because of using the POS2009 hack. What also could have happened is that when you were performing the WindowsUpdate check, you chose "Automatic" instead of "Custom", and by choosing automatic you did not pick and choose which updates were being downloaded, and you downloaded one of those WGA validation checks and your system failed the check (which happens many times, even on legit systems). I always tell people who manually update XP to never download the WGA "Genuine Validation" update, and to de-select it from the update list so the system will never download it even when they switch to automatic instead of custom update. "