Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



glnz

POSReady 2009 updates ported to Windows XP SP3 ENU

Recommended Posts

glnz    20

First, before making the registry change below, you should download and install Microsoft's updated Windows Installer 4.5 (KB942288-v3) from THIS LINK for Windows XP 32-bit, which is what we assume you have.  (The MS article that explains this updated installer is HERE.)

Next, copy the text given by @Sebijk (below) to notepad and save it as POSReady.txt
Make sure what you copy starts with the "Windows..." line and has two blank lines after the line that ends in "00000001"
Rename the file POSReady.txt to POSReady.reg, right-click on it, select "Merge", then "Yes".
Reboot the system.

On 5/21/2014 at 2:54 PM, Sebijk said:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001

and POSReady2009 Updates will install on XP + Windows Update [then] shows the updates for POSReady 2009 :)

=================######=================

Direct Links to WU/MU (just in case...):

for Windows Update	http://update.microsoft.com/windowsupdate
for Microsoft Update	http://update.microsoft.com/microsoftupdate

=================######=================

'Nuff said!

Edited by glnz

Share this post


Link to post
Share on other sites

harkaz    25
On 2/14/2016 at 2:37 AM, dencorso said:

Some relevant links to threads derived from this one, as time goes by:

1. The EMET thread;

2. The Root Certificates and Revoked Certificates thread;

3. TBA.

On 5/22/2014 at 3:38 PM, dencorso said:

And for anyone who, like me, prefers reg files, here is the Myrrh-Sebijk-Harkaz trick in .reg form:

 


Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded]

[-HKEY_LOCAL_MACHINE\SYSTEM\WPA\WEPOS]

[-HKEY_LOCAL_MACHINE\SYSTEM\WPA\WES]

[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001

On 1/26/2016 at 10:59 PM, dencorso said:

It can be removed afterwards, too. But one has to remove Myrrh-Sebijk-Harkaz trick from the cold (unbooted) system, by using a live CD. That's described in this post.

 

Of course, there's a simpler version of it:

On 5/21/2014 at 3:54 PM, Sebijk said:

there is a much easier way:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady]
"Installed"=dword:00000001


 

and POSReady2009 Updates will install on XP + Windows Update shows the updates for POSReady 2009 :)

NOTE [08/03/2016]: All SP4 users up to including version 3.1a must delete the following key to continue receiving the latest updates automatically from WU:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded

Direct Links to WU/MU:

for Windows Update	http://update.microsoft.com/windowsupdate
for Microsoft Update	http://update.microsoft.com/microsoftupdate

=================######=================

 

UPDATE [22/5/2014]: Sebijk reported that 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\WindowsEmbedded\ProductVersion","FeaturePackVersion",0x00000000,"SP3"

HKLM,"SYSTEM\WPA\WEPOS","Installed",0x10001,0

HKLM,"SYSTEM\WPA\WES","Installed",0x10001,0

HKLM,"SYSTEM\WPA\POSReady","Installed",0x10001,1

 

and restart the computer. Then run WU to get the latest updates.

 

ORIGINAL METHOD:The latest Patch tuesday updates have been easily ported to a Windows XP virtual system - fully updated until April 2014.

 

The constraints are entirely artificial. Porting is easy as 1-2-3:

 

1. Modify update.inf file and remove the

 

condition=CompositeOp,OrOp,Prereq.XPInstallEmbedded.Section line

 

from the Prerequisite section.

 

2. Use a patched update.exe version 6.3.13.0 or later to accept the modified update.inf file. Update.exe files differ between various languages.

 

UPDATE: Instructions on how to apply the patch to any language can be found here:

http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?p=1078363

 

3. Compress to SFX EXE file. Delta compression optional.

 

I have already uploaded the files at RyanVM.net...

 

So Windows XP can have semi-official support until 2019! :w00t:

  • Upvote 3

Share this post


Link to post
Share on other sites
Guest   
Guest

Yep indeed. Just tested them by manually copying the files over and rebooting. No issues.

Edited by -X-

Share this post


Link to post
Share on other sites
harkaz    25

Lol.. it must be an unpleasant surprise to them

PS. By mistake, I refreshed the page when posting the thread and it has been double-posted. Please lock/remove the older one.

Share this post


Link to post
Share on other sites
dencorso    542
Well, Bulletin 1 in the [...] IE8 version should be immediately usable, perhaps requiring a relaxing of the .INF  "Applies To"  conditions [...]. I'm betting Bulletin 5 (the .NET one) may be directly applicable, too, perhaps requiring, likewise, some previous callisthenics... As for Bulletin 6, we'll only know, when whe know what does it contain. [...]

 

Thanks to harkaz, Bulls 1, 5 and 6 installed and running great! :thumbup

 

Long live, XP! :)

  • Upvote 1

Share this post


Link to post
Share on other sites
jaclaz    943

With reference to this:

http://www.microsoft.com/en-us/download/details.aspx?id=42774

which is related to this kb:

http://support.microsoft.com/kb/2932079

 

 

Introduction
This update resolves a vulnerability in the Microsoft .NET Framework that could allow elevation of privilege if an unauthenticated attacker sends specially crafted data to an affected workstation or server that has the .NET Framework Remoting feature enabled.

 

it is IMHO not a patch for a vulnerability, it is a patch for generic stupidity.

 

jaclaz

Share this post


Link to post
Share on other sites
the xt guy    1

First of all, thank you *very much* harkaz, this is beyond cool! Heading home from work yesterday I was almost a bit giddy seeing these semi-official patches and thinking of all the future ones that could/will be coming our way through 2019!

Let the idiots on neowin storm off in a huff! Tell them to come back in 2019.

For myself, I only get 1 patch out of the deal (I don't have IE or any version of "dontnet" installed). Hmm, I didn't think about POS not having IE6. Looks like we won't get any IE 6 patches unless somebody ports them from 2003.

Jaclaz, I agree it's a patch for general stupidity-let's hope MS doesn;'t start patching for that, as we'll all need petabyte sized drives.

(Seriously though, the link to the bulletin 42774 that you posted; under 'System Requirements' it states that Windows XP is a "supported operating system" along with Windows Server 2003. But the title at the top of the page for 42774 just says Windows Server 2003.)

Share this post


Link to post
Share on other sites
dencorso    542

Rest assured the IE6 and the IE7 patches for POSReady 2009 also exist! I'm sure harkaz'll release modded versions of them soon, too.

Share this post


Link to post
Share on other sites
jsc1973    1

Is there any chance of getting all of the Windows Server 2003 x64 updates onto XP x64? Someone just suggested I ask my question in this thread, and TIA for any help. :)

Earlier today, I attempted to download the three available updates for Server '03 and install them manually onto my XP x64 laptop. I had no trouble with MS14-026 (using the .NET 2.0 version; I don't have 4.0 installed so I didn't try that one) or 029. However, MS14-027 failed. A check of the .inf files inside the update revealed that Microsoft put in a block in "update_SP2QFE.inf" that prevents it from installing on XP x64:

[Prereq.XPAMDInstallBlock.Section]

PresentOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000

NotEqualOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000,!=,"WinNT"

Display_String="%WrongProductMessage%"

Is this update legitimately not suitable for XP x64 for some reason, or is Microsoft just being a PITA about it? And if it's the latter, how hard would it be to hack it to run? Would like to keep this machine on XP x64 as long as I can. It's a Dell Inspiron 1545 with a T9800, and it can run 7, but feels like it's running in mud compared to XP x64.

Edited by jsc1973

Share this post


Link to post
Share on other sites
harkaz    25

The update is applicable to Windows XP x64 SP2 if you remove the:

 

    Condition=AndOp,Prereq.XPAMDInstallBlock.Section

 

line from the [Prerequisite] section and patch the update.exe file to accept the modified update.inf. Instructions can be found here: http://www.ryanvm.net/forum/viewtopic.php?p=115464#115464

 

The shlwapi.dll file is not an exclusive Server 2003 x64 component. In addition there are registry keys in the INF file specific for XP Professional x64:

 

[ProductInstall.ProfessionalFiles]
    AddReg=Product.Add.Reg.Professional

[save.Reg.For.Uninstall]

HKLM,SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%

 

[Product.Add.Reg.Professional]
    HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Comments",0,%SP_TITLE_XP%
    HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Fix Description",0,%SP_TITLE_XP%
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"RegistryLocation",0,"HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%"
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"ParentDisplayName",0,"%PARENT_DISPLAY_NAME_XP%"
    HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%,"DisplayName",0,"%SP_TITLE_XP%"
    HKLM,SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP%SERVICE_PACK_NUMBER%\%SP_SHORT_TITLE%,"Description",,%SP_TITLE_XP%
 

and the relevant strings.

 

All these observations indicate that the update is applicable to XP x64 without any issues (It's not proved completely - that would require an analysis of the patch itself, something rather difficult and not required in this scenario).

 

One final note: Because these updates have been deployed on a relatively limited number of machines (XP support has officially ended and most users ignore the existance of these updates) testing any of them in VM before deploying to real hardware is strongly recommended.

Share this post


Link to post
Share on other sites
dencorso    542

Besides other editings needed, the "Frankenstein folder" "Windows XP Version 2003" must be corrected to "Windows XP", BTW.

Share this post


Link to post
Share on other sites
harkaz    25

@den It should not be corrected for Windows XP x64 edition:

 

All Windows XP x64 (Version 2003) post-SP2 updates are verified via this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×