POSReady 2009 updates ported to Windows XP SP3 ENU

[SD73]

6 hours ago, Bersaglio said:

Direct links for January 2019 updates: WES09/POSReady 2009 update (English only), IE8 cumulative security update (English), .NET Framework 2.0 SP2 and .NET Framework 4.0 updates (international), Office 2003 SP3 security update

 

http://download.windowsupdate.com/c/msdownload/update/software/secu/2018/12/windowsxp-kb4481275-x86-embedded-enu_5160cf8226e525f266f39e7279ce39e6176cece9.exe

 

 

http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/01/ie8-windowsxp-kb4480965-x86-embedded-enu_469b647b191dac942734a9a64e05bc27321e79a5.exe

 

 

http://download.windowsupdate.com/d/csa/csa/secu/2019/01/NDP20SP2-KB4480087-x86_010990466ABCF053D7164DFFE1BC0812B5A86B96.exe
http://download.windowsupdate.com/d/msdownload/update/software/secu/2019/01/NDP40-KB4480077-x86_05E61336A238A90796BCDA78D13F0982075F2A2E.exe

 

 

http://download.microsoft.com/download/0/5/5/055B2A2C-2102-40D1-B0C7-A0BF29DEA79B/office2003-KB4461635-FullFile-ENU.exe

 

P.S. Windows Embedded Standard 2009 (WES09) support has ended. WES registry keys should be removed. There should be only POSReady key left from now on.

So I've removed the WES key.  Shall I leave the WEPOS and the rest of the keys here?

Thanks!

[Destro]

they both get the same updates.  you only ever needed one of them to begin with.

Edited January 9, 2019 by Destro

[SD73]

I really want to triple check this before I delete.  Remove everything then with the exception of the POSReady key?

edited to add

Ah, okay.  So now I've removed WES and WEPOS keys.

edited again

I manually ran the MU and it picked up 4 of the 5 updates.  It did not find the Office 2003 update, so I downloaded and installed that one by hand.  All went well.

Thanks again, fellas! 

Edited January 9, 2019 by SD73

[FranceBB]

I found all the updates by manually scanning for them on Microsoft Update. It didn't take much time. No yellow shield, though.

[Mcinwwl]

On my end, all found within seconds and installed with no bugs spotted so far! Only issue was .Net update running for half an hour, but as long as it works, I have no problem with it.

[Mathwiz]

Yes, updating the .NET frameworks (especially .NET 4.0) always seems to take forever and a day.

[Destro]

I mean u didn't need both keys not to remove the key.

[SD73]

30 minutes ago, Destro said:

I mean u didn't need both keys not to remove the key.

Is this in regards to the two keys I removed, WES and WEPOS?  I've saved the registry entries.  Should I add one back in?  I did find all but the Office 2003 updated when I ran MU.

[Bersaglio]

5 hours ago, SD73 said:

Should I add one back in?

No. Only POSReady key should stay otherwise upcoming updates (from February 2019 and later) will not appear via automatic updates and will not install.

[SD73]

7 hours ago, Bersaglio said:

No. Only POSReady key should stay otherwise upcoming updates (from February 2019 and later) will not appear via automatic updates and will not install.

Thank you!

[Vistaboy]

20 hours ago, Mathwiz said:

Yes, updating the .NET frameworks (especially .NET 4.0) always seems to take forever and a day.

And you are really lucky.

I can't install any .NET framework updates since last month:

NDP35SP1-KB4470633-x86 + NDP40-KB4470490-x86 (December)

+ 

NDP20SP2-KB4480087-x86 + NDP40-KB4480077-x86 (January)

I try to install them offline but get the message of updates are incompatible with NET version system or that my NET 4.0 was not installed that is untrue cause i clearly see it in my programs panel.

I simply gave up and hidden the recursive WU alert on updates installation pending, cause in April, i will do the (probably) last POSREADY installation 

 

[Dave-H]

My WEPOS and WES keys both have the "Installed" DWORD set to 0.
Only the POSReady key has Installed set to 1.
Does it matter if I don't remove them in that case?

[Mathwiz]

I've heard of that problem before. KB4480077 updates .NET Framework 4 Client Profile; yet it may refuse to install unless .NET Framework 4 Extended is also installed.

Looks like KB4470490 updates both Client Profile and Extended.

[Bersaglio]

45 minutes ago, Dave-H said:

My WEPOS and WES keys both have the "Installed" DWORD set to 0.
Only the POSReady key has Installed set to 1.

Most likely, with such values everything will be fine. Removing them are unnecessary in this case.

Edited January 11, 2019 by Bersaglio
typo

[SD73]

20 minutes ago, Bersaglio said:

Most likely, with such values everything will be fine. Removing them are unnecessary in this case.

Interestingly, I had backed up both those keys before I deleted them.  Mine were also set to "0" and everything had been working well.  It may have been a non-issue for those of us who missed it.  Regardless, thank you all for the input!