1

Recently Authenticator stopped popping up a window on my phone to enter the 2 digit number on the PC screen. Eventually I uninstalled the app and reinstalled it. Now I can’t get it to work correctly. Had to go with phone/SMS.

Usually you end up scanning the QR code, only to be eventually be told that authentication failed. Scanning the code again (or entering the code/url) fails because it’s already been used. So back up, come back in and you’ll do it all again. So far, administration/support hasn’t figured out what is wrong.

As the SMS code approach works, I’m not dead in the water, but the geek gene has kicked in - I want this to WORK.

Secondary issue - I had my protonmail MFA in there originally too - but that’s broken - the recovery phrase in protonmail is rejected. Again, not a show-stopper - still works on my phone where I do most of my personal emails.

@windowsauthenticati8132

9 Spice ups
2

Check the time on your phone. Make sure the time is set to auto sync with your providers network, or if possible the same time servers as the auth server.

3

If the mere installation of the authenticator app let you back into your things, it wouldn’t be very useful. Unfortunately, by uninstalling it, you erased the secret keys that were stored for protonmail, microsoft, etc. Because you have an alternate MFA method (SMS) for Microsoft, you can go to Sign in to your account and delete the old “app” method and re-add it, after you’ve also deleted the account from the app itself.
For protonmail or other apps you had in there, you’re out of luck, unless you had backup codes saved somewhere, or another method registered.

4

I tried the aka.ms/mfasetup/deleting the old app method and re-added it. Didn’t work. On the protonmail deal - that’s what I concluded as well. As I say, getting to protonmail via browser is a very low priority.

I wonder if the time factor is an issue. Our org did change infrastructure providers fairly recently - they may be using a different time server. Interesting.

Because I am apparently insane - I might try it again, and expect a different result. Give me something to do and keep me off the street.

Thanks for the feedback.

5

I was able to get to a workable solution - it allows me to enter the 6 digit code on my authenticator ap into the PC. Works. But not the pop-up/enter 2 digits on PC screen method. I did further research and found that the error number 53003 is associated with “BlockedByConditionalAccess” which causes me to wonder if my always-on VPN on my phone is causing problems - it of course routes me through a server in another state. I’ve mentioned this to my technical support people - we’ll see.