Dave-H

This is mine.

And the UK English version it would seem!

When Office 2010 support ends in a couple of months, I am probably going to update the copy on the Windows 10 side of my machine to Office 2019. I'd like to then use the serial number I have for Office 2010 on another XP machine, but although I have the installation media, it does not include the updates, including the service pack. As Microsoft Update for XP is now dead, what's the best way of doing that and doing all the updates? I really don't want to be doing them all manually one by one from the Microsoft Catalogue! Cheers, Dave.

That is very interesting! My Windows XP is English, but set to United Kingdom English. I wonder if the cab would work if I changed it to US English? I don't see why it would make a difference, but stranger things have been known!

The 2019 version of wsusscn2.cab from the Wayback Machine works fine for me too in WUMT thanks very much! It's still a mystery to me why the last SHA-1 signed 2020 version won't work for me or you though, especially when others have said that it does! I tried the 2019 version in MBSA, and that didn't work I'm afraid, as with the 2020 version I just got "The catalog file is damaged or an invalid catalog". I've now got those bloody ESENT error messages in my Event Log all the time again too, I guess I'll have to restore the SoftwareDistribution folder from my backup again! Probably it's time to give up on MBSA, it's presumably never going to work again except with the 2018 version of wsusscn2.cab which it has cached. It doesn't seem to want to know about later versions.

Glad I'm not the only one having that problem with WUMT!

I just seemed to remember that we had a lot of experimenting with HDAICOUT.HDA to get any sound out of my system, but as you say, I guess the problem that @sweaterfishis having is different. My system is fine, no stability issues at all thanks! I still get odd pops and clicks all the but at least the sound works, and I was only really needing it for the system sounds anyway as I have a multi-boot machine. Cheers, Dave.

Just to chip in here, IIRC you had to produce a specific HDAICOUT.HDA to support my hardware, so I suspect that the same will be needed here. It's still working fine BTW! Cheers, Dave.

Finally got around to installing the patches, all OK apart from, as has been said, KB4484454 which contains another XP incompatible MSO.DLL. All fine as usual after the old one was put back. Let's hope the next two batches of Office 2010 updates, which will be the last ones, are still signed with SHA1 so they will install on XP. It will be very annoying if they aren't when it's so near to EOS anyway!

I guess maybe I don't have the properties tab on cab files in Explorer on XP because I have cab files associated with WinZip? Anyway, I checked the file on Windows 10 Explorer, which does show the details, and it's definitely the right digital signature date and definitely SHA1 signed. It just doesn't work when I try to use it!

I have a utility to check in XP, it's definitely SHA1 signed. That's why I can't understand why it won't work for me in WUMT.

No problem, thanks anyway!

Thanks @MicahMoo11, but I'm afraid the file in wumt(1).zip seems to be the same as the one I've already got, the 2020 file.

Ah, thanks for the clarification, good to know that the latest updates do install on XP, I was worried that they might not have the necessary signing now.

When was that? Were they offered before Microsoft Update was withdrawn as far as XP is concerned? I've never seen them.

Does anyone have a version from 2019 archived? As I can get the Nov 2018 version to work, but can't get the July 2020 version to work, I'd like to see if one from 2019 will work.

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!

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!

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!

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!

I doubt what you've done will cause any problems, but it is strange that the behaviour on your system isn't the same as on mine and Daniel's.

Thanks, tried that but no difference at all here.

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?

FWIW, the CWDIllegalInDllSearch registry entry does not exist on my system. I've never installed SP4.

OK, I now got this - At least it's different! WUMT still shows the same error as before.