Fall Creators Update (Version 1709) of Windows 10 breaks Duo for Windows Logon’s support for Microsoft Accounts

[Nebb]

Ever since Windows 10 decided to the upgrade to the latest Fall Update. Whenever I RDP into my computer the Duo Login Prompt does not load, it does not send the push notification. Thus I am unable to login remotely. I have uninstalled and reinstalled with the latest version of Duo with no success.

Any ideas?

[Chuck5]

I have not edited the registry or made any other changes. The only changes that have occurred are
Windows Updates. The Live account is working for all reconnects and connects, and I receive a Duo prompt each time.

[DuoKristina]

Do you still have a local account present on the system that works in addition to the Live account, or is the Live account the only one?

[Chuck5]

@DuoKristina

On both systems (the one where I can login and the other where I must reboot to login) I have one Live account and one different local account. Both computers use the same Live account.

On both computers, for the Live Account, I checked to verify that it is using a Live account instead of a local account. I went under Settings->Accounts and there is the option to “Sign in with a local account instead”.

[DuoKristina]

Thanks for clarifying that! I believe in testing we’ve seen that with RS4/RS5 Live accounts work as long as there is still a local account on the system.

We are still actively in communication with Microsoft about the ultimate root cause for issues with the Live credential provider and what mitigation will work for all use cases.

[Chuck5]

I was unable to find any updates to MS Case 117121217311532.

Any status update on this?

[Peter_Berbec]

Mind posting a list of the last dozen or so update you received? It’s possible Microsoft hot fixed this and we can figure out where from that information.

[Chuck5]

@Peter_Berbec

This is a relatively new computer, I only have three Windows Updates on here.
KB4338853
KB4343669
KB4338819

[Duo_RDP_User]

Something changed this week to SOLVE this issue for at least 2 of us - this hasn’t worked for me since October 2017 and just today it started working. I have a different set of recent updates tho from Chuck (KB4345421, KB4338832) but we do have KB4338819 in common. That the fix? Or did something else change here, on the cloud live account side maybe?

Worth a try again if you’ve been watching this issue…And thanks sharing Chuck!

[jbize]

No Joy yet.

I tried deleting the whitelist registry property on two Win 10 machines with the latest updates (including KB4338819) and the Microsoft accounts immediately “disappeared.” Rebooting didn’t help. I’m sure it doesn’t matter, but one is “Windows 10 Home” and the other is “Windows 10 Pro.”

Both machines have local accounts too. (Else getting back in would be a challenge.)

[Chuck5]

@johnbize

What version/build of Windows are you using?

[jbize]

Windows 10 Pro, always up to date.

[jbize]

Something seems to have changed with a recent Win 10 update, but it might be Monday before I can really check it out. On one of the laptops (with the ProviderWhitelist property), a user was challenged by Duo 2FA while logging in to his Microsoft Account.

Hopefully I’ll have something more to report next week when the laptops are available (in the office) again.

[jbize]

Nope. It’s still not working.

There is one user that is able to log in to one laptop with his Microsoft account and get the Duo 2FA challenge. His account is also visible with the ProviderWhitelist property removed. So it is functioning like a local account even though it is not.

I added my own Microsoft account to the laptop and was not able to get it to work.

So still looking for any news from Duo.

[DuoKristina]

We continue to work with Microsoft on this.

If you haven’t already done so, you can contact Microsoft support and attach your org to our existing open case #117121217311532.

[Antony Paul]

It has been over a year since this issue started. Might we see this solved in 2019 - who knows?!