minor updates

Author: lucciz01

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

@@ -4,7 +4,7 @@ description: Solves an error that occurs when you run the Run PowerShell script
 ms.author: iomavrid
 author: yiannismavridis
 ms.custom: sap:Desktop flows
-ms.date: 04/15/2025
+ms.date: 04/16/2025
 ---
 # "Failed to run PowerShell script" error when running the Run PowerShell script action
 
@@ -48,14 +48,14 @@ To resolve this issue, follow these steps to update the **Path** environment var
 
 1. Under the **System variables** section, locate and select the **Path** variable, then select **Edit**.
 
-1. Add the directory path of `powershell.exe` to the list of paths. In most cases, the missing path is:
+1. Add the directory path of `powershell.exe` to the list of paths.
 
-   **C:\WINDOWS\System32\WindowsPowerShell\v1.0\\**
+   In most cases, the missing path is: **C:\WINDOWS\System32\WindowsPowerShell\v1.0\\**
 
-1. To confirm the correct path, open a PowerShell terminal and run the following command:
+   To confirm the correct path, open a PowerShell terminal and run the following command:
 
    `$PsHome`
 
-   Use the displayed path as the value to add to the **Path** variable if it differs.
+   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/take-screenshot-action-fails-in-unattended-mode.md

@@ -4,7 +4,7 @@ description: Resolves an error that occurs in the action 'Take screenshot', when
 ms.author: iomavrid
 author: yiannismavridis
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
-ms.date: 04/15/2025
+ms.date: 04/16/2025
 ---
 # Unattended desktop flow run fails with the "Failed to take screenshot" error
 
@@ -30,9 +30,15 @@ The issue occurs due to a specific security policy that impacts how a User Accou
 
 ## Resolution 1: Locate and allow binaries except for non-Windows ones to run without elevation prompt
 
-Configure the [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) security policy setting.
+To solve this issue,
 
-:::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":::
+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 below