On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019

[cc333]

I'm trying it, and all I get is "Interface not supported", whatever that means....

c

Edited August 9, 2020 by cc333

[Dave-H]

You're trying to use the later version, which only runs on Windows 10 apparently!
See earlier posts.

[Condor.07]

5 hours ago, Dave-H said:

@Condor.07

Just a quick thought.
Do you have the POSReady updates installed on your system?

I repeat, I have installed absolutely nothing!
Windows XP SP3 clean
added the folder with WUMT and starting in offline mode as you can see from the image.
surely in your Windows XP you have corrupted something ...
try a clean install and you will see that it works.

P.S.= your error (0x800b0100) should be an antivirus problem

Edited August 9, 2020 by Condor.07

[daniel_k]

2 hours ago, IntMD said:

Weird. what error did it show btw? Also to rule out obvious things, you selected "Offline mode" before searching, right?

 

[Dave-H]

I repeat, I have installed absolutely nothing!
Windows XP SP3 clean
added the folder with WUMT and starting in offline mode as you can see from the image.
surely in your Windows XP you have corrupted something ...
try a clean install and you will see that it works.

OK, yes I realise you're using a clean install!
What I'd like to know is whether anyone else who has a fully POSReady updates patched system has this working.
If nobody can show this, I think we have to assume that one or more of the POSReady updates is the problem.
I don't think I'm going to be going back to a clean install just to fix this, but it would be good to know one way or the other!

 

Edited August 9, 2020 by Dave-H
Quote added

[Dave-H]

2 minutes ago, daniel_k said:

 

I'm getting a different error message "An error has occurred: 0x800B0100 No signature was present in the subject".

[daniel_k]

  

3 minutes ago, Dave-H said:

What I'd like to know is whether anyone else who has a fully POSReady updates patched system has this working.

Yes, it works.
For me, it's easier to get it working on a fully patched (POSReady) XP than a clean install.

 @Dave-H, one last try:
- stop the Automatic updates service
- delete C:\WINDOWS\SoftwareDistribution\ScanFile and rename C:\WINDOWS\SoftwareDistribution\DataStore and C:\WINDOWS\SoftwareDistribution\Download
- restart the Automatic updates service
- run the MS script

[cc333]

8 minutes ago, Dave-H said:

You're trying to use the later version, which only runs on Windows 10 apparently!
See earlier posts.

I thought I had downloaded that version, but apparently I didn't;  I accidentally re-downloaded the Win10-only version :/

So, I went back and got the proper version this time, and it's at least starting now!

So, now let's see if it'll see updates properly....

c

[Dave-H]

16 minutes ago, daniel_k said:

  

Yes, it works.
For me, it's easier to get it working on a fully patched (POSReady) XP than a clean install.

 @Dave-H, one last try:
- stop the Automatic updates service
- delete C:\WINDOWS\SoftwareDistribution\ScanFile and rename C:\WINDOWS\SoftwareDistribution\DataStore and C:\WINDOWS\SoftwareDistribution\Download
- restart the Automatic updates service
- run the MS script

OK, I now got this -

At least it's different!
WUMT still shows the same error as before.

[Dave-H]

OK, I just tried substituting the wsusscn2.cab file I've been using with the other one I had on my system in the D:\Users\Dave\Local Settings\Application Data\Microsoft\MBSA\Cache folder.
That is obviously an older version (in fact from 2018).
WUMT works fine with it! It scans and shows me the "Installed" updates.
The script produces a very similar result to before, but the exit code is 0xC800042D, not 0x8024000B.
Is that better?

If WUMT works with the older version of wsusscn2.cab, why won't it work with the newer version?

[TigTex]

I have that same problem if I enable windows XP automatic updates.

Disable windows XP automatic updates (set to never check for updates), reboot the system and try again.

[Dave-H]

Thanks, tried that but no difference at all here.

[Dave-H]

I tried MBSA again, and the result was the same.
It spent ages downloading the data, and then said it had failed to download it!
It then performed a scan using the old version from 2018.
I suspect it hasn't actually failed to download the data, it's just decided that it can't use it, exactly the same as WUMT.
I'm now getting five identical error messages in the Windows Application Event Log on every boot!
I think what I'm going to do now is restore the entire SoftwareDistribution folder from a backup I made a week ago, before any of this happened.
Hopefully this will get rid of the error messages, unless something in the registry is causing them.

BTW FWIW Belarc Advisor is still working fine for me, and tells me I'm not missing any updates!

Edited August 10, 2020 by Dave-H
Typo

[Dave-H]

OK, I restored the SoftwareDistribution folder from my backup, and the error messages in the Event Log have gone away thank goodness!
Something must have got corrupted in there.
I guess I'll just leave things well alone now, although I'm still puzzled as to why the latest wsusscn2.cab will just not work for me, no matter how I try to deploy it.
As I said, the earlier one I have from 2018 works fine, at least in MBSA and WUMT.
Are there any versions between the 2018 one and the current one still available to download anywhere so I can try them?
This is in the XML file in the 2018 cabinet, looks like it was issued in November 2018.

<?xml version="1.0" encoding="utf-8"?><OfflineSyncPackage MinimumClientVersion="5.8.0.2678" ProtocolVersion="1.0" PackageId="22a18bc5-f805-4490-b510-4f1c71ba6261" SourceId="cc56dcba-9026-4399-8535-7a3c9bed7086" CreationDate="2018-11-18T01:19:21Z" PackageVersion="1.1" xmlns="http://schemas.microsoft.com/msus/2004/02/OfflineSync"><Updates><Update CreationDate="2018-11-13T18:00:08Z" DefaultLanguage="en" UpdateId="a3169b82-874b-4eb9-a790-88dbcf9f785d" RevisionNumber="201" RevisionId="27769579" IsLeaf="true" IsBundle="true"><Categories><Category Type="Company" Id="56309036-4c77-4dd9-951a-99ee9c246a94" /><Category Type="Product" Id="a3c2375d-0c8a-42f9-bce0-28333e198407" /><Category Type="ProductFamily" Id="6964aab4-c5b5-43bd-a17d-ffb4346a8e1d" /><Category Type="UpdateClassification" Id="0fa1201d-4330-4fa8-8ae9-b877473b6441" /></Categories><Prerequisites><UpdateId Id="37e61eda-4a37-4625-88c1-7af8c0b61979" /><UpdateId Id="4103af66-247a-4782-b970-8899394c27c3" /><UpdateId Id="0fa1201d-4330-4fa8-8ae9-b877473b6441" /><UpdateId Id="a3c2375d-0c8a-42f9-bce0-28333e198407" /></Prerequisites></Update><Update CreationDate="2018-11-16T19:28:22Z" DefaultLanguage="en" UpdateId="f0073aff-33ce-456d-9e9c-103a3472e417" RevisionNumber="201" RevisionId="27769578" DeploymentAction="Bundle" IsLeaf="true">

Any versions from 2019 still around to download?

I wonder if those of us with Office 2010 installed will see a yellow shield in the system tray in a couple of days time?
I'm not holding my breath for it!

Edited August 10, 2020 by Dave-H
Addition

[Dave-H]

No less that eight updates offered today for Office 2010 64 bit on the Windows 10 side of my machine!
In no particular order -

KB4484494 (Word)
KB4484497 (Outlook)
KB4484375 (Office)
KB4484461 (Excel)
KB4484379 (Office)
KB4484385 (Access)
KB4484454 (Office)
KB4092435 (PowerPoint)

No sign of them being offered on XP needless to say!