Leaderboard

Bold = loud Italics = emphasis

Don't worry, you're fine. This sort of thing is exactly what this forum is all about!

Stop fighting against people who are trying to provide information! The issue has been seen in Discord Preview, some search engine results, Some versions of Supremium and one version of Iron so far. Posting user agents that are affected are OK but I have a thought that it isn't user agent based. On my Iron install where the redirect happens, I have this user agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Iron Safari/537.36 If I change my user agent in Chrome to that using the Network Conditions option in DevTools, the redirect doesn't occur. I verify that Chrome is using the Iron UA via whatsmyuseragent.com The thing in common is that all browsers are using an older Chromium engine. I do not think that it is a client issue per se.

https://www.techspot.com/news/111434-tofu-brine-could-power-safer-batteries-last-decades.html Tofu Brine could power safer batteries that last decades, researchers say A new neutral-electrolyte battery survives more than 120,000 cycles without fire risk By Skye Jacobs Today (Feb 23, 2026) Bottom line: A mixture most people associate with tofu production could soon help make safer, longer-lasting batteries. Researchers from the City University of Hong Kong and Southern University of Science and Technology have built a water-based power cell that runs on tofu brine – the mineral-rich solution left behind after pressing soy curds. The design replaces the complex, flammable chemistry of lithium-ion batteries with an electrolyte that's as safe as saltwater. In lab tests, the prototype endured more than 120,000 charge cycles, an endurance record that far exceeds today's commercial standards. Typical electric-vehicle batteries degrade after just a few thousand cycles – even long-duration grid systems seldom survive beyond ten thousand. ...

Describe extensively what you have done so far! Normally if all instructions of both posts have been performed properly, you shouldn't have any error codes. Therefore you missed a step. Check all steps again! PS: @WULover refers to these four updates: KB4467770, KB4019276, KB4493435, KB94228-V3. Install them again!

In my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use" you will find the solution for error code 0x80072F8F. Look here and have fun:

Beside the manual method to get access to locked registry keys, as described in linked tutorial above, you can use a tool called Registry Permission Tool. It's freeware and can be downloaded from the homepage of this tool: https://www.xeromag.com/fvshare.html

Where did you get a warning? Everyone can and is allowed to express their opinion. Of course, the music makes the sound. We still live in a democracy and enjoy the right to freely express our opinions. We have to realize painfully again and again that this is not the case everywhere in the world! But anyway, I respect hard work. People are different and behave different. All these proxies are great, my favourite is HTTPSProxy, and we actually should be glad being able to use them. But what I don't understand is how you can keep getting stuck on negative aspects when there are so many positives. There are certainly other things to get excited about.

ProxHTTPSProxy and its reinvented successor ProxHTTPSProxyMII were originally developed by whenever. Therefore, first credits to whenever of course. If you want to know which modifications @heinoganda had made to ProxHTTPSProxyMII, you have to read following thread completely: There you can find all changelogs and information about @heinoganda's releases. For example he created ProxHTTPSProxy_PSwitch.exe to start and set up the proxy automatically and delete its settings when closing. He did a lot of modifications and updating. Simply said its version is more recent than the original version. I wouldn't say we praise him. But it's a kind of respect to people having done hard work to a project. Providing programs in that way I don't like too. You feel like a supplicant if you want a download link. My favourite one is HTTPSProxy. @Thomas S. provided it in form of a download link. Unfortunately the link is invalid for a long time, but I decided to provide a fresh one because it would be a pity if such a program were simply lost. You can find the link under section Downlads in my thread: Anyway, HTTPSProxy is more comfortable, easier to manage and control. In a nutshell, simply great!

Of course, it's just my opinion after analyzing the facts. Anyway, you're welcome!

Exactly! That's why it also works with IE6. Wouldn't it make more sense to use this version instead of @heinoganda's version since you don't necessarily need the PosReady updates? Generally, no! Due to security reasons only. We do not use ProxHTTPSProxy for accessing MU exclusively. The more recent, the more safer! We want to establish secure connections using IE engine in a couple of applications. But for using to access MU only, my answer is yes!

As I mentioned above I do not use these OSs and therefore I can't check what's going on. Windows XP 64 bit has not received any updates since 2015 and has no native TLS 1.1 and TLS 1.2 support. There are no updates to add these features subsequently. Without further analysis, I would say that MU access via IE obviously requires an older version of ProxHTTPSProxy in such a system, heinoganda's version is already too up-to-date. I think there are problems with SHA256, SHA1 seems to work fine. In the changelog of whenever's ProxHTTPSProxy you can read: I guess that is probably the crux of the matter. You have used a version still supporting SHA1 for signing certificates, the more recent seem to be problematic due to signing via SHA256.

Newer browsers do not need HTTPSProxy or ProxhttpsProxy. I use these tools only for accessing web sites using IE or IE engine. Some programs use IE looking for updates or providing other services. Same for email clients. Most of the time HTTPSProxy is disabled in my system.

Of course but I don't trust such features anyway and in case of Malwarebytes Premium for Windows 3.5.1.2522 even more. Your log looks fine until warning and error code 0x801901f6 appears, a cold comfort unfortunately. Please check if my provided config.ini is used and check Trusted Zone if only the three provided urls related to Microsoft exist. Check your Internet Zone too, maybe lower restrictions i.e. lower security level.

Thanks! Good find. Works flawlessly.

@Dave-H Although our ProxHTTPSProxy versions are different here are the equivalent lines of my Windows Update Log if ProxHTTPSProxy is doing its job: 2022-01-29 19:24:30:015 1128 b1c Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-29 19:24:30:140 1128 b1c Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-29 19:24:30:140 1128 b1c Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-29 19:24:30:015 1128 b1c Service ************* 2022-01-29 19:24:30:140 1128 b1c Service ** START ** Service: Service startup 2022-01-29 19:24:30:140 1128 b1c Service ********* 2022-01-29 19:24:30:875 1128 b1c Agent * WU client version 7.6.7600.256 2022-01-29 19:24:30:875 1128 b1c Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-29 19:24:30:890 1128 b1c Agent * Access type: No proxy 2022-01-29 19:24:31:078 1128 b1c Agent * Network state: Connected And you can see MU recognized No proxy.

I want to compare your system to mine. Without HTTPSProxy I can't do that. AFAIK your connection error is related to synchronizaton and you've got other setting than me. We have to do trial and error. For comparing systems they have to have same structure. And our logs speak a clear language. We have different proxy settings. Beyond that MU is connecting to a https version of fe2.update.microsoft.com although you've loaded http version. You can see this in the log. If you want to solve your problem perform the steps above. And you know you can have installed both HTTPSProxy and ProxHTTPSProxy. They have different certificates and both are portable. None of them will harm your system. I use both and they are working properly. The only thing you have to take notice of is not runnig both in RAM at once. Due to the fact that I have installed ProxHTTPSProxy Rev 3d we can't compare these versions and my test partition has still to be installed.

@Dave-H I have compared your log to mine. In your log you can see: 2022-01-29 12:28:25:312 1860 cc4 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0000) =========== 2022-01-29 12:28:25:312 1860 cc4 Misc = Process: D:\WIN-NT\System32\svchost.exe 2022-01-29 12:28:25:312 1860 cc4 Misc = Module: D:\WIN-NT\system32\wuaueng.dll 2022-01-29 12:28:25:312 1860 cc4 Service ************* 2022-01-29 12:28:25:312 1860 cc4 Service ** START ** Service: Service startup 2022-01-29 12:28:25:312 1860 cc4 Service ********* 2022-01-29 12:28:25:343 1860 cc4 Agent * WU client version 7.6.7600.256 2022-01-29 12:28:25:343 1860 cc4 Agent * Base directory: D:\WIN-NT\SoftwareDistribution 2022-01-29 12:28:25:343 1860 cc4 Agent * Access type: Named proxy 2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy: https=127.0.0.1:8079 2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy bypass: <local> 2022-01-29 12:28:25:343 1860 cc4 Agent * Network state: Connected In my log you see a difference: 2022-01-29 14:26:34:093 1128 b38 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-29 14:26:34:109 1128 b38 Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-29 14:26:34:109 1128 b38 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-29 14:26:34:093 1128 b38 Service ************* 2022-01-29 14:26:34:109 1128 b38 Service ** START ** Service: Service startup 2022-01-29 14:26:34:109 1128 b38 Service ********* 2022-01-29 14:26:35:140 1128 b38 Agent * WU client version 7.6.7600.256 2022-01-29 14:26:35:140 1128 b38 Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-29 14:26:35:234 1128 b38 Agent * Access type: No proxy 2022-01-29 14:26:35:578 1128 b38 Agent * Network state: Connected Here are my IE LAN-Settings: HTTPSProxy switched off: https://imgur.com/TRquakL HTTPSProxy switched on: https://imgur.com/w19OXo2 https://imgur.com/iuu80if So switch to HTTPSProxy and do the same settings. You can do it by clicking Inet_CurUser_ProxySettings.reg Switching on and off by SysTray icon. Important first screenshot. Automatic Configuration both options are unchecked. And check your hosts file if it is clean related to MU. And in background ProxHTTPSProxy may not be loaded. Post your Windows Update Log once again.

@Dave-H Well, now we are at the same time and your Windows update Agent works as it should be. Microsoft Update error code 0x80072F8F means ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong. Maybe this can help you: Check in your registry if the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate doesn't exist otherwise delete it. Open system panel, click Automatic Updates and check if it is not greyed out. Then select Turn off Automatic Updates. Open Internet Explorer on the Tools menu, click Internet Options. Under Advanced check if check for server certificate revocation is unselected. Then click the Content tab. Under Certificates, click Clear SSL State. Click OK when you receive the message that the SSL cache was successfully cleared. Under Personal information, click AutoComplete. Under Clear AutoComplete history, click Clear Forms. Click OK when you are prompted to confirm the operation. Click Clear Passwords. Click OK when you are prompted to clear all previously saved passwords, and then click OK two more times. Close Internet Explorer. Start ProxHTTPSProxy and then Internet Explorer. Try to access Microsoft Update one more time. Post your Windows Update Log again.

Yeah, in your posted link there is a second link to a Microsoft site https://docs.microsoft.com/en-us/archive/blogs/win7/windows-update-error-80072f8f and setting "time.windows.com" as time server was the recommendation. Anyway try Windows time service for a next short time and try other time servers. I use "ptbtime2.ptb.de" or use one located in your country. Your log shows you have synchronization errors. The good news your WU Agent works properly we have fixed it. The "WARNING: Unable to establish connection to the service. (hr=80004002)" is blown away.