NotHereToPlayGames

Also, is update.exe "called" just once? Or is it "called" multiple times?

Bingo!

Ah yes, that is correct. BUT... there's still a finite amount of time when one installation ENDS *before* a second can BEGIN.

There is also the way that Windows has to wait for a previous "installer" to completely terminate before another "installer" can begin. Same goes for when you go to "uninstall" something. You can only uninstall one at a time or get hit with a message to wait for the first to complete. The standard "WaitToKillAppTimeout" is TWENTY SECONDS. So if you are installing 150 installers sequentially, 150*20/60 is FIFTY MINUTES of just waiting for those timeouts. I can't speak for ever witnessing these sorts of KBxx install durations because I never install KBxx's. I sometimes slipstream into my install disk, but for the most part I only run "first release" versions of Windows and NEVER UPDATE THEM. The only time I ever "update" Windows is when I go from FIRST RELEASE of a 2016 version of Win10 to a FIRST RELEASE of a 2022 version of Win10. In my XP days, I *NEVER* updated via KBxx. I installed XP. Formatted, installed XP+SP1. Formatted, installed XP+SP2. Formatted, installed XP+SP3. Never anything past SP3 (including never installing any of the "illegal" PosReady2009 stuff).

It sounds to me like you are removing all of the pre-requisite checks. Microsoft KBxx updates don't "install" just because you double-click them, they analyze your system and run checks to see if the update even qualifies for your system. Those checks take time that have nothing to do with writing a file or registry entry.

Interesting. Could the affected tell us what they have these settings at? I have all three DISABLED (always have, will never use, DO NOT TRUST THEM). It would be interesting to see if these "protections" are what is CAUSING this to those affected. But... I don't even think these were present in Iron v109 (the oldest browser being affected, if I recall).

AGREED !!!

Yep! Openly mocking! But I REALLY do think that there is NOTHING THAT CAN BE DONE to "prevent" this. I really do think that! Or why would it not be fixed by now? It's been two months since this issue has been brought to everyone's attention. I kind of view it along these lines, "We have 200 active members, all 200 remain active, we haven't lost any members, therefore this is a NON-ISSUE that we can IGNORE." (I have no clue how many ACTIVE members we have, 200 is probably HIGH but also depends on just what is meant by "active")

I can't help but think that those that are afflicted with this issue is MAKING IT WORSE by confirming the issue exists. Kind of like how most search engines move most-visited or most-relevant to the TOP. Kind of like how fake "unsubscribe" spam links don't really unsubscribe you, but rather inform the spammer that they have a legit email address. By confirming the isssue (over, and over, and over again), aren't you basically creating some form of confirmation "DNS Cache"? By confirming the issue, aren't you basically voluntarily and willfully handing over your IP Address to "whomever is behind this"?

Again, I revert to this, You and I will *NEVER* know.

If something server-level was compromised, nobody is telling the userbase (in my country, these have to be disclosed, but the server does not sit in my country). It's not a "certain browser" issue. Several Supermium users but only one affected. Several Iron users but only one affected. Several Chromium users but only one affected.

The thread title calls it a "redirect". Can still be ISP. I do not use the same ISP as our supervisor (he hosts a website and we do not live in the same 1-of-50 US States, my ISP operates in 15 US States and there are at least 4 US States between us). Again, I revert to this, You and I will *NEVER* know. We have clear indication that MSFN owners, admins, and moderators CAN'T TELL US (citing confidentiality reasons, ADMIRABLE) and CAN'T FIX IT (in my opinion).

Can you run a test? DELETE YOUR ENTIRE PROFILE AND START FROM SCRATCH !!! Is your FIRST visit/search WITHOUT ANY EXTENSTIONS being redirected ON AN ENTIRELY NEW PROFILE ??? Does it take TEN OR MORE visits/searches to get redirected ??? Do you not get redirected until AFTER adding the extensions that you use ???

That's what I suspected (ie, everyone that keeps pointing at User Agent - STOP POINTING AT USER AGENT, that is not the problem). Seems to me that you need to contact your ISP and see what they have to say. Seems to me that it only affects certain countries (maybe we need a list of those countries?). But don't expect any answers from MSFN owners, admins, or moderators.

Not relevant. What IS relevant (because everybody keeps pointing at user agent) - WHAT USER AGENT WERE YOU USING WHEN YOU WERE REDIRECTED ??? My view: If you are using Version 146 (Official Build, ungoogled-chromium) (64-bit) NORMAL USER AGENT, then WE HAVE A PROBLEM. If you CHANGED THE USER AGENT TO SOME SEARCH BOT OR WHATEVER, then YOU CREATED THE PROBLEM WHERE IT OTHERWISE DID NOT EXIST. (but then there still exists an issue with the OWNER of that 'search bot or whatever' - NOT the owner of MSFN, NOT the owner of the browser encountering the redirect)

If I may be so bold, this issue can NOT be fixed or it would have already been fixed by now.

Of course it has nothing to do with Supermium. If you can get past the language barrier and truly follow the entire thread, nobody ever claimed this to be a Supermium issue.

You're missing the point. Not my problem.

Well... Um... Seems to me that the forum admins and moderators really do not want us "regular members" to truly know why this is happening. They've hinted at knowing why it is happening, only to tell us "regular members" this: But even at that, they *CAN'T* fix it. Or so I have to assume. Or it wouldn't still be happening. I've never been hit with this redirect. NEVER. And yeah, that's a GOOD THING. I really don't think us "regular members" will *EVER* be told why this is happening. Even one (but not all) of our moderators had to set up a different browser just to visit MSFN. That, to me, rules out anything in the DNS Chain because his other browsers would seemingly also be affected. That, to me, indicates a CORRUPTION within his browser profile - but only he can test, axe the profile and all remnants *COMPLETELY* and see if the issue persists. On one hand, we can applaud the Apple iPhone route of not sharing "for confidentiality reasons". On the other hand, it only opens up a large can of Conspiracy Theories.

bump (I wanted to hold the record for bumping an outdated post)

That's what I suspected. And also CONFUSES things, if you ask me. I hate to always use my city billpay as an example, but it is the ONE website that always FORCES me to upgrade my browser due to infinite loop unsolvable Cloudflare b&llsh#t. OFFICIAL Pale Moon does the same EXACT thing on the city billpay that OFFICIAL Chrome and OFFICIAL Chromium both do! They WORK until they don't (which is always when the version that I am running becomes TWO MONTHS OLD). Update to a version that is only ONE month old and they ALL can pass the Cloudflare b&llsh#t. Then a month later, the d@mn cycle repeats, ALL of them fail (infinite unsolvable loop) until again updated to something LESS than two months old. The same EXACT scenario has happened FOUR times in the past SIX months. Dang near clockwork! I swear, it's gotta be easier to hack into FBI servers than log into my city billpay! And for Official Pale Moon and Official Chrome to BOTH do this ???

"Passed" a few days ago. "Fails" today. Nothing changed on my end. Unsure if just a (un)timely coincidence.

The HACKER NEWS linked within that article was far more informative than the article itself, IMO.

I don't think it is that "easy". Do we have any info from the Official Pale Moon Team that they are "registered as a developer"?

Cloudflare isn't "out to get" UXP browsers. PERIOD. Cloudflare goes into an INFINITE UNSOLVABLE LOOP even in Chrome/Chromium/Supermim v144 on my city utilities billpay website. This has happened FOUR TIMES in the last SIX MONTHS. The city will not allow any web browser more than TWO MONTHS OLD to log in! You can access the web site and read the web site BUT YOU CANNOT LOG INTO THE WEBSITE. This has been discussed in the past. You have to have an account to log into in order to get the infinite loop Cloudflare. OFFICIAL Pale Moon (which is also UXP!) *IS* able to log into the website IF THE MOST RECENT VERSION. Why in H#LL the city won't allow ANY browser (be it Chrome/Chromium/Supermium AND EVEN UXP PALE MOON) that is more than a mere TWO MONTHS OLD is beyond me! What we need (all of us!) is a publicly maintained list of web sites being blocked by Cloudflare. I have provided my city billpay in the past, but it is USELESS to everybody else not living in my city or with an ACCOUNT TO LOG INTO. A maintained LIST of websites should help developers WAY better than our way-overused "Cloudflare isn't working".