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

[AstroSkipper]

8 hours ago, RainyShadow said:

What is the exact link you use for MU?

The best is to avoid  https links related to MU. This is what most of us use: http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en.
If you stuck at installing activex addon check your security settings in Internet Options in your IE. Lower the security level in Internet Zone only! In this thread I've provided a lot of approaches to solve error code 0x80072F8F. Try them! Maybe one of them will work for you.
The goal is to figure out why it is working for some of us like me and for others generating the error code 0x80072F8F.

Edited February 11, 2022 by AstroSkipper
addition

[AstroSkipper]

2 hours ago, maile3241 said:

httpsproxy gives me problems too.

Due to your HTTPSProxy failure did you do what I advised you urgently some posts before?:
 

Quote

At first avoid running both in RAM. That won't work at all. You have to exit the unused one to use the other.

You can' t use both proxies in RAM at the same time.
Then another idea. You said you had generated a new HTTPSProxy CA certificate in the past. Did you delete all certificates in certs subfolder of HTTPSProxy's program folder subsequently? If not it won't work at all.

Edited February 11, 2022 by AstroSkipper
addition

[maile3241]

I found the problem for httpsproxy. Here my solution:

Close httpsproxy. Delete all Certificates from the folder "Certs". Delete the generated Certificate from httpsproxy and replace it with mine and run the Certinstaller. Call up Windows Update again and try to search for updates.

It works fine for me.

HTTPSProxyCA.crtProxHTTPS Cert Install.exe

Edited February 11, 2022 by maile3241

[AstroSkipper]

16 minutes ago, maile3241 said:

Close httpsproxy. Delete all Certificates from the folder "Certs". Delete the generated Certificate from httpsproxy and replace it with mine. Call up Windows Update again and try to search for updates.

It works fine for me.

So I've been right. You forgot to delete all certificates in certs folder the last time when you had generated a new HTTPSProxy CA certificate. Deleting was the solution. I mentioned that several times in the past. As I told you if one of them works the other has to work too. They are from same source.

[maile3241]

6 minutes ago, AstroSkipper said:

So I've been right. You forgot to delete all certificates in certs folder the last time when you had generated a new HTTPSProxy CA certificate. Deleting was the solution. I mentioned that several times in the past. As I told you if one of them works the other has to work too. They are from same source.

I always deleted it before. Still, it never worked. This "new" regenerated certificate seems to be the problem.

[AstroSkipper]

13 minutes ago, AstroSkipper said:

replace it with mine

Providing a personal certificate which was generated only for your proxy isn't a good idea due to security reasons. Using this certificate by other people is a security risk for your encrypted connections. And I doubt that the cause of failure was the HTTPSProxy CA certificate only. It was most likely the combination of HTTPSProxy CA.cert and deleting certs in certs subfolder.

Edited February 11, 2022 by AstroSkipper
addition

[maile3241]

1 minute ago, AstroSkipper said:

Providing a personal certificate which was generated only for your proxy isn't a good idea due to security reasons. Using this certificate by other people is a security risk for your encrypted connections.

This certificate comes from ProxhttpsProxy. I don't think it's a risk.

[AstroSkipper]

7 minutes ago, maile3241 said:

This certificate comes from ProxhttpsProxy. I don't think it's a risk

Just to clarify and to avoid misunderstandings you copied the ProxHTTPSProxy root certificate in HTTPSProxy's program folder to use it there? Are you sure? I can't hardly believe that.

[maile3241]

Just now, AstroSkipper said:

Just to clarify and to avoid misunderstandings you copied the ProxHTTPSProxy root certificate in HTTPSProxy's program folder to use it there? Are you sure? I can't hardly believe that.

Correctly.

[AstroSkipper]

3 minutes ago, maile3241 said:

Correctly.

In my system both proxies generated their own root certificates to work with. I do not use the pregenerated root certificate of ProxHTTPSProxy either and both are working flawlessly. Just a reminder!

[maile3241]

Just now, AstroSkipper said:

In my system both proxies generated their own root certificates to work with. I do not use the pregenerated root certificate of ProxHTTPSProxy either and both are working flawlessly. Just a reminder!

For me it only works with this one.

[AstroSkipper]

1 minute ago, maile3241 said:

For me it only works with this one.

So how many ProxHTTPSProxy root certificates do you have installed in your system's Trusted Root Certification Authority? Please have a look and provide a screenshot!

[maile3241]

26 minutes ago, AstroSkipper said:

So how many ProxHTTPSProxy root certificates do you have installed in your system's Trusted Root Certification Authority? Please have a look and provide a screenshot!

These are mine:

[AstroSkipper]

4 minutes ago, maile3241 said:

These are mine

Ok, you have installed the same ProxHTTPSProxy root certificate twice, one for ProxHTTPSProxy itself and one for HTTPSProxy. Is that correct?

Edited February 11, 2022 by AstroSkipper
correction

[maile3241]

2 minutes ago, AstroSkipper said:

Ok, you have installed the same ProxHTTPSProxy root certificate twice, one for ProxHTTPSProxy itself and one for HTTPSProxy. Is that coorect?

Right. These are urgently needed, otherwise it won't work. I edited my post above again.