Leaderboard

This one in particular wasn't even "disguised", the .js file has "browser-detect" right in its name. Watch that uBlock LOGGER and you will learn to spot these before you know it. The LOGGER even has a little arrow to click that opens the .js file in a new tab so that you can read the javascript. Reading these will not turn you into a "coder", but you will learn things to watch for. Such as the browser-detect js being discussed here (discourse) does use Firefox's user agent to define if "unsupported" but does not test for Edge or Chrome user agent. And a small list of CSS entries which define if "unsupported". I've seen more **CSS** render websites unsupported in the last couple of years than javascript functions, which is an odd twist of fate as it used to always be the other way around.

First, welcome to the MSFN forums ; I take it you are using FirefoxESR-115, now on v115.27.0esr, supposedly to be EoL'ed on Win7/8.1 with the next, last, release v115.28.0esr ... Do you, by any chance, have uBlock Origin installed in your FxESR-115 profile? If yes, there's a way you can continue accessing the full version of Discourse-based forums in FxESR-115; read this post ; basically, you'd have to create below custom filter: ! Discourse-based forums ||*/browser-detect-$script,important uBO -> dashboard -> My Filters -> add above code -> Apply changes (header of tab) -> exit dashboard then delete discourse-forum cookies (for good measure) and reload the forum page... Can you please be more specific? Which version is that exactly? Help -> About r3dfox -> ? r3dfox has recently moved into a new GitHub repo, with new Releases section ... I'll assume you currently are in v140.0.4 (not the latest, BTW) ... Did you just transplant/migrate your full FxESR-115 profile to r3dfox-140 ? Although r3dfox is Firefox-based, such big jumps between major versions are prone to profile corruption ... I would advise you start from a clean redfox profile and then, progressively, tailor it to your own needs (settings, extensions, importing bookmarks from FxESR-115, etc.) ... In FxESR-115, load about:logins (Password Manager); click the 3-dot-button (top-right) and you should see a context option to "Export Passwords"; this will save ALL your login credentials to a CSV file; via a similar, but now reverse, procedure, you can import this CSV file to r3dfox and have all your passwords restored! (Take good care of that CSV file, as it contains the passwords in unencrypted, human-readable, form). Best regards ...

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

@Dave-H Damn! Quick view of your Windows Update Log shows your Windows Update Agent is working correctly now. That's fine. Ok, which time server do you use for time synchronization? And is your computer part of a domain?

Yep , you're right , Vista Home Premium ! I do not remember the exact model . Yes , it was HP Pavilion with a thin remote control . The temps were fine , esp. at idle , I remember I was playing Dungeon Siege 2 when it caught fire . I never had it overheated . It was standing on my table , the air conditiong was on. P.S. You see , the same as I was told "HP cheaped out on the cooler". I also had an HP printer which went bad after a year ! They lost a customer , I do not by anything from them since .

Any idea why x86 systems don't have that problem with Haswell ? By the way , I'm not sure if you remeber , back in the day (I think in 2007 Vista already had the exact same black screen of death on some systems , they even had a patch , but it was deleted from servers. It had the SAME logon failure error. Some people wrote that the reason was the changed activation process , I do not know if that's true . I never had it with my Core Quad during that days. Take a look here : https://www.gfisk.com/windows-vista-logon-screen-of-death/

Hello , really !?!? I think 512MB RAM is more like 2004 - 2005 , sorry if I'm mistaken , though . I'm from Europe . In 2007 we had 1gb DDR2 as a bare minimum even on cheap models. At our local stores most were 2GB and expensive ones - 4GB . I had Toshiba Satellite A50 with 512 of RAM in 2004 and it was NOT a gaming laptop , it was a budget model with Intel graphics and a tiny ATA HDD.