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

    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 do with Edge browser….

    On the Patchmanagement.org list the following was reported on Edge 97:

    “Hello everyone,
    We’ve been seeing a weird issue where users are having Microsoft Edge open at log on. I was able to trace it down to coming from MicrosoftEdgeUpdate.exe. There is a scheduled task to run Edge update with two triggers: one at logon and one at a random time period. We’ve found that disabling the logon trigger stops Edge from opening at log on, but I’m a bit wary of disabling this for everyone, even if there is a secondary trigger available.
    Has anyone else seen this?”

    “Yes, version 97 that dropped on Thursday 1/6 added two registry keys found at the below location. The AutoRunOnLogon is set to 1 by default, if you change it to 0 it fixes the issue. Our machines are set to only get updates from our WSUS servers, but this one bypassed if the machines were not behind a firewall that specifically blocked all of the Microsoft update servers.”

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}\Commands\on-logon-autolaunch
    Type: REG_DWORD
    Value Name: AutoRunOnLogon
    Value: 0 (zero)

    Note if you need this registry value – the link to automatically fix this is here.

    Next up is Firefox.

    As noted on the 9to5mac blog,  Firefox may hang on certain web sites. If you are seeing this, edit the following:

    Open a new Firefox window.
    Type about:config in the URL bar. This will open a settings screen.
    Search for the setting ‘network.http.http3.enabled’.
    Set this setting to ‘false’ to disable HTTP3.
    Then, fully close and restart Firefox.
    This workaround applies to all desktop versions of Firefox, so it’ll work regardless of whether you are on Windows and Mac.

    Of course, once the actual software bug has been resolved, you’ll want to go back and re-enable HTTP3 so that you can use HTTP3-dependent services in the future.

    Edit 1/16/2022: Note Firefox has resolved this bug so you should not be seeing this in your Firefox browsers.

    So are you seeing either of these two bugs in your browsers?