Unanswered

Changed Machine Account and Now Unattended Mode Issue

(0) Share

Report

Posted on by choffman

Hello everyone,

My Desktop flows were working in attended and unattended mode on my VM. I was trying to resolve a different issue and updated the Service Account for the PAD machine runtime to my account. I was having connection issues so I reverted back to the default Service Account, but now I can't get my flows to run in Unattended mode.

I tried deleting/creating a new connection. I deleted the old machine and created a new machine. I created a new connection reference in the flow Solution. But the cloud flow will get stuck on the Run Desktop Flow step and nothing appears to be happening.

I also noticed that I can now log into my VM when the Desktop Flows are still running in unattended mode (which I don't think I was able to before), and it looks like the desktop flow was running. The web browser is still open and on the web page I'm feeding in from the Cloud flow.

I think when I changed the runtime account it cached somewhere and is allowing this "partial" connection, but I'm not sure what else I can do to fix this besides an uninstall/reinstall.

Any help is appreciated, thank you!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (5)

Answers (1)

Riyaz_riz11 3,844 Super User 2025 Season 2 on at

Like (0)

Report

Hi @choffman ,

I wish delete the old connection in connection setting and add new machine settings.

If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

Regards,
Riyaz

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (0)

Report

@choffman

You may try to delete your machine from cloud orchestrator first.

Please attempt to uninstall and reinstall Power Automate Desktop, followed by performing a fresh machine registration, and then try running the flow again.

If the issue persists after these steps, consider copying your cloud flow, removing the existing "Run Desktop Flow" action, and recreating it. Ensure to create a new connection for the action as well.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
choffman 21 on at

Like (0)

Report

Hi @Ahammad_Riyaz -

I have already deleted my old connection and added the new connection to the new machine. This did not resolve the issue.

Any other suggestions?

Thank you!

Was this reply helpful? Yes No
choffman 21 on at

Like (1)

Report

@Deenuji -

I tried the steps with only deleting the machine, and then also did those steps of copying my cloud flow, and deleting/creating new Run Desktop flow actions and both of those didn't work.

I was only able to get it working after uninstalling PAD. I'll post the steps that I took.

Thank you for taking the time to help me.

Was this reply helpful? Yes No
Verified answer

choffman 21 on at

Like (1)

Report
Here's what I did and it's now working:

Uninstalled Power Automate Desktop on my VM
Delete all possible files from my Power Automate Desktop folder on VM (some files were still running so I skipped those)
Deleted my Power Automate Desktop Connection References in my Solutions (in cloud portal)
Deleted my Power Automate Desktop Connections (in cloud portal)
Deleted my Power Automate Desktop Machine (in cloud portal)
Reinstalled Power Automate Desktop on my VM
Started Power Automate Desktop on VM and went to Machine setting to set it up on the environment.
Registered my machine on cloud portal, created a new connection, and created new connection references in my solutions.
I then updated the connections in my cloud flows and it is now working.

Was this reply helpful? Yes No