Merge pull request #9263 from MicrosoftDocs/lucciz01-migrate-SMC-article--to-LMC

AB#6424: Update troubleshoot-session-creation-errrors.md

Author: lucciz01

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -2,7 +2,7 @@
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
 ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon
-ms.date: 05/29/2025
+ms.date: 07/11/2025
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -23,6 +23,7 @@ _Original KB number:_   4555406
 |AttendedUserSessionNotActive<br>AttendedUserNotLoggedIn|400|Attended|Check that you're logged in with the correct user and that the session is unlocked on the machine. For more information about the error codes, see [AttendedUserSessionNotActive](troubleshoot-desktop-flow-run-queue-errors.md#attendedusersessionnotactive) and [AttendedUserNotLoggedIn](troubleshoot-desktop-flow-run-queue-errors.md#attendedusernotloggedin).|
 |SessionCreationError|400|Unattended|We couldn't create the session on the machine for an unknown reason. To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationerror).|
 |SessionCreationErrorWithThirdPartyCredentialProvider|400|Unattended|To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationerrorwiththirdpartycredentialprovider).|
+|SessionCreationUserPromptedForCredentialsAfterConnection|400|Unattended|To solve this issue, see [Troubleshoot session creation error codes for an unattended desktop flow run](troubleshoot-session-creation-errrors.md#sessioncreationuserpromptedforcredentialsafterconnection).|
 |SessionCreationWinLogonFailure|400|Unattended|We can't create a Windows session to run your unattended desktop flow. You need to restart your machine.|
 |SessionExistsForTheUserWhenUnattended|400|Unattended|Check that you aren't logged in with the same user (regardless of the state of the session) on the machine. For more information about this error code, see [SessionExistsForTheUserWhenUnattended](troubleshoot-desktop-flow-run-queue-errors.md#sessionexistsfortheuserwhenunattended).|
 |UnattendedUserSessionDisconnected|400|Unattended|For more information about this error code, see [UnattendedUserSessionDisconnected](troubleshoot-desktop-flow-run-queue-errors.md#unattendedusersessiondisconnected).|

support/power-platform/power-automate/desktop-flows/troubleshoot-session-creation-errrors.md

@@ -3,30 +3,31 @@ title: Session creation error codes in unattended desktop flow runs
 description: Solves error codes related to session creation during unattended desktop flow runs in Power Automate.
 author: johndund 
 ms.author: johndund 
-ms.date: 04/29/2025
-ms.reviewer: madiazor, guco, fredg 
+ms.date: 07/11/2025
+ms.reviewer: madiazor, guco, fredg, alarnaud
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
-# Resolve session creation error codes for an unattended desktop flow run
+# Resolve session creation errors for an unattended desktop flow run
 
-This article provides background and potential solutions to the `SessionCreationError` and `SessionCreationErrorWithThirdPartyCredentialProvider` error codes that might occur during an unattended desktop flow run in Microsoft Power Automate.
+This article provides background and potential solutions for session creation errors that might occur during an unattended desktop flow run in Microsoft Power Automate.
 
 _Applies to:_   Power Automate
 
 ## Symptoms
 
-Your [unattended desktop flow run](/power-automate/desktop-flows/run-unattended-desktop-flows) might fail with the `SessionCreationError` or `SessionCreationErrorWithThirdPartyCredentialProvider` error code.
-
-## Cause
-
-When an unattended session is run, Power Automate attempts to create a remote desktop (RDP) session on the target machine. If this session creation fails, you might receive one of the following error codes:
+Your [unattended desktop flow run](/power-automate/desktop-flows/run-unattended-desktop-flows) might fail with one of the following error codes:
 
 - [SessionCreationErrorWithThirdPartyCredentialProvider](#sessioncreationerrorwiththirdpartycredentialprovider)
+- [SessionCreationUserPromptedForCredentialsAfterConnection](#sessioncreationuserpromptedforcredentialsafterconnection)
 - [SessionCreationError](#sessioncreationerror)
 
+## Cause
+
+When an unattended session is run, Power Automate attempts to create a Remote Desktop Protocol (RDP) connection on the target machine. If this session creation fails, you might receive one of the error codes.
+
 ## SessionCreationErrorWithThirdPartyCredentialProvider
 
-This error code occurs because third-party software interferes with Power Automate's ability to create a session on the machine. Power Automate doesn't support some third-party credential providers.
+This error code occurs because third-party software interferes with Power Automate's ability to create a session on the machine. Power Automate doesn't support some third-party credential providers, or might experience conflicts depending on their configuration.
 
 ### Resolution
 
@@ -44,6 +45,72 @@ Each subkey represents an installed credential provider. The following table lis
 | SIDCredentialProvider | 36ED98C6-02FF-47e8-B7FE-957A411CEA16 |
 | CGWinLogon | BDA6DA5B-7E7E-482C-9B3E-67AFF0C838C0 |
 
+## SessionCreationUserPromptedForCredentialsAfterConnection
+
+This error code occurs when the machine prompts for credentials after the RDP connection is established. Power Automate expects credentials to be handled during the connection setup, so this unexpected prompt might cause the flow to fail.
+
+### Resolution
+
+The resolution steps depend on the machine's setup. Follow the instructions to determine the setup and apply the appropriate solution:
+
+[!INCLUDE [Registry important alert](../../../includes/registry-important-alert.md)]
+
+1. Open **Command Prompt** and run `dsregcmd /status`.
+
+2. In the output under the **Device State** section, check the values for `AzureAdJoined` and `DomainJoined`.
+
+   **If `AzureAdJoined: YES` and `DomainJoined: NO`:**
+
+   1. Open **Registry Editor** by pressing Windows+<kbd>R</kbd>, typing `regedit`, and pressing <kbd>Enter</kbd>.
+
+   2. Navigate to the following path:
+
+      `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services`
+
+   3. Check if the `Terminal Services` key contains a `fPromptForPassword` subkey:
+
+      - If it exists and is set to **1**, contact your IT department to disable the "Always prompt for password upon connection" policy. After the policy is updated, force a policy refresh on the machine.
+      - If `fPromptForPassword` doesn't exist, navigate to:
+
+        `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`
+
+        Look for the `fPromptForPassword` DWORD. If it exists, set its value to **0**. If it doesn't exist, create it and set its value to **0**.
+
+   **For other machine configurations:**
+
+   1. Open **Registry Editor** by pressing Windows+<kbd>R</kbd>, typing `regedit`, and pressing <kbd>Enter</kbd>.
+
+   2. Navigate to the following path:
+
+      `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services`
+
+   3. Check if the `Terminal Services` key contains the following values:
+
+      - `fPromptForPassword` = **1**
+      - `SecurityLayer` = **0**
+      - `UserAuthentication` = **0**
+
+      If all three values exist, contact your IT department to update one of these values:
+
+      - Set `fPromptForPassword` to **0**, or
+      - Set `SecurityLayer` to **1** or **2**, or
+      - Set `UserAuthentication` to **1**.
+
+      If one or more values are missing:
+
+      - Choose one of the missing values based on your requirements.
+      - Navigate to:
+
+        `Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp`
+
+      - Update (or create if not present) the selected value:
+
+         - Set `fPromptForPassword` to **0**, or
+         - Set `SecurityLayer` to **1** or **2**, or
+         - Set `UserAuthentication` to **1**.
+
+3. Restart the machine after making registry changes.
+
 ## SessionCreationError
 
 This error code occurs when a session creation fails for an unknown reason.