Not able to login to Power Automate / Can not sign out

[Landmine]

Greetings,

Everything was working fine with Desktop Power Automate until a month ago but now
I have the following critical problem that prevents me using it:

I have my email address as both a personal and work login for Power Desktop.

If I login in using the email to my personal account all is good.

However if I login using the same-same email but to my work account I get the following
error message shown below, login fails and I can not sign out. 
Restarting does not help.
Still stuck facing an indefinite spinning wheel over a "getting things ready..." message.
and I still cant sign out.

Even uninstalling Power Automate Desktop and re-installing does not help.
PAD still stuck trying to login to the same-same bad account.

Changing my computer does not help:
Testing on a brand new Virtual Machine just now..

Any suggestions?

Many thanks in advance.


Full text of the error message follows:
Message = The given key was not present in the dictionary.
Error = System.Collections.Generic.KeyNotFoundException
Full text = System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Concurrent.ConcurrentDictionary`2.get_Item(TKey key)
at Microsoft.Flow.RPA.Desktop.Console.Persistence.Core.Repositories.Environments.OneDriveEnvironmentsRepository.<GetByIdAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Console.Application.Environment.Commands.SetSelectedEnvironmentCommandHandler.<Handle>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at MediatR.Pipeline.RequestPostProcessorBehavior`2.<Handle>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at MediatR.Pipeline.RequestPreProcessorBehavior`2.<Handle>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Console.Host.MainViewModel.<SelectUserDefaultEnvironmentAsync>d__154.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Console.Host.MainViewModel.<OnSigninFlowFinishedEvent>d__142.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

[Guriga]

Hi,
I had a similar experience after I update PAD today (2.17).

Did you try an older version 2.16?

[Landmine]

Hi Guriga,

Many thanks for the good idea,

But where can I get an older version of the PAD 2.16 installer?

[Landmine]

Thread here has exactly same-same unresolved login problem.
https://powerusers.microsoft.com/t5/Power-Automate-Desktop/cannot-launch-power-automate-desktop/td-p...

[Guriga]

Good question.

I haven't got and I didn't find it online, yet.

[Landmine]

Summary List of Notes on other folks discussing related login issues: 

https://powerautomate.microsoft.com/en-us/blog/known-issue-login-troubles/
Suggests something could have changed in Azure Active Directory Settings....

https://powerusers.microsoft.com/t5/General-Power-Automate/Authentication-Error-cannot-log-in/td-p/7...
Suggests:
"checking the properties in the Azure App portal and the "Enable User Sign-In" is set to Yes

https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Connection-error-Power-Automate-Desktop/t...
Suggests, login problems can be caused because of the internet security, "my power automate for desktop doesn’t work on the wi-fi from where i work, but it does work on home wi-fi…"
However: PAD login to my account gets stuck on multiple machines in multiple locations

https://powerusers.microsoft.com/t5/Power-Automate-Desktop/Actions-have-disappeared-from-editor/m-p/...
Suggests: "a way around the problem by installing an older version of Power Automate Desktop - version 2.1.43.20312.
All the actions are now available and working as expected. Obviously not an ideal solution, but it's possible that there is an issue with more recent editions of PAD that causes this rare problem to occur.
This problem is not fixed by the latest version. See the accepted solution - endpoints need to be unblocked. The preview version (2.1.43.20312) from November 2020 will work with blocked endpoints. But only if you have the installer on hand and as a temporary fix.

LIST OF SERVICES REQUIRED FOR RUNTIME
https://docs.microsoft.com/en-us/power-automate/ip-address-configuration#desktop-flows-services-requ...

Not sure if this announcement is relevant:
We determined some users using MSA account are not able to consent starting from February 08, 2022 at 6:15 AM UTC . The issue has been fixed by Feb 15, 02:15 AM UTC.
Last updated: 2/16/2022 1:18:27 AM UTC
https://powerautomate.microsoft.com/en-us/support/

Similar Sharepoint problem with solution:
https://nishantrana.me/2013/05/14/fixed-the-given-key-was-not-present-in-the-dictionary-error-in-reg...
Message = The given key was not present in the dictionary.
Error = System.Collections.Generic.KeyNotFoundException
Full text = System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Concurrent.ConcurrentDictionary`2.get_Item(TKey key)

[Landmine]

Update: Microsoft Technical Support provided the following initial suggestion:

• Uninstall PAD
• Open installation folder of PAD and check for remaining files
• Delete remaining files
• Reinstall PAD
• Log in again

However:

C:\Program Files (x86)\Power Automate Desktop folder is completely removed by uninstall.
No further remaining files are left to uninstall manually.
Re-installed but same-same error.
Still logged into the same-same account...still frozen and cannot log out

[Guriga]

Can you try to log in with a different profile on your PC?

[MichaelAnnis]

Are you still experiencing this issue.  I had something similar happen a few days ago, closed PAD and killed it from Task Manager and then it worked just fine.

[Landmine]

At the moment the only way to continue using PAD is to create a new Windows User Account,
re-install PAD and create a new PAD Account and NEVER, EVER attempt to log back
into the old PAD using the old PAD account as the same-same problem will re-occur.

[Landmine]

Thanks for the suggestion. It  would be nice if such a simple solution worked.

Unfortunately even after a complete re-installation of PAD and Microsoft Tech Support
suggestion to close PAD and delete the file %localappdata%\Microsoft\Power Automate Desktop\msalcache.bin3 
and then try to login back in ...Still stuck again same-same as before

I also try deleting the whole folder  %localappdata%\Microsoft\Power Automate Desktop\    
but somehow PAD is still somehow able to remember the same-same stuck login.

[MT_Head]

I just had the same problem as I'd tried to log in with the wrong account. I followed you %localappdata% path but went to the cache folder as well and deleted all the files in the Accounts folder. It has now let me open PAD and prompted me to re-sign in. All working now. Realise this may be a bit late for you but might help other hitting this problem.