Merge pull request #8648 from MicrosoftDocs/iomavrid-screenshot-and-powershell-issues-docs-update

AB#5351 & AB#5352: Iomavrid screenshot and powershell issues docs update

Author: lucciz01

support/power-platform/power-automate/desktop-flows/failed-to-run-powershell-script-error.md

@@ -0,0 +1,59 @@
+---
+title: Failed to Run PowerShell Script Error
+description: Solves an error that occurs when you run the Run PowerShell script action in a desktop flow in Microsoft Power Automate for desktop.
+ms.author: iomavrid
+author: yiannismavridis
+ms.custom: sap:Desktop flows
+ms.date: 04/24/2025
+---
+# "Failed to run PowerShell script" error when running the Run PowerShell script action
+
+This article provides a resolution for an error that occurs when running the [Run PowerShell script](/power-automate/desktop-flows/actions-reference/scripting#runpowershellscript) action in Microsoft Power Automate for desktop.
+
+## Symptoms
+
+During the execution of a desktop flow in Power Automate for desktop, an error occurs when running the **Run PowerShell script** action. This issue might also occur after a recent Windows update.
+
+The error message appears as follows:
+
+```output
+Microsoft.Flow.RPA.Desktop.Modules.SDK.ActionException: Failed to run PowerShell script. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
+   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
+   at Microsoft.Flow.RPA.Desktop.Modules.System.Actions.SystemActions.RunPowershellScript(Variant powershellCode, Variant& scriptStandardOutput, Variant& scriptErrorOutput)
+   --- End of inner exception stack trace ---
+   at Microsoft.Flow.RPA.Desktop.Modules.System.Actions.RunPowershellScript.Execute(ActionContext context)
+   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)
+```
+
+## Cause
+
+The **Run PowerShell script** action internally starts an instance of `powershell.exe` and provides the script specified in the action's input as an argument for the process. If the system fails to find `powershell.exe`, you might receive the error message.
+
+The most likely cause of this issue is that the **Path** environment variable doesn't include the directory containing the `powershell.exe` executable. To confirm this is the root cause, follow these steps:
+
+1. Open a Command Prompt (CMD) window.
+1. Run `powershell.exe` by typing the command and pressing **Enter**.
+
+If the following message occurs, then the issue lies in the missing path to `powershell.exe` in the **Path** environment variable.
+
+> 'powershell.exe' is not recognized as an internal or external command, operable program or batch file.
+
+## Resolution
+
+To resolve this issue, follow these steps to update the **Path** environment variable to include the directory of the `powershell.exe` executable:
+
+1. Open the Start menu, search for **Environment Variables**, and then select **Edit the system environment variables**.
+
+1. In the **System Properties** window, select **Environment Variables**.
+
+1. Under the **System variables** section, locate and select the **Path** variable, and then select **Edit**.
+
+1. Add the directory path of `powershell.exe` to the list of paths.
+
+   In most cases, the missing path is **C:\WINDOWS\System32\WindowsPowerShell\v1.0\\**.
+
+   To confirm the correct path, open a PowerShell terminal and run the `$PsHome` command.
+
+   Use the displayed path as the value to add to the **Path** variable.
+
+1. Select **OK** to save changes and close all dialogs.

support/power-platform/power-automate/desktop-flows/media/take-screenshot-action-fails-in-unattended-mode/local-security-policy.png

@@ -0,0 +1,63 @@
+---
+title: Take Screenshot Action Fails in Unattended Mode
+description: Resolves an error that occurs in the Take screenshot action when you run an unattended desktop flow in Microsoft Power Automate for desktop.
+ms.author: iomavrid
+author: yiannismavridis
+ms.custom: sap:Desktop flows\Unattended flow runtime errors
+ms.date: 04/24/2025
+---
+# Unattended desktop flow run fails with the "Failed to take screenshot" error
+
+This article provides a resolution for an error that occurs in the [Take screenshot](/power-automate/desktop-flows/actions-reference/workstation#takescreenshotbase) action when running an unattended desktop flow in Microsoft Power Automate for desktop.
+
+## Symptoms
+
+The **Take screenshot** action fails with the following error message:
+
+```output
+Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Failed to take screenshot. ---> System.ComponentModel.Win32Exception: The handle is invalid
+   at System.Drawing.Graphics.CopyFromScreen(Int32 sourceX, Int32 sourceY, Int32 destinationX, Int32 destinationY, Size blockRegionSize, CopyPixelOperation copyPixelOperation)
+   at System.Drawing.Graphics.CopyFromScreen(Int32 sourceX, Int32 sourceY, Int32 destinationX, Int32 destinationY, Size blockRegionSize)
+   at Microsoft.Flow.RPA.Desktop.Modules.System.Actions.SystemActions.TakeScreenShot(Variant fileName, Variant screenToCapture, Int32 screenCaptureOption, Boolean copyToClipboard, Int32 fileFormat)
+   --- End of inner exception stack trace ---
+   at Microsoft.Flow.RPA.Desktop.Modules.System.Actions.TakeScreenshotBase.Execute(ActionContext context)
+   at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)
+```
+
+## Cause
+
+The issue occurs due to a specific security policy that impacts how a User Account Control (UAC) window (for administrative privileges) is prompted. This policy prevents the flow from accessing the screen and capturing the screenshot.
+
+## Resolution 1: Locate and allow binaries except for non-Windows ones to run without elevation prompt
+
+To solve this issue:
+
+1. In Local Group Policy Editor, go to **Computer Configuration** > **Windows Settings** > **Security Settings** > **Local Policies** > **Security Options**.
+1. Locate the **User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode** security policy setting.
+1. Set the value to **Prompt for consent for non-Windows binaries**.
+
+   :::image type="content" source="media/take-screenshot-action-fails-in-unattended-mode/local-security-policy.png" alt-text="Screenshot of the User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode setting in the Local Security Policy window." lightbox="media/take-screenshot-action-fails-in-unattended-mode/local-security-policy.png":::
+
+For more information about the best practices, location, values, policy management and security considerations for the security policy setting, see [User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-administrators-in-admin-approval-mode).
+
+## Resolution 2: Change the registry key
+
+Modify the registry key to adjust the UAC behavior:
+
+- Hive: **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System**
+- Registry key name: [ConsentPromptBehaviorAdmin](/windows/security/application-security/application-control/user-account-control/settings-and-configuration?tabs=reg#user-account-control-configuration)
+- Type: DWORD
+- Value: **5**
+
+Options for the **ConsentPromptBehaviorAdmin** key:
+
+- **0** = Elevate without prompting
+- **1** = Prompt for credentials on the secure desktop
+- **2** = Prompt for consent on the secure desktop
+- **3** = Prompt for credentials
+- **4** = Prompt for consent
+- **5** (Default) = Prompt for consent for non-Windows binaries. Set the registry key to this value.
+
+## More information
+
+[User Account Control settings and configuration](/windows/security/application-security/application-control/user-account-control/settings-and-configuration)

support/power-platform/power-automate/desktop-flows/take-screenshot-action-fails-in-unattended-mode.md

@@ -160,6 +160,10 @@
       href: desktop-flows/troubleshoot-excel-errors.md
     - name: Errors when running attended or unattended desktop flows
       href: desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md
+    - name: '"Failed to run PowerShell script" error'
+      href: desktop-flows/failed-to-run-powershell-script-error.md
+    - name: '"Failed to take screenshot" error in unattended desktop flow run'
+      href: desktop-flows/take-screenshot-action-fails-in-unattended-mode.md
     - name: Failed connection between Power Automate components
       href: desktop-flows/failed-connection-between-power-automate-components.md
     - name: Failed license check on a desktop flow run