Leaderboard

Totally understood! For me, it's FIREFOX !!! To this day, it is the only program that has ever resulted in a complete reformat/reinstall. That was the late 90s and the sour taste still remains. Long before things like Proxomitron, uBO, NoScript, et cetera. The sour taste *never goes away*.

Thanks. Not contradicting you, just as I told you, had a bad experience with Comodo and it's the first time Sphinx has caused a very particular problem. Been using it for 4 years now and everything was normal. Does its thing, not intrusive, super light. Anyway, now I have couple more programs to test! Reality is I need to go "fishing" and also start collecting firewood 'cause winter is coming. I'll let you know as I progress. Thanks again, I'm humbled.

re: "lightweight" I'm showing Sphinx 6.1.9.53 (I've tried three different downloads for 7.5.100.200 but they all show 6.1.9.53 in Help/About) to use around 3 MB RAM. And Comodo 2.4.x to use around 11.4 (v2.4.16.174) to 13.5 (v2.4.17.183) MB RAM. But Sphinx is a LIMITED version that throws NAGS about not being able to do this or that without upgrading to Plus Edition !!! While Comodo 2.4.x is a REAL *FULLY FUNCTIONING* non-limited version that PUTS YOU IN THE DRIVER'S SEAT. Not to sound rude or whatever, but you can stick with lightweight and LIMITED or run something that actually WORKS but uses a little more RAM.

Any of the 2.4 versions. You can't go back as far as the 2.3 versions because they require a phone-home activation. The version I used to use is Comodo Firewall Pro 2.4.18.184. I could not find a download link without doing too much digging, but here is source (scroll all the way to the bottom) for 2.4.16.174 and 2.4.17.183. https://www.afterdawn.com/software/security/firewalls/comodo_personal_firewall.cfm#all_versions

@reboot12 We work together Dietmar

Same here. Plus Edition messages and wouldn't let me EDIT but did let me DELETE. And since my XP is locked down and NOTHING at the OS-level tried to connect after deleting, they did not reappear. They "probably" would have reappeared at reboot, but I didn't get that far, my goal was just to get FDM to download.

Screencaps of the profile that I use:

I technically don't do either. It's not "installed" but it's not truly "portable" either because I save my profile in the registry. Step #1) My XP installations simply get the .exe and the .chm "copy-pasted" / "extracted" into a folder. Step #2) I import the profile I use via an archived .reg file (herein renamed as MSFN). Step #3) I run the .exe, load the profile, and Apply Settings. Reboot (not sure if required, just good practice after these types of changes). This is the profile that I use:

We gotta take it all, with many grains of salt. I hope I don't come back, a week from now, and read my writing here. I'd have stop myself from edition all the things I say, that are "kinda" right, "close" to right, and "maybe, I shouldn't post when I haven't slept well". You guys bare with me pretty well.

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