POSReady 2009 updates ported to Windows XP SP3 ENU

[dencorso]

For the sake of easier reference, I've added the Microsoft Security Bulletin Number (in blue), to @heinoganda's list, quoted below:

On 4/20/2017 at 5:45 PM, heinoganda said:

The relevant updates are installed on my system. I have the list, based on more recent updates, updated.

;KB958644  MS08-067           10/22/2008     replaced by KB2705219!
KB2705219-v2  MS12-054 10/09/2012    relevant Update!
browser.dll     5.1.2600.6260
netapi32.dll    5.1.2600.6260

KB2347290  MS10-061       09/13/2010   relevant Update!
spoolsv.exe    5.1.2600.6024

;KB3011780    MS14-068         11/17/2014     replaced by KB3126041!
;KB3126041    MS16-014         02/08/2016     replaced by KB3161561!
KB3161561   MS16-075       06/14/2016   relevant Update!
kerberos.dll    5.1.2600.7075
ksecdd.sys      5.1.2600.7075
msv1_0.dll      5.1.2600.7075
xpsp4res.dll    5.1.2600.7075
srv.sys           5.1.2600.7075

KB3198510   MS16-137       11/07/2016   relevant Update!
lsasrv.dll         5.1.2600.7151
msv1_0.dll      5.1.2600.7151

KB4012598   MS17-010       03/12/2017   relevant Update! (also for CVE-2017-0146, and CVE-2017-0147)
xpsp4res.dll    5.1.2600.7208
srv.sys           5.1.2600.7208

[heinoganda]

The list of Mathwiz shows correctly (see Technet blog), from which patch these relevant vulnerabilities were removed. In the meantime, there may be other vulnerabilities in the same files that are fixed by a newer patch. Because of this problem, it happens because the previous patch has become obsolete, which is not offered for a new installation of the updates the previous patch. For this reason I have developed a corresponding list which takes this problem into account and the user does not wonder why certain updates can not be found or can be installed later manually. The list is a snapshot, where the user shows which updates are relevant at the current time, so that the security holes listed in the Technet blog are eliminated. (I deliberately refrained from specifying the additional vulnerabilities in the follow-up patch, in order not to discourage the users, since again no reference is possible to the Technet blog.)

Edited April 26, 2017 by heinoganda

[Mcinwwl]

@FranceBB

So I thing I'll try to find time to post on their forums. I can get away with updates (POSRedy updates are not an official way, I get they might don't want to support them), I know how PUP is wrapped within installers and how to mitigate it, but a problem with scanner effects directly my relatives, and I don't want to be called by person for every document scanning :/

[FranceBB]

I sent a message to the support (I'm running Avast Premier Beta) about the issue, but feel free to open a topic in the Avast forum; luckily, Martin will look at it and do something about it.

Now, a totally unrelated thing: I've tried to install the two updates for the .NET Framework 4 both via executable and via Windows Update, but I failed to install them in both ways. Please, don't tell me that I have to uninstall and re-install the .NET Framework every bloody time an update pops up

Quote

OS Version = 5.1.2600, Platform 2, Service Pack 3
OS Description = WinXP - x86 Professional Service Pack 3

CommandLine = c:\dda6f8b271d1c858d6bcdc6f13c7\Setup.exe
TimeZone = ora legale Europa occidentale
Initial LCID = 2057

Using Simultaneous Download and Install mechanism

Operation: Installing

Package Name = KB4012355
Package Version = 10.0.30319

User Experience Data Collection Policy: UserControlled

Number of applicable items: 1

Summary Information:

Microsoft .NET Framework 4 Client Profile

Patch (c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB971891.msp;c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB4012355.msp) Install succeeded on product (Microsoft .NET Framework 4 Client Profile). Msi Log:

Patch (c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB971891.msp;c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB4012355.msp) Install succeeded on product (Microsoft .NET Framework 4 Extended). Msi Log:

Patch (c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB971891.msp;c:\dda6f8b271d1c858d6bcdc6f13c7\NDP40-KB4012355.msp) Install failed on product (Microsoft .NET Framework 4 Client Profile ITA Language Pack). Msi Log:

Final Result: Installation failed with error code: (0x80070643), "Errore irreversibile durante l'installazione. " (Elapsed time: 0 00:13:31).

[heinoganda]

I could not retrace the error 0x80070643 with KB4012355 during a test installation of the .NET Framework 4 in the VM. Is MSI 4.5 (KB942288-v3) installed? If so, I have found here an error solution suitable to the error. If no, MSI 4.5 should be installed and try a repeated installation of KB4012355.

[FranceBB]

Yep, MSI 4.5 is installed, otherwise all the other pos updates wouldn't have been installed in the past, as well as former .net updates. It seems that I gotta reinstall the .NET framework 4 once again (I already have the .net repair tool); doing that will solve the issue for sure. Anyway, the "weird" thing is that I use the .net 4 almost on a daily basis (avisynth, which is a frameserver, and its filters) and everything works fine, which makes me think that it's not actually really corrupted. Well, I guess I'll reinstall it once again...

Edited May 2, 2017 by FranceBB

[cc333]

OK, I'm getting XP up and running on a Dell Latitude D600, but with a slow, single core P4 CPU, I'm afraid that updating via WU will take days of sitting at "Checking for updates...", instead of the hours it took for my comparatively much faster D630.

Any advice on how to prevent the stickage?

c

[FranceBB]

10 hours ago, cc333 said:

OK, I'm getting XP up and running on a Dell Latitude D600, but with a slow, single core P4 CPU, I'm afraid that updating via WU will take days of sitting at "Checking for updates...", instead of the hours it took for my comparatively much faster D630.

Any advice on how to prevent the stickage?

c

Try to install Harkaz ISO instead of the standard Service Pack 3, so you'll have to update from 2014 to 2017 instead of from 2008 to 2017. So many years of updates will take a lot for sure.

Ok, now welcome back to our community, called "Windows XP Spotter". The last time I posted a picture of a Windows Embedded POSReady from a Quickmark in the UK, but I got a picture from Ivo, a friend of mine living in Italy, which actually shows a Windows XP machine. 

See you next time with another episode of "Windows XP Spotter"

Edited May 4, 2017 by FranceBB

[heinoganda]

@FranceBB

Did you solve your problem with .NET Framework 4 ?

[FranceBB]

Yep, I removed the .NET 4 and installed it from scratch together with updates. Not sure why it behaves like that, considering that I use it on a daily basis and that it's not really corrupted ('cause it works). Anyway, it's not the first time that I have issues updating the .NET Framework, and after monkeying around, googling trying a few things to avoid reinstalling in the past, I found out that I lost more time looking for a workaround than the time I would actually have spent reinstalling (which I did).

Edited May 5, 2017 by FranceBB

[heinoganda]

It is nice to hear that your .NET Framework 4 is installed correctly again. The worst thing about a .NET Framework installation is the eternal update process. Since I have found a way to accelerate this.

[Dave-H]

Not directly relevant to Windows updates, but I just thought I'd mention for those still using it that there was another update for Adobe Reader 11 a few weeks ago, to version 11.0.20. You can get it here if you want it.

 

[heinoganda]

Current Update for .NET Framework 2.0 sp2:

NDP20SP2-KB4020517-x86.exe                           05/01/2017                   File download

Current Update for .NET Framework 4:

NDP40-KB4020510-x86.exe                                 05/01/2017                   File download
 

Info: .NET Framework 2.0 sp2 and .NET Framework 3.0 sp2 are a component of the .NET Framework 3.5 sp1 installer packages.

Edited May 9, 2017 by heinoganda
So everyone should be satisfied now!

[dencorso]

Out-of-band? It must be serious...

[heinoganda]

There are updates for the security updates KB4014580 and KB4014570!

Further information:
https://support.microsoft.com/en-us/help/894199/description-of-software-update-services-and-windows-server-update-services-changes-in-content-for-2017

Fixed a problem with the Powershell (stop-computer command fails. When this issue occurs, you receive a "Privilege not held" error message).

More I could not find out.

Edited May 6, 2017 by heinoganda