Dave-H

The certificate for *.update.microsoft.com is in the ProxHTTPSProxy Certs folder. I assume it was downloaded when I visited the site. Why there are two certificates for ProxHTTPSProxy is strange, but I've seen that happen before. I have tried deleting the older one of them, but it makes no difference to anything. I can only guess that the 2025 one is the original one supplied with the program that installs when the program is first run, but it then updated to the second one, which is set to expire in 2030 as I had the clock set to 2020, and it just added to the other one rather than replacing it. I'm not going to be reinstalling Internet Explorer to try and fix this, unless there is an absolute guarantee of success, which there isn't of course!

Well I tried setting the clock back to 2020, regenerated the certificates and made sure they were installed. Does that look right? I seem to have two entries for ProxHTTPSProxy, which I have seen before. Same error on Microsoft Update, clock out of sync with an update certificate.

This is strange. It looks as if the connection to www.update.microsoft.com is OK (in green) but the connection to fe2.update.microsoft.com is failing (in red).

http://update.microsoft.com wasn't in my list, I've added it now but no difference. I really don't think it matters whether we do this with HTTPSProxy or ProxHTTPSProxyMII. They are extremely similar programs which do exactly the same thing, I can't believe that something would work with one of them and not with the other. There is no actual log file, I just copied and pasted from the console. I'm a bit apprehensive about setting my system clock to ten years in the past, if that's what you're suggesting. I'm worried it will upset other things.

Well I've restored ProxHTTPSProxy now, but I guess it's the same scenario. I don't think that it matters which of the two programs you use, they are extremely similar and the same problem exists in both of them for me. Entries in red in the console normally indicate errors I would have thought, both on HTTPSProxy and ProxHTTPSProxy. I've now found that if I use the older certificate on ProxHTTPSProxy (the one that expires in 2025), it doesn't work at all. I have to install the newer one that expires in 2031 to get it to work again. Yes, I did start it with a new empty "Certs" folder!

Yes, my HTTPSProxyCA.crt is now valid from 23/01/22 to 23/01/32. It doesn't work. I guess that HTTPSProxy and ProxHTTPSProxyMII have exactly the same issue then, and whichever one you use will have the same problem.

And the next attempt. [22:49] 000 "[SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:600)" while trying to establish local SSL tunnel for [...................:80] [22:49] 131 [D] "HEAD https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 302 216 [22:49] 132 [D] "HEAD https://fe2.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 200 27634 [22:49] 133 [D] "GET https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 302 216 [22:49] 134 [D] "GET https://fe2.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 200 27634 [22:49] 135 [D] "HEAD https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 302 216 [22:49] 136 [D] "HEAD https://fe2.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232249" 200 27634 [22:50] 000 HTTPSProxy FrontProxy/v1.5.2 [WinError 10054] An existing connection was forcibly closed by the remote host

@AstroSkipper OK, I now have HTTPSProxy working, and I am using your confg.ini file. It does seem to be doing everything that ProxHTTPSProxy was doing. Unfortunately, there's no difference on Microsoft Update. I'm still getting "[0x80072F8F] Your computer's date and time appear to be out of sync with an update certificate." This is the output from HTTPSProxy. I don't know if it provides any clues. [22:43] 010 HTTPSProxy FrontProxy/v1.5.2 [WinError 10054] An existing connection was forcibly closed by the remote host [22:43] 013 HTTPSProxy FrontProxy/v1.5.2 [WinError 10054] An existing connection was forcibly closed by the remote host [22:43] 014 [D] "HEAD https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232243" 302 216 [22:43] 015 [D] "HEAD https://fe2.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232243" 200 27634 [22:43] 016 [D] "HEAD https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232243" 302 216 [22:43] 017 [D] "HEAD https://fe2.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab?2201232243" 200 27634 [22:44] 000 HTTPSProxy FrontProxy/v1.5.2 [WinError 10054] An existing connection was forcibly closed by the remote host

@AstroSkipper Which of the two versions of HTTPSProxy should I use? I assume one is later than the other as it says "Update", but why are there two versions there, is there a reason to use one over the other?

I can't imagine that would be any problem, but if in doubt you could always attach it to a PM.

The link to HTTPSProxy here is dead.

Are you sure it's not just hidden?

It wasn't the nicest comment to make to a fellow forum member, he can consider himself warned, unofficially at the moment. Whatever you may think of others personally, keep it to yourself please everyone, and stay on-topic. If you feel a real need to dispute with someone, take it to a PM, we don't tolerate public slanging matches on threads here.

Sorry, that was my error, I edited my post when I realised. I was looking for disallowedcerts.sst as I thought that's what the file was called!

OK, you sold me, I'll give it a try! I've been using ProxHTTPSProxyMII for a long time now, and always been very happy with it, but I'm also very happy to look at alternatives.

As far as I'm concerned, "dude" is a slang term, the American equivalent to the British term "mate". Usually fine in informal banter, but not always appropriate in every context, and open to the user being accused of overfamiliarity, and being patronising, during a dispute. This is getting personal, and off-topic of course. I will be wielding my axe if it goes on any longer.

So how does "HTTPSProxy" differ from "ProxHTTPSProxyMII" as ported to XP by @heinoganda? Is there any known reason why one would work in this scenario and not the other?

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!