Desktop flow cannot start on the machine
Do not change service accounts, firewalls or registration as a first step.
Applies to: Power Automate for desktop on Windows.
Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

What does the message mean?
Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.
| What you see | What it may indicate | What to check |
|---|---|---|
| Machine unavailable / runtime error (wording varies) | The machine state, registration, user session or connectivity may be involved. | Do not change service accounts, firewalls or registration as a first step. |
| No message at all | Problems can happen without any message. A blank screen or a missing control is still useful evidence. | Record the visible behaviour, the time and who is affected. Do not guess a code. |

Step-by-step checks
Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.
Record the run mode
- Do this
- Note whether the run is attended or unattended, and the machine or group selected.
- What you should see
- The intended mode and machine are clear.
- Then what?
- If this explains what you see, record it and continue only if the next check still applies.
Check the visible machine state
- Do this
- Ask the machine owner whether it is on, reachable and in the expected session state.
- What you should see
- The observed state is recorded without interrupting sessions.
- Then what?
- Record the result without changing settings. Stop if work, data or security could be affected.
Capture the exact error
- Do this
- Read the run error and the runtime version if shown in normal menus.
- What you should see
- A specific error is available.
- Then what?
- Use only the approved action described here. If it does not match your screen, stop and ask IT.
Escalate runtime diagnostics
- Do this
- Ask the authorised machine administrator to review the runtime diagnostics.
- What you should see
- The issue is routed without changing services or security settings.
- Then what?
- If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.
When to stop and contact IT or the owner
- Work could be lost, or you cannot tell which version is current.
- The problem repeats, or a managed setting blocks you.
- A step would change production data, shared connections, permissions or security.
What to put in your support request
The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.
Microsoft reference
Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.
Related guides
Was this guide helpful? Leave feedback
Tell us what worked, what was unclear, or what is missing. Feedback is private and goes to The Workflow Lab for review. It is not shown publicly and is not an IT support request.
The Workflow Lab is independent of Microsoft and is not your employer’s service desk.