AstroSkipper

@Dave-H Great! I'm glad your system has got back all features you wanted to have.

Here: Just to clarify: 360Chrome = 360 Extreme Explorer

The proxy has a lot to do. Checking web sites, generating cerificates, comparing web site addresses with config.ini settings and so on. Poor proxy! And there might be another cause for such loss of speed. You're running Mwarebytes 3.5.1.2522. It has a web filter function and this might cause such loss of speed either. Switch off web control function and do your speed test once again!

But for these purposes only speed doesn't matter. Isn't it?

I do have that too and that's absolutely normal. A lot of programs have one main instance calling up a second one probably with different tasks. For example 360Chrome does the same. First 360Loader.exe calling up 360chrome.exe calling up a second instance of 360chrome.exe and more of them. Of course there are a lot of proxies slowing down speed. Due to the fact that I use these proxies for Internet Explorer access or Internet Explorer engine access only it doesn't matter for me.

@Dave-H This can be answered easily. It depends on what the user has done when installing ProxHTTPSProxy CA certficate. If you import ProxHTTPSProxy CA certficate by clicking right mouse button it'll be installed under Trusted Root Certification Authority but for current user. If you import ProxHTTPSProxy CA certficate by using Microsoft Management Console mmc or Internet Options Control Panel applet selecting "show physical stores" of IE you've got the option to point to Trusted Root Certification Authority but for local computer. Therefore all of us installed that certificate under Trusted Root Certification Authority physical store but some of us under account current user and others under account local computer. This is the reason why heinoganda's ProxHTTPS Cert Installer is working for all of us. His installer imports due to automatical selection the certificate PROXCERT.p7b (other format of this certificate) correctly but of course installing the old well known certificate valid until 2025 only. This installer is a modified Roots Certificates Update installer and you know these certificates it has to install are added under account local computer generally. Furthermore there is a general positive effect for those loving Windows XP (and 2000 or Vista). If correctly integrated into the system we are all now able to use a freshly generated 10 years valid root certificate of ProxHTTPSProxy or HTTPSProxy as long as Windows XP, Internet Explorer access to WWW, TLS 1.2 functionality, Microsoft Update for Windows XP or the user himself still exists.

As @maile3241 already said opening of ProxHTTPSProxy.exe generates automatically a new CA.crt if none is in its program folder. But first you have to delete all certificates in certs subfolder and update your cacert.pem as described in document file.

You're absolutely right! Talking and philosophizing about a problem you haven't got in your own system is contraproductive. So I produced the problem you all had got and could analyze what was going on. The best way someone can have. Btw I installed ProxHTTPSProxy 3e (you can remember!) for testing purpose and it is working perfectly.

I already knew the alternative way to import certificates using IE but I want to do it in a clear safe way. It was a really long odyssey to find a final solution. I hope it'll work for all of us. Btw I provided links to Windows Update Reset Tool (Script). Have you already looked into? I think it is an interesting tool if problems due to MU occur.

Final fix of error code 0x80072f8f while accessing WU or MU web site @Dave-H, @RainyShadow, @maile3241 and all other interested people, I have definitely solved the problem getting error code 0x80072f8f. I've done a second ProxHTTPSProxy installation just due to testing purpose. I let ProxHTTPSProxy generate a new CA.crt valid until 2032 by deleting old CA.cert file in ProxHTTPSProxy's program folder and opening ProxHTTPSProxy.exe afterwards. Then I installed this root certificate. But it didn't work either. I got error code 0x80072f8f too. I analyzed what had happened and found out it was installed in Trusted Root Certification Authority but for current user only. And that's the cause of the problem. It has to be installed in Trusted Root Certification Authority of local computer anyway. How is it done? Open console by typing mmc, add a snap-in for certificates, then choose for local computer and import your recently generated ProxHTTPSProxy CA certificate to Trusted Root Certification Authority. Finished. First a screenshot of MU using ProxHTTPSProxy along with recently generated ProxHTTPSProxy CA certificate valid until 2032: And here is a screenshot of my Trusted Root Certification Authority - local computer: Hope this will be the final solution to get rid of error code 0x80072f8f forever! PS: More detailed information relating to ProxHTTPSProxy and HTTPSProxy you can find in this article: Kind regards, AstroSkipper

Ok, on the one hand you solved your connection problem using HTTPSProxy and that's fine, but on the other hand 2025 is your deadline of accessing to MU web site. @Dave-H won't help that either because the original provided ProxHTTPSProxy root certificate doesn't work for him accessing to MU web site.

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

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!

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!

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.

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.

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.

Due to your HTTPSProxy failure did you do what I advised you urgently some posts before?: 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.

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.

Welcome to the selected members troubleshooting error code 0x80072F8F! Which proxy do you use? If you are using ProxHTTPSProxy you have two choices of config.ini files. The one file is mine: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file., the other is the config.ini of @maile3241: https://msfn.org/board/applications/core/interface/file/attachment.php?id=49135&key=c915b3197ea8b62e406422ccfec16ea4. Each of them is working in their system but they are different. Try them and report if one of them does the trick or not!

In my little guide I already mentioned the problem with Automatic Updates are greyed out: The solution is to delete this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

That's a very good question. In my real Windows XP system the MU web site fix is working perfectly too.

And this is just the problem. Some of your statements are confusing. Please clarify! And I know you are running HTTPSProxy in your XP vm but that wasn't what I suggested. Please take time to read and understand what I' ve written and tried to suggest!

Both proxies base upon same source. So both have to work as they do in my system. But you said ProxHTTPSProxy would work. So use it in your host system and configure your vm to access to it only for https as @RainyShadow suggested.

I still have assumed you are using my config file but you said it wouldn' t work for you. Therefore I suggested to modify the mentioned section in this file: