Dave-H

Thank you too! I've just tried @AstroSkipper's version of what I assume is the same thing, running rvkroots.exe first, and then rootsupd.exe. Again it appeared to work with no errors, but hasn't made any difference to Microsoft Update. BTW, I couldn't get your Microsoft link to the original rootsupd.exe to work, it just gives a 404 not found.

Thanks, I'll give that a try!

How do I do that? I've packed up the files, and the resulting file appears to run with no errors, but how can I tell if it's worked? There's no difference so far on Microsoft Update, it's still failing.

I know that!

Aww, thank you! You won't get around my moderation like that though!

OK, I'll give that a try to see if it makes any difference, and I'll report back tomorrow.

Are you chatting me up?!

How do you know it's failed? Just so I can check that mine hasn't!

Yes, years ago! I use heinoganda's certificates updater regularly, and I've no reason to think that anything isn't as up to date as it can be. There are no problems anywhere else, just on the revived Microsoft Update site. 360Chrome is no use for MS Update of course, as the site relies on ActiveX controls. That bit is apparently working fine, and it scans, but instead of showing the results, it fails with the supposed clock setting error.

Thanks, yes I've done that, but no difference. I suspect those certificates were already installed as they appear to date from 2011. Looking at @xpandvistafan's installation script, I've now also manually added the registry entries, which weren't there before on my system. Still no difference, I can't seem to get past the "clock setting" error.

So is this a non-starter then? If so, I will just have to accept the machine as it is on XP, and be happy that it works as well as it does. The lack of sound is the biggest annoyance. BTW, thanks to George King, I'm now using the bearwindows graphics driver, which does work pretty well, although with no hardware acceleration. I tried the Windows 98 version some years ago, and wasn't impressed, but the NT version is pretty good considering.

I can give it a try, but I'm not familiar with that program or procedure at all I'm afraid. You will have to talk me through it, as I'm very nervous of tinkering with anything to do with BIOS!

I don't have that certificate. Could you export it and upload it here so I can try it to see if it makes any difference? I'm very loathe to start messing around with my installation of ProxHTTPSProxy, I've been using it for years and it has always worked perfectly with many other sites and continues to do so. I find it hard to imagine that it has an intrinsic problem that is stopping just MS Update from working but everything else is fine.

Thanks very much! Sadly my CPU is a Celeron N2840, so I guess this won't work?

I've checked them all and everything is already done, and has been for a long time. There is nothing wrong with my computer's clock. I do think that very likely the error message I'm getting is a bit misleading, as they often are! I don't think it's anything to do with clock settings, it's just that it's trying to use a certificate which is either missing or expired. There is a certificate in my list of Intermediate Certificate Authorities called "Microsoft Update Secure Server CA 1". It expired on 9th May 2021. I wonder if that's the problem? The file is attached. Anyone any Idea how I can update it to a valid version? MSUpdateCert.cer

I'd already looked at that page and tried everything there, nothing made any difference. My anti-virus is Malwarebytes Premium. I'll check to see if that has any relevant settings. Other https sites seem to work fine, so I'd be surprised if there is something there only affecting the Microsoft Update site.

A good thought thanks, but I tried generating an new empty DataStore.edb and just got the same error message I'm afraid. Some research indicated that the error I'm getting is because my system time does not match the time on the server, and I wondered if this was because I'm not in the States, but I then saw that others in Europe have had this working, so it can't be that!

I went back to the version of CA.crt which came with ProxHTTPSProxy, and MS Update then didn't work at all, "unable to display page" (Error number: 0x80072F7D). After restoring the newer version it loads and scans again, but then I'm getting the supposed clock setting error again.

My install of ProxHTTPSProxy came from @heinoganda's original package. I've checked it, and it does include a CA.crt file, which is valid from 01/10/15 to 30/09/25. I must have subsequently updated it. I can try going back to the original version and see what happens.

Yes, that is puzzling. Are people who have this working using the http:// URL or the https:// URL? Looking at the screen grabs, it appears to be generally the http version. I realised I actually have only https links set to use ProxHTTPSProxy, not http links, so I changed that to use it for all URLs, but it didn't make any difference, I'm still getting the supposed clock setting error.

This thread is now locked. These types of arguments will never be resolved, and MSFN isn't the place for them, even in this section.

IIRC I must have updated the certificate using the details in cacert Update.txt. The one you have appears to be the default CA.crt supplied with the program. I don't see how installing an older certificate would make Windows Update suddenly work, surely it would need a newer certificate if anything. As I use ProxHTTPSProxy for some important things, like keeping the certificate error popups away on my ancient Eudora e-mail client, which uses the IE engine to display messages, I don't want to risk messing it up by installing an old certificate.

I certainly didn't do anything knowingly to generate my own certificate. My certificate was issued in June 2021, yours in October 2015, so I'm a bit loathe to now install an apparently older certificate.

That looks like the same version of ProxHTTPSProxy that I've already got, and its certificate is installed of course, or it won't work! Is there a more recent one, that one looks like it's good until 2031!

My glasses are blue!