|
| 1 | +--- |
| 2 | +title: Troubleshoot FailedToTakeScreenshot Errors During Computer Use Actions |
| 3 | +description: Learn how to resolve a "FailedToTakeScreenshot" error that occurs during computer use actions in Microsoft Copilot Studio. |
| 4 | +ms.date: 09/22/2025 |
| 5 | +ms.reviewer: guco, v-shaywood |
| 6 | +ms.custom: sap:Actions\AI actions |
| 7 | + |
| 8 | +#customer intent: As a developer, I want to resolve FailedToTakeScreenshot errors that might occur during computer use actions. These errors are preventing me from using computer use actions with my Copilot agents. |
| 9 | +--- |
| 10 | + |
| 11 | +# "FailedToTakeScreenshot" error during computer use action |
| 12 | + |
| 13 | +This article provides troubleshooting guidance for "FailedToTakeScreenshot" errors that might occur during [computer use actions](/microsoft-copilot-studio/computer-use) for Microsoft Copilot Studio agents. The computer use model requires screenshots to interact with the desktop. If the screenshot process fails, the computer use action ends. |
| 14 | + |
| 15 | +## Symptoms |
| 16 | + |
| 17 | +During a computer use action, a "FailedToTakeScreenshot" error code is returned to the [agent transcript](/microsoft-copilot-studio/analytics-transcripts-studio#download-agent-session-transcripts). When the screenshot process fails, the computer use action ends. |
| 18 | + |
| 19 | +## Cause 1: UAC prompt is displayed |
| 20 | + |
| 21 | +If Windows displays a [User Account Control](/windows/security/application-security/application-control/user-account-control/) (UAC) prompt, the prompt blocks the desktop, and the system or application can't capture a screen image. |
| 22 | + |
| 23 | +### Solution |
| 24 | + |
| 25 | +- Make sure that a UAC prompt isn't displayed when you open a new Remote Desktop session to another computer. |
| 26 | +- Verify that the [UAC level](/windows/security/application-security/application-control/user-account-control/architecture#system) isn't set to **Always notify**. That setting can cause UAC prompts to be displayed during session startup. |
| 27 | + |
| 28 | +## Cause 2: Windows OOBE experience is displayed |
| 29 | + |
| 30 | +The first time that a user signs in to the remote computer, Windows starts the [Out Of Box Experience](/windows-hardware/customize/desktop/customize-oobe-in-windows-11) (OOBE). At startup, the OOBE typically displays the message, "Getting things ready." If the OOBE image is displayed during the computer use action, the screen capture action fails. |
| 31 | + |
| 32 | +### Solution |
| 33 | + |
| 34 | +The OOBE is displayed only the first time that a new user signs in to the remote computer. Make sure that you manually sign in the user at least one time before they use a computer use action. |
| 35 | + |
| 36 | +## Cause 3: Remote Desktop session isn't visible |
| 37 | + |
| 38 | +A screen capture fails if the Remote Desktop session isn't visible. This issue might occur in the following situations: |
| 39 | + |
| 40 | +- If you use an existing Remote Desktop session in a web browser (for example, when you connect to a Power Automate-hosted computer), screen capturing fails if the Remote Desktop tab isn't focused. |
| 41 | +- If you use a Remote Desktop session in [Windows App](/windows-app/overview), screen capturing fails if the application window is minimized. |
| 42 | + |
| 43 | +### Solution |
| 44 | + |
| 45 | +Before you start a computer use action, make sure that the Remote Desktop session is focused and visible on the screen. |
| 46 | + |
| 47 | +## Related content |
| 48 | + |
| 49 | +- [Hosted machines](/power-automate/desktop-flows/hosted-machines) |
| 50 | +- [Automate web and desktop apps with computer use](/microsoft-copilot-studio/computer-use) |
0 commit comments