Winautomation login with Power Automate Licence stopped working

(4) Share

Report

Posted on by 3TA

As of today WinAutomation with Power Automate Licence Login has stopped working.

I have a per user Power Automate Attended RPA licence.

I have just had a windows update (Windows 10) and since then WinAutomation has asked me to log in again. When I submit my Power Automate / Azure email credential I get the following.

Sorry, but we’re having trouble with signing you in.

AADSTS700016: Application with identifier '7afbe641-8db0-4580-96d1-b2b58538a3f3' was not found in the directory 'XXXXXXXXXXXXX'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Troubleshooting details

If you contact your administrator, send this info to them.

Copy info to clipboard

Request Id: d8c6c13e-e816-4bab-999c-9020aca34700

Correlation Id: 34e8b54b-dc22-4f27-bfdd-348299f6bdc4

Timestamp: 2022-11-03T17:24:56Z

Message: AADSTS700016: Application with identifier '7afbe641-8db0-4580-96d1-b2b58538a3f3' was not found in the directory 'XXXXXXXXXXXX'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Flag sign-in errors for review: Enable flagging

If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

I checked in Azure and WinAutomation was present in the Enterprise Apps section. I tried setting the flag but it did not show up in Azure. I deleted it from there thinking it would reset when I signed in but it has not and I dont know how to get it back or restore function to WinAutomation.

I need WinAutomation to work again, I am in the middle of a business-critical development and I have thousands of hours of work in my WinAutomation database, going back since 2015. There are numerous problems moving this over to PAD which I will not go into here, but it is going to be an enormous undertaking. I need WinAutomation to function.

I have tried to get support through the Power Automate licence route but when I try to log in it does not recognize my Azure/Power Automate credentials.

Please help.

Please advise how I can restore full functionality to WinAutomation with my Power Automate Unattended RPA licence using my Azure login details as before.

Categories:

General topics

I have the same question (0)

All responses (78)

Answers (1)

carlos_slim 35 on at

Like (2)

Report

Same here. I have too many processes that can be migrated in a matter of days.

Was this reply helpful? Yes No
ApexOrigin 150 on at

Like (1)

Report

Same error for me.

Says to "contact the administrator." Don't you just love it when you get that message and you are the administrator!

Was this reply helpful? Yes No
ApexOrigin 150 on at

Like (1)

Report

Has anyone opened a ticket yet?

Was this reply helpful? Yes No
prit6690 4 on at

Like (1)

Report

Did any one get solution ?

Was this reply helpful? Yes No
ApexOrigin 150 on at

Like (1)

Report

I am still waiting on a call back from support. It was difficult opening a ticket with their awkward automated system, but I am finally in the queue after being bounced around. Ticket said they would contact me in 8, but didn’t say mins, days, weeks, months, years, decades, centuries….

Was this reply helpful? Yes No
3TA 74 on at

Like (0)

Report

How did you open a ticket?

I am going to have to spend today finding a solution to this.

Also I have noticed WinAutomation has disappeared from my apps in power automate admin. But I now have some kind of health app, and dynamics 365 apps in there.
Does anyone have the same?
Could be because I deleted the app from Enterprise apps in Azure.
Any body from power platform or azure in here I can tag?

Was this reply helpful? Yes No
3TA 74 on at

Like (0)

Report

Also can anybody else confirm that this occurred after a windows 10 update? A "feature" update I believe.

Was this reply helpful? Yes No
MathiasRT 24 on at

Like (1)

Report

Hi,

We are experiencing the same issue.

Has anyone heard from Microsoft on the matter?

Was this reply helpful? Yes No
3TA 74 on at

Like (0)

Report

Nothing here so far.
Can I ask did your issue occur after a Windows 10 upate?

Was this reply helpful? Yes No
MathiasRT 24 on at

Like (1)

Report

I thought so initially, but i have the same error on a machine running Server OS

Was this reply helpful? Yes No