You’re offline. This is a read only version of the page.
We have a Power Automate Desktop Flow that needs to run on a VM unattended. We find that running on attended, it works fine but it is failing when we switch it to unattended. The error message that is it giving out is 'Problem while executing action 'AttachToChromeByTitle'. Failed to assume control of Chrome. No Chrome browser window was found within the remaining timeout period (2 seconds).'
We checked and chrome extension is there and it is working fine when running on attended. our vm/server that we are using is on prem and it has this screen which we think might be the reason why chrome is not getting detected?
Do you know if running unattended, it is bypassing this screen or is it getting stuck on this screen? or is there some kind of login agent that we can use to get the bot to login to this server, press ok and go on with running the flow?
@ArianneC you probably have the Microsoft Store version of Power Automate Desktop installed. Please uninstall it from the VM and install it via the MSI Installer, this should resolve the 'Failed to assume control' issue.
Thank you.
I just re-read your message. The error is on an attach to chrome by title. So are you launching chrome earlier just fine? How can you do an attach when no chrome instance is running?
Our company uses that same type of message on logon, we have never had any issues with Unattended. Are you using the same network user for both Attended and Unattended. It is possible if they are different users, that chrome is not right for the unattended user.
Another thing to try is to use Remote Desktop once the desktop flow is going. Maybe have a flow that pauses for a minute- before trying to start Chrome, then run it, RDP into that machine to see what is going on. Just note that once you make the RDP connection you have to keep it open until the bot is done, at which time it will automatically log off for you and your RDP session will end.
One more thing to consider is that the default setting in for the service that handles opening the session, it will run the desktop at 1024x768. We found that our web apps switch to a tablet UI at that resolution, so we had to investigate the config settings necessary to force higher resolution.
Hope some of that helps.
I would assume that the unattended gets stuck to that screen. Its probably your organizations security settings that make that screen appear.
When you run attended on the VM are you logged in to the machine with same account as the unattended bot? Or is that your account and not the automations account? That would explain why you don't get the screen when running attended but the bot gets it since your account probably has authorization to the VM and the bots account doesn't.
Can you ask the people who admin the accounts to give same authorization as regular employee to the automation account?
#1
eetuRobo
64
Super User 2025 Season 1
#2
Nived_Nambiar
18
Super User 2025 Season 1
#3
CU12050101-0
12
Share
Report
All responses (
Answers (