Tips for the weekend – Browser checkup – January 15, 2022

Topic

New Reply

This weekend I’ll want you to check if you are being impacted by either of these two browser bugs that popped up recently. Video here The first has to
[See the full post at: Tips for the weekend – Browser checkup – January 15, 2022]

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Alex5723

Reply | Quote

Replies

The firefox issue has been going on for some time (at least in nightly/developer editions). Maybe 10 months?
They said it was fixed on cloudflare’s end but it never ended up working properly.
I’ve had it disabled in Firefox Developer Edition since April 2021. Very concerning that they appear to have shipped such a broken feature to release channel users.

Reply | Quote

Earlier today, Firefox became unresponsive due to a change in defaults by a cloud provider which triggered a Firefox HTTP/3 bug. We disabled the configuration change and confirmed this fixed the issue.

Reply | Quote

I have Edge 97 but don’t have Commands\on-logon-autolaunch like you show. Values are not set in my Edge 97. Windows 10 Pro 21H2

As for Fx, I’m on Fx 60.9ESR so don’t have that setting. I have current Fx Portable so I’ll close this version and check it.

On Fx Portable I have Fx 91.4 ESR and that setting does not exist on it.

I’m glad I wait and do not get the latest version of browsers immediately.

Reply | Quote

@Mele20, I have the same Edge 97 problem (Version 97.0.1072.62). I have ‘on-logon-autolaunch’ registry entry but no ‘AutoRunOnLogon’, just ‘CommandLine’.

Fx at 96.0.1 now but no http3 problem noted prior to that.

Dell Inspiron 16 Plus 7640 Core Ultra 7 155H 32GB Win 11 Pro 23H2 (22631.5189)
Dell Inspiron 15 7580 i7 16GB Win 11 pro 24H2 (26100.3775),
Microsoft 365 Version 2502 (18526.20168)
Location: UK

Reply | Quote

Win10 Pro 21H2 with Edge 97 (v97.0.1072.62) and there is no Commands\on-logon-autolaunch key in my registry.

However, there is a Commands\on-os-upgrade key with AutoRunOnOSUpgrade and CommandLine entries.

AutoRunOnOSUpgrade = 1

CommandLine = a cmd command that runs the Edge setup.exe program.

Reply | Quote

I believe the FireFox HTTP/3 bug in version 96.0 was just fixed in the latest version 96.0.1 released on 1/15/22 as reported by Martin Brinkmann on ghacks.net

Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS

1 user thanked author for this post.

lmacri

Reply | Quote

Just another Forum Poster wrote:

However, there is a Commands\on-os-upgrade key with AutoRunOnOSUpgrade and CommandLine entries.

Yeah, I have that also. So, does that mean that if we stay on Windows 10 that we won’t have to deal with this? Only if we move to Windows 11?

Reply | Quote

Here is what my Registry looks like at that location:

Edge Version:

Maybe this is just on Domain connected computers?

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

I see something similar and what I did before I got here. I am behind so on Win10 Pro 20H2 64-bit.

Originally I went in to have a look and there was nothing in Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\Commands\ . So I used regedit to add key “on-logon-autolaunch” and made a mistake. Next I saw a 3 keys added: “on-logon-autolaunch”, “on-logon-startup-boost” and “on-os-upgrade”. Both “on-logon-autolaunch” and “on-logon-startup-boost” have the “AutoRunOnLogon” set to 1 while “on-os-upgrade” has “AutoRunOnOSUpgrade” set to 1. I changed “AutoRunOnLogon” to zero and you can see the 3 current keys.

The 2 “AutoRunOnLogon” Registry keys deleted after I set the values to zero.

Reply | Quote

I had no problems with Firefox 96.0.  Still waiting for .1.

Edge – what Edge?

 

Reply | Quote

To get FF 96.0.1, simply click on the “Help” item after clicking on the “Hamburger” icon on the right side of FF’s open window and then select the “About Firefox” item. That will both tell you the current version of FF that you’re running (96.0 per your statement) and should also provide you with a button to click to download and automatically install the update that will take you from 96.0 to 96.0.1.

Reply | Quote

Well, I am using MSEdgeRedirect on my Windows 10 Pro 21H2 system and even though I do still have an Edge icon to click, MSEdgeRedirect does such a good job that I always get Chrome to open even when I click on the Edge icon.

Reply | Quote

I’m on Win 10 21H2 Pro x64 fully updated through December’s patches (build 19044.1415) with FF 96.0.1 and Edge 97.0.1072.62 and have had no issues mentioned in Susan’s blog post. Even in FF 96.0 I didn’t notice any problems accessing sites.

I do have both Task Scheduler entries mentioned and the first one has two separate triggers which it’s always had. No problems whatsoever with Edge launching when I or anyone else log on to the computer.

I have the registry key mentioned, with the path ending in the \on-logon-autolaunch key, but I don’t have the DWORD value mentioned in Susan’s  blog post, only a REG_SZ command line entry, exactly as shown in @RetiredGeek ‘s post above. Because of this, I’m with him in that I think the Edge autolaunch issue is limited to machines that are Domain joined.

Reply | Quote

Mine are domain joined at the office and I’m not seeing it there.  Maybe on certain versions of Windows 10?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I have not had the error with Firefox, but I have been getting Edge opened at startup.   Like several others above, I did not have that registry Dword.   However, I just added it under the folder of the same name.  I will see if this fixes the issue.

Reply | Quote

Edge…

It’s Microsoft trying to copy Avast’s trick with their “Secure browser”. Open it automatically when Windows start and people won’t notice they are using your monetizing browser. Wow, would they aim low if that was true. The thing is… I am really not sure if this joke is more true or false, especially considering the last few years of similar “oops” moments.

What, clicking X on a Window doesn’t mean “go ahead, stop bugging me and install Windows 11? Oh, probably the new intern didn’t get the memo. Everybody else knows about it from Windows 10.”

Reply | Quote