If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
keep XP updated until 2019
Ammammata wrote:
(what-ever) I posted the full details of this hack back on May 22 in a thread with the subject: "A few registry key entries will allow XP to update itself via Windows Update until the year 2019" For those that are too afraid or simply don't know about how this works - there is something that is really just an alternate version of XP-SP3 that Micro$haft calls "POSReady 2009". POSReady 2009. Nobody in a thousand years searching for XP related updates or hotfixes would ever think to search for "POSReady 2009". Very good move for Macro$haft to call it POSReady 2009 instead of "XP for POS 2009" or some such. POS means "Point of Service". It's what cash registers and bank teller computers are running. I think ATM's and gas pump machines too (as if they couldn't be running DOS). POS2009 came out in 2009 (I think that's when SP3 came out for XP). It will have full security updates for 10 years (hence EOL in 2019). POSReady 2009 is exactly the same as XP-SP3, but with a few trivial differences - such as no help files, DotNet installed by default, no Movie Maker, etc. You get the idea. Micro$haft will tell you that POS2009 and XP-SP3 are two different products. Of course they are! You take an XP CD, slap a new label on it, give it a new SKU or product number, -CREATE A SPECIAL LICENSE AGREEMENT FOR IT- and voila - you have a different product. Yes - the only real difference is the license agreement. And who here really pays attention to that stuff anyways? So the security updates and fixes that Milkro$oft will be making for POS2009 for the next 5 years are fully compatible with every XP-SP3 system out there. Meekro$oft will tell you that POS2009 updates ARE NOT INTENDED FOR XP - of course they're not! Not if Macro$haft had it's way and was in control of your computer! But of course you all realize that saying "not intended" is not the same thing as saying "they won't work". =============== A simple registry tweak is enough for WU to show the latest POSReady updates on Windows XP. This method has been tested and works on any XP build. Add the following registry keys (INF Format): HKLM,"System\CurrentControlSet\Control\WindowsEmbe dded\ProductVersion","FeaturePackVersion",0x000000 00,"SP3" HKLM,"SYSTEM\WPA\WEPOS","Installed",0x10001,0 HKLM,"SYSTEM\WPA\WES","Installed",0x10001,0 HKLM,"SYSTEM\WPA\POSReady","Installed",0x10001,1 Or use notepad to copy the following and save as .reg file and run it: ========== Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\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 recieve 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). To be on the safe side, you should probably be running XP-SP3 (but who wouldn't be?) and you might want to select "manual" updating and have a look at the updates and DO NOT EVER download anything called "WGA" or "Windows Genuine disAdvantage" if anything like that ever comes down the pipe. |
#2
|
|||
|
|||
keep XP updated until 2019
On Sat, 31 May 2014 22:24:11 -0400, XP Guy "XP"@Guy. com wrote:
Ammammata wrote: (what-ever) I posted the full details of this hack back on May 22 in a thread with the subject: "A few registry key entries will allow XP to update itself via Windows Update until the year 2019" For those that are too afraid or simply don't know about how this works - there is something that is really just an alternate version of XP-SP3 that Micro$haft calls "POSReady 2009". POSReady 2009. Nobody in a thousand years searching for XP related updates or hotfixes would ever think to search for "POSReady 2009". Very good move for Macro$haft to call it POSReady 2009 instead of "XP for POS 2009" or some such. POS means "Point of Service". It's what cash registers and bank teller computers are running. I think ATM's and gas pump machines too (as if they couldn't be running DOS). POS2009 came out in 2009 (I think that's when SP3 came out for XP). It will have full security updates for 10 years (hence EOL in 2019). POSReady 2009 is exactly the same as XP-SP3, but with a few trivial differences - such as no help files, DotNet installed by default, no Movie Maker, etc. You get the idea. Micro$haft will tell you that POS2009 and XP-SP3 are two different products. Of course they are! You take an XP CD, slap a new label on it, give it a new SKU or product number, -CREATE A SPECIAL LICENSE AGREEMENT FOR IT- and voila - you have a different product. Yes - the only real difference is the license agreement. And who here really pays attention to that stuff anyways? So the security updates and fixes that Milkro$oft will be making for POS2009 for the next 5 years are fully compatible with every XP-SP3 system out there. Meekro$oft will tell you that POS2009 updates ARE NOT INTENDED FOR XP - of course they're not! Not if Macro$haft had it's way and was in control of your computer! But of course you all realize that saying "not intended" is not the same thing as saying "they won't work". =============== A simple registry tweak is enough for WU to show the latest POSReady updates on Windows XP. This method has been tested and works on any XP build. Add the following registry keys (INF Format): HKLM,"System\CurrentControlSet\Control\WindowsEmb edded\ProductVersion","FeaturePackVersion",0x00000 000,"SP3" HKLM,"SYSTEM\WPA\WEPOS","Installed",0x10001,0 HKLM,"SYSTEM\WPA\WES","Installed",0x10001,0 HKLM,"SYSTEM\WPA\POSReady","Installed",0x10001, 1 Or use notepad to copy the following and save as .reg file and run it: ========== Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\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 recieve 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). To be on the safe side, you should probably be running XP-SP3 (but who wouldn't be?) and you might want to select "manual" updating and have a look at the updates and DO NOT EVER download anything called "WGA" or "Windows Genuine disAdvantage" if anything like that ever comes down the pipe. I'm saving this message for reference. This sounds useful. But I question whether one can activate this as a private individual. You did not post a URL to download it. BTW: Movie Maker can be downloaded separately from MS. If I install this, I sure hope my computer becomes an ATM and spits out lots of money! I'm sure glad you specified "Point of Service" or I would have thought it meant "Piece of ****"...... I know someone who refers to his car as a POS. |
#3
|
|||
|
|||
keep XP updated until 2019
|
#5
|
|||
|
|||
keep XP updated until 2019
Zo wrote:
Hey Guy, just curious - what is the difference between your recommended fix and the one suggested in this article from betanews? http://betanews.com/2014/05/26/how-t...xp-until-2019/ or Tiny URL= http://tinyurl.com/kxqk2th The difference is that the betanews article only gives this key: [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 as the olny key to add to your XP system so that it will download POSReady 2009 updates. Adding that key, and setting it's value to 1, is necessary for this method to work. The method I posted includes that key, as well as these additional keys: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WindowsEmbedded\ProductVersion] "FeaturePackVersion"="SP3" [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS] "Installed"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES] "Installed"=dword:00000000 The addition of those 3 keys has been found to suppress "Key Not Found" errors in the Windows Update log files during update sessions. There is some discussion of the possibly that having the WEPOS or WES keys set to 1 might also work by itself. |
#6
|
|||
|
|||
keep XP updated until 2019
XP Guy formulated on Tuesday :
Zo wrote: Hey Guy, just curious - what is the difference between your recommended fix and the one suggested in this article from betanews? http://betanews.com/2014/05/26/how-t...xp-until-2019/ or Tiny URL= http://tinyurl.com/kxqk2th The difference is that the betanews article only gives this key: [HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady] "Installed"=dword:00000001 as the olny key to add to your XP system so that it will download POSReady 2009 updates. Adding that key, and setting it's value to 1, is necessary for this method to work. The method I posted includes that key, as well as these additional keys: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\WindowsEmbedded\ProductVersion] "FeaturePackVersion"="SP3" [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS] "Installed"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES] "Installed"=dword:00000000 The addition of those 3 keys has been found to suppress "Key Not Found" errors in the Windows Update log files during update sessions. There is some discussion of the possibly that having the WEPOS or WES keys set to 1 might also work by itself. Really appreciate the reply, Thank you very much. -- Zo Isn't it a bit unverving that doctors call what they do, PRACTICE. |
#7
|
|||
|
|||
keep XP updated until 2019
|
#8
|
|||
|
|||
keep XP updated until 2019
On Sun, 1 Jun 2014 04:54:17 +0100, "J. P. Gilliver (John)"
wrote: There isn't anything to download: if you read what he said, there are only four registry keys to be created/altered, but if you don't want to do that, he made it as a .reg file: you copy the bits _of his post_ between the === lines into NotePad, then save the result as a .reg file, then run it. (On your head be it though!) [Use his original post - or, if you take the text from this one, remove all the ""s.] [] -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Ok, I now understand. It's using the already installed copy of XP. Just modified to get the updates. I hope that also updates Security Essentials. I'm sick of that thing nagging me that XP is expired. |
#9
|
|||
|
|||
keep XP updated until 2019
|
#10
|
|||
|
|||
keep XP updated until 2019
On Sun, 01 Jun 2014 01:22:16 -0400, XP Guy "XP"@Guy. com wrote:
wrote: I hope that also updates Security Essentials. I'm sick of that thing nagging me that XP is expired. Apparently, Microsoft dropped support for POS Ready 2009 with version 2 of Security Essentials. MSE is only supported on XP 32-bit, and vista/w7 32 and 64-bit. It is not supported on any other platforms. That's too bad. Security Essentials (SE) seemed to be one of the best AV programs available, at least of the free ones. I suppose I may as well just uninstall it then. I guess I'll have to buy Kaspersky then. I'm not impressed with any of the free ones. In fact AVG claims to run on Windows 2000 SP4. That's what I have on one computer, yet it wont install. I guess when it comes to something as important as AV software, one cant be cheap. However I wont touch anything made by Symantec. I always figured that MS would make the best AV, since they know the OS best. |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
More updated driver, anyone? | Jack | Nvidia Videocards | 2 | July 3rd 05 06:50 PM |
updated to 53.03 BAD IDEA!!! | KM | Nvidia Videocards | 12 | January 24th 04 11:35 PM |
Updated drivers? | Jbob | Nvidia Videocards | 5 | October 7th 03 03:09 PM |
Updated FX5600 | Thomas Andersson | Nvidia Videocards | 1 | June 26th 03 01:15 AM |