On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019

[Dave-H]

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.

 

[AstroSkipper]

@Dave-H No, you have to set back to year 2020 and only to generate in HTTPSProxy a new certificate valid until 2030.To let HTTPSProxy do that you have to delete the old one called HTTPSProxyCA.crt. After that you can turn back time to current date and time. I did often such manipulation without any serious problems. Believe me! And the best is manipulations of HTTPSProxy don't harm your ProxHTTPSProxy installation. You can try whatever you want.

Edited January 24, 2022 by AstroSkipper
correction

[AstroSkipper]

@Dave-H And if that fails then is my final advice to do all steps described in my post 

once again. Doesn't matter if you did before or not. Do it and check all mentioned problems! I did so and now it is working perfectly. 

Edited January 24, 2022 by AstroSkipper
addition

[Dave-H]

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).

[maile3241]

5 minutes ago, Dave-H said:

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).

Mine are red too. But it works.

[xpandvistafan]

19 minutes ago, Dave-H said:

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).

Mine is all in red but it still works. I do not know why it does not work for you. I have just installed a blank XP Pro SP3 install and followed all the instructions in the kit that I made and it works. Yes, I did get 0x800072F8F if I generated my own certificate through ProxHTTPSProxy that was valid for 10 years from the day it was generated. 

Edited January 24, 2022 by xpandvistafan

[AstroSkipper]

On 1/24/2022 at 2:42 PM, maile3241 said:

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).

In my system when MU searching for updates has finished successfully all connections of HTTPSProxy to MU are red.

https://imgur.com/xFTx1fk

And here my log more readable:
https://imgur.com/GawLOUT

 

Edited January 31, 2022 by AstroSkipper
correction

[AstroSkipper]

And here is my log of ProxHTTPSProxy when MU searching for updates has finished successfully:
https://imgur.com/q5ezkA9

 

@Dave-H Comparing your log to ours I discovered you are using a more recent version of ProxHTTPSProxy. You've got urllib3/1.25.7 and we've got urllib3/1.25.3. I don't know if it is relevant.

Edited January 31, 2022 by AstroSkipper
deletion

[Dave-H]

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.

 

[AstroSkipper]

1 hour ago, Dave-H said:

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.

@Dave-H I am a little bit confused. In your list of Trusted Root Certification Authorities I can see two ProxHTTPSProxy CA certificates. But why is your new one issued to *.update.microsoft.com as well as to ProxHTTPSProxy CA? I do not have that. That's no good I think. The dates look as expected. But I assume you can't have both due to the fact that only one instance of ProxHTTPSProxy should use its certificate. Comparing to my ProxHTTPSProxy CA certificate I would delete the "right one" with "Issued to: *.update.microsoft.com". The ProxHTTPSProxy CA certificate belongs to ProxHTTPSProxy and not to MU website. Truth be told I would rather delete both (make a backup before incl. Certs folder) and let ProxHTTPSProxy create a new one (e.g. from 2020 to 2030 or 2018 to 2028). The idea is before generating a new certificate by ProxHTTPSProxy you have to delete its old one. One instance of ProxHTTPSProxy, one ProxHTTPSProxy CA certificate. For me it looks like a bit messed up. But maybe @Mathwiz could tell us more.

Edited January 24, 2022 by AstroSkipper
correction

[maile3241]

23 hours ago, AstroSkipper said:

@maile3241 As I already mentioned some posts above copy your patched file first to system32\dllcache and then to system32. If it is blocked do it from outside using linux or WinPE. Restart computer and check if both files are still there. And then...hopefully...

But one thing I have to say. It would be much easier if you read your posts a little bit more intently. Hope it'll work finally.

Thanks, it finally worked. Now I have the problem that the search takes forever. I've seen the svchost service using 100% CPU.

[maile3241]

3 hours ago, Dave-H said:

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.

 

Have you tried reinstalling Internet Explorer?

[AstroSkipper]

On 1/24/2022 at 7:49 PM, maile3241 said:

Thanks, it finally worked. Now I have the problem that the search takes forever. I've seen the svchost service using 100% CPU

The old trick to avoid long searches of MU was reinstalling latest cummulative IE update. Resetting of datastore.edb can help too. By the way my search lasts only seconds. 

Edited January 29, 2022 by AstroSkipper
correction

[RainyShadow]

5 hours ago, maile3241 said:

Mine are red too. But it works.

Look at the response codes (first number after the address)

Code for first line is 302, which means redirection.

Code for second line is 200 - success.

Looks fine to me.

[Dave-H]

7 hours ago, AstroSkipper said:

@Dave-H I am a little bit confused. In your list of Trusted Root Certification Authorities I can see two ProxHTTPSProxy CA certificates. But why is your new one issued to *.update.microsoft.com as well as to ProxHTTPSProxy CA? I do not have that. That's no good I think. The dates look as expected. But I assume you can't have both due to the fact that only one instance of ProxHTTPSProxy should use its certificate. Comparing to my ProxHTTPSProxy CA certificate I would delete the "right one" with "Issued to: *.update.microsoft.com". The ProxHTTPSProxy CA certificate belongs to ProxHTTPSProxy and not to MU website. Truth be told I would rather delete both (make a backup before incl. Certs folder) and let ProxHTTPSProxy create a new one (e.g. from 2020 to 2030 or 2018 to 2028). The idea is before generating a new certificate by ProxHTTPSProxy you have to delete its old one. One instance of ProxHTTPSProxy, one ProxHTTPSProxy CA certificate. For me it looks like a bit messed up. But maybe @Mathwiz could tell us more.

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!