Feedback by UserVoice

Brian Podhajsky

My feedback

  1. 646 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    112 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Brian Podhajsky commented  · 

    The above solution is INCORRECT for Office 2019 Build 16.0.11126.20234 32-bit.

    I had the same issue, only affecting one user of many in their org. Never got an error code until after uninstalling McAfee SMB Protection, which I suspected for firewall/network traffic issues. Then I found this article, only to realize that another tech had already been in the registry and created DisableADALatopWAMOverride set to 1. I deleted the key and tried DisableAADWAM set to 1 but this also failed.
    Rereading, I noticed the old key was DisableADALatopWAMOverride while the newer version was listed as DisableAADMWAM
    only after many failed attempts did I realize that there was a typo:
    ADA vs AAD
    deleted the old key, replaced with the following-
    The CORRECT Key for 2019 and possibly other newer versions:
    DisableADAWAM (DWORD) set to Value (1)

    This worked for me without further prompts for the Password. Reinstalled McAfee and the user is good to go.

    It seems like DisableAADWAM may have worked for some people, or maybe they typed it as ADA without realizing it. Very confusing.

    Either way, MS got some 'splainin to do...

    ... just found out about the Mandela Effect on that phrase, so I don't even know what to believe anymore. If the ME applies to registry keys we are done for.

Feedback and Knowledge Base