Dave-H

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.

No, me neither. Some background on DLL loading priorities here. Doesn't seem to solve the problem though!

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

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!

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

I'm only working from my very faulty memory here, but is that dll listed in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs? IIRC, if it is there programs will always use the version in system32. If it's there, remove it and try again.

Tried that, and both WUMT and the script just complain that the service isn't running and cannot be started. Again, can anyone confirm that this works on a system with all the POSReady updates applied? We've found (see other current threads) that a couple of those updates stopped Office 2010 encryption working properly, which I don't think anyone was aware of before, so is it possible that a POSReady update or updates has also hosed this?

Yes, works fine with the older file just in the Office program folder, no need to change the system file!

That file doesn't exist by default in the Office program folder, only in \system 32. Putting any version in there should not be a problem.

Wow, great news! My version of dssenh.dll in \system32 is 5.1.2600.7345. The version in KB3081320 is 5.1.2600.6924. I guess a subsequent update changed the system version, probably causing the Office encryption problem, but if the older version of the file is in the Office program folder it still uses that. Great result!