Are you all triggering Windows Update somehow to start downloading? I've got a fresh XP SP3 in a VM but I don't think it's checking (or it's failing) for downloads. I got it set to "Download and notify"

AutoPatcher seems to be broken btw. It errors when it's about download the update files (using the "release2" list)

I think after I did the updates on my son's machine it was like 132 so you should be complete

HandOfFate wrote on 2020-08-09, 16:34:

Are you all triggering Windows Update somehow to start downloading? I've got a fresh XP SP3 in a VM but I don't think it's checking (or it's failing) for downloads. I got it set to "Download and notify"

AutoPatcher seems to be broken btw. It errors when it's about download the update files (using the "release2" list)

In my case I had it set to automatically download updates and it did so within minutes of me logging in for the first time. A little yellow shield thing with an exclamation mark should appear in the system tray in the corner with a %. The website for updates is broken though.

Tempest wrote on 2020-08-09, 20:26:

HandOfFate wrote on 2020-08-09, 16:34:

Are you all triggering Windows Update somehow to start downloading? I've got a fresh XP SP3 in a VM but I don't think it's checking (or it's failing) for downloads. I got it set to "Download and notify"

AutoPatcher seems to be broken btw. It errors when it's about download the update files (using the "release2" list)

In my case I had it set to automatically download updates and it did so within minutes of me logging in for the first time. A little yellow shield thing with an exclamation mark should appear in the system tray in the corner with a %. The website for updates is broken though.

Until very recently, once I updated to IE8, I could get to the Windows Update site, and it would be off and running. But now this happens (I've tried it on two different computers today):

"
SHA-1 Windows content to be retired August 3, 2020

To support evolving industry security standards, and continue to keep you protected and productive, Microsoft will retire content that is Windows-signed for Secure Hash Algorithm 1 (SHA-1) from the Microsoft Download Center on August 3, 2020. This is the next step in our continued efforts to adopt Secure Hash Algorithm 2 (SHA-2), which better meets modern security requirements and offers added protections from common attack vectors.

SHA-1 is a legacy cryptographic hash that many in the security community believe is no longer secure. Using the SHA-1 hashing algorithm in digital certificates could allow an attacker to spoof content, perform phishing attacks, or perform man-in-the-middle attacks.

Microsoft no longer uses SHA-1 to authenticate Windows operating system updates due to security concerns associated with the algorithm, and has provided the appropriate updates to move customers to SHA-2 as previously announced. Accordingly, beginning in August 2019, devices without SHA-2 support have not received Windows updates. If you are still reliant upon SHA-1, we recommend that you move to a currently supported version of Windows and to stronger alternatives, such as SHA-2."
https://techcommunity.microsoft.com/t5/window … 20/ba-p/1544373

All good things come to an end. I'm only surprised Windows Update continued to work with Windows XP as long as it did.

I also updated to IE8 yesterday and I got the same screen.

I saw the SHA-1 thing but I also saw that SP3 is supposedly to have the SHA-2 patch. Don't know if that patch also applies to Windows Update, of course. I also manually downloaded some other patches that people mentioned in discussions about the SHA-2 thing. No change.

I've enabled fully automatic updates now on a schedule (to daily at 11:00). I'm guessing it will stagger the start time between 11:00 and 11:59 because, in the olden days, they wouldn't want thousands and thousands of machines to start at the same minute.

Let's see what will happen. But it otherwise it would mean that I'm just a few days too late?

to get SHA2 support in in XP, you have to install KB968730, which is not in windows update. But if it will resolve problem you have, I dont know.

Also, you can install Windows server with WSUS, bulk download updates there and tell your XP machine to update from your WSUS server.

I did install KB968730 on an English XP (couldn't find the one in Dutch anywhere, it has disappeared from the face of the internet) but so far my English install isn't doing anything either.

I like your solution with Windows Server. It's probably time consuming and clunky to set up but it's authentic. Would the free trial of Windows Server 2012 or 2019 work for this?

As I test, I did an install of Windows 7, and when I tried to update it, you guessed it; "Code 80244019."

Repo Man11 wrote on 2020-08-10, 12:56:

As I test, I did an install of Windows 7, and when I tried to update it, you guessed it; "Code 80244019."

This should get you up to 2016 update levels : https://answers.microsoft.com/en-us/windows/f … 89-48e1e883051e

Windows update may work after that .

Windows update still works for my win 7 ultimate daily driver I just checked

Oh and if somebody needs Windows 7 SP1, you can still get it from here https://www.catalog.update.microsoft.com/Sear … aspx?q=KB976932
The x86 update is under "Windows 7 Service Pack 1 (KB976932)" . The x64 one is under "Windows Server 2008 R2 Service Pack 1 for x64-based Systems (KB976932)" . I have run a binary comparison against my own Windows 7 x64 SP1 backup and it matches . The update is likely the same as for Windows Server 2008 R2 Service Pack 1 for x64 .

@HandOfFate I run it with Windows server 2003 😀 As you say, it definitely is not straightforward and you need to learn basics how to set up WSUS and work with it, but then you just set one GPO in XP system with WSUS server address and it gets updates from there.

It works fine with clean Win2003 SP2 + .Net framework 2 SP2 + reportviewer2008sp1 + WSUS3SP2-KB972455 + WSUS Update KB2720211

Server 2008, 2012 or 2019 should also work without issue.

@Repo Man11 as for Windows 7 and error 80244019, you need to manually install KB4474419 and it should start working again. its described here: https://support.microsoft.com/en-gb/help/4569 … ts-discontinued

marvias wrote on 2020-08-10, 13:31:

@HandOfFate I run it with Windows server 2003 😀 As you say, it definitely is not straightforward and you need to learn basics how to set up WSUS and work with it, but then you just set one GPO in XP system with WSUS server address and it gets updates from there.

It works fine with clean Win2003 SP2 + .Net framework 2 SP2 + reportviewer2008sp1 + WSUS3SP2-KB972455 + WSUS Update KB2720211
[...]

I got it to get updates. I installed the following things: Win2003 R2 x86, WSUS 3.0 with SP2, .NET 2.0 SP2 (to be able to update WSUS to SP2), KB3072630 (because people said it's a SHA-2 related fix?), Internet Explorer 8 (probably wouldn't have been necessary).

Next step will to be modify my Windows XP installs (Dutch & English) to use the WSUS server. I read I can do it via gpedit.msc and avoid having to set up an Active Directory domain. Then I will hopefully get a nice directory full of patches of everything that came after SP3.

Btw, funnily enough, Windows Update itself doesn't work on Server 2003 either when using Microsoft's servers. You have to let it update itself via its own WSUS, probably.

Does no one else think it would be easier to slipstream these 132 updates into the install CD and not have to download them every time?

Jorpho wrote on 2020-08-11, 16:35:

Does no one else think it would be easier to slipstream these 132 updates into the install CD and not have to download them every time?

It's certainly an approach that's been used many times in the past.

That is also my goal

There's the unofficial XPSP4 project to do exactly that:
https://ryanvm.net/forum/viewtopic.php?t=10321

Also comes with addons to integrate the PosReady 2009 patches, if you have an SSE2-capable machine.

In my case I'd rather do it myself. Far more interesting 😀

[edit]
Immediately after changing the Windows Update server in XP's Group Policy, it started downloading updates. Nice!

Fun fact, Microsoft took down the entire update site completely, only for it to be returned back to a workable setate for a day or two before the 0x80244019 started to occur.
Suggest to follow this thread from this point (gives you a graspe over how MS messed things up and the ideas of circumventing the problem): https://msfn.org/board/topic/178377-on-decomm … comment=1185321