Dave-H

Thanks! I think that's the first time for a very long time that the date has been the same on all the entries in the list!

Otter browser still has a version for XP, it works fine, but it's still very much a work in (very slow) progress. https://sourceforge.net/projects/otter-browser/files/otter-browser-weekly333/otter-browser-win32-weekly333-xp.zip/download

That's good to see, but don't depend on it staying like that! There's evidence that Yahoo and others are gradually updating the requirements on their servers, and all the servers will I'm sure start rejecting TLS v1 logins eventually. I'm using yahoo.co.uk servers which already reject TLS v1 logins.

And yet I'm sure there are people with fully POSReady patched SP3 machines who report that the July 2020 cab works fine! This is really strange.

I've just made the rather annoying discovery that the new Facebook layout, which will become mandatory next month, apparently causes the playing of videos to break if Firefox 52.9 ESR is used with the Primetime plugin. The videos appear for an instant, and then go to a black screen with a message on it saying that the video can't be played. Reverting back to the old layout makes it all come good again. Can anyone else confirm this?

There are two problems here, firstly the OAuth2 issue, and secondly the fact that a lot of e-mail providers are dropping support for TLS v1, and mandating at least TLS v1.2. I still use Eudora for my e-mail, and have since about 1995! It's the best e-mail client ever made IMO. In recent months I've had to jump through a few hoops to keep it working with my Sky e-mail account, which is managed by Yahoo. I had to get an "application specific password" some time ago, and more recently I had to use an update provided by the Hermes project to add TLS v1.2 support. Without both of those, it would have become useless after 25 years! It's now working fine, but other legacy e-mail clients must all be facing the same issues.

That does sound very likely, but I'm not 100% certain about that! It would make sense that all the English variants of XP shared the same ISO, as unlike in later versions of Windows, the XP English GUI is always in American English, it's only things like keyboard layout, currency and time and date format displays that are customised for the different English versions, as far as I know. So, why does it work for you, and not for me? Curiouser and curiouser!

So are you saying that all those versions work fine with the July 2020 last SHA1 signed wsusscn2.cab file, and EN-US, but French does not work? I'd be interested if you could try EN-GB to see if that works for you.

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!