Also, because you’re installing updates for a system other than Windows XP, there’s the possibility that not all updates will work as intended. Naturally, there’s no way of knowing how long this trick will work - Microsoft could put a stop to it at any moment. This trick only works for 32-bit editions of XP, but there’s a workaround for 64-bit versions here. Windows will now automatically fetch updates designed for POSReady 2009, ensuring XP remains protected for the foreseeable future.
That will make that change to the registry. If it’s not showing up as a registry file, open any folder, go to Tools > Folder Options, select View and uncheck 'Show hidden files and folders'. reg is the proper extension - so not "XP.reg.txt". But a simple registry tweak is enough to fix that.Ĭreate a text document, and call it XP.reg.
You can’t simply install the updates - that would be too easy - and you’ll receive a version mismatch error if you try. This is based on Windows XP Service Pack 3, and the security updates which are being released for it are essentially the same ones Microsoft would have pushed out for XP, if it was still doing so. Meanwhile, the continuous support of Windows Embedded POSReady 2009 enabled some users to receive security updates on Windows XP Home and Professional SP3-based machines through the use of a. The workaround makes use of updates for Windows Embedded Industry (formerly known as Windows Embedded POSReady). 'The security updates that could be installed are intended for Windows Embedded and Windows Server 2003 customers and do not fully protect Windows XP customers.
0 kommentar(er)
