PR feedback

Author: haywoodsloan

support/power-platform/power-automate/desktop-flows/browser-automation/failed-to-assume-control-of-edge-chrome-firefox-error.md

@@ -14,9 +14,7 @@ _Original KB number:_   5001691
 
 ## Symptoms
 
-### Scenario 1
-
-When you run a desktop flow that has a [Launch new Microsoft Edge](/power-automate/desktop-flows/actions-reference/webautomation#launch-new-microsoft-edge), [Launch new Chrome](/power-automate/desktop-flows/actions-reference/webautomation#launchchromebase), or [Launch new Firefox](/power-automate/desktop-flows/actions-reference/webautomation#launchfirefoxbase) action in Microsoft Power Automate, the attempt fails. Additionally and the program returns one of the following error messages:
+When you run a desktop flow that has a [Launch new Microsoft Edge](/power-automate/desktop-flows/actions-reference/webautomation#launch-new-microsoft-edge), [Launch new Chrome](/power-automate/desktop-flows/actions-reference/webautomation#launchchromebase), or [Launch new Firefox](/power-automate/desktop-flows/actions-reference/webautomation#launchfirefoxbase) action in Microsoft Power Automate, the attempt fails. Additionally the program returns one of the following error messages:
 
 - > Failed to assume control of Microsoft Edge (Internal error or communication failure).
 - > Failed to assume control of Chrome (Internal error or communication failure).
@@ -25,10 +23,6 @@ When you run a desktop flow that has a [Launch new Microsoft Edge](/power-automa
 > [!IMPORTANT]
 > To resolve the error, run the **Troubleshoot UI/Web automation issues** diagnostic by using the [Power Automate for desktop troubleshooter](/power-automate/desktop-flows/troubleshooter). When the diagnostic runs, it generates a report that identifies issues. Resolve these issues by pressing the **Fix** button that appears after the diagnostics check finishes. If the troubleshooter doesn't resolve the error, refer to the potential causes and solutions that are provided in this article.
 
-### Scenario 2
-
-The error occurs when you run a Launch Browser action, and the browser is started by using a different system user than the one that was used to run Power Automate for desktop. For the recommended workaround, see [Cause 3](#cause-3-you-start-the-browser-by-using-a-different-system-user-than-the-one-you-use-to-run-power-automate-for-desktop-version-238-or-higher) in this article.
-
 ## Cause 1: Web extension isn't installed correctly or enabled
 
 The Microsoft Edge, Google Chrome, or Firefox web extension isn't installed correctly or enabled.
@@ -56,15 +50,11 @@ The Microsoft Edge, Google Chrome, or Firefox web extension isn't installed corr
 
 ## Cause 2: Launch Browser action takes longer than the default timeout
 
-Starting the browser takes longer than the Launch Browser action's default timeout (30 seconds). The automation process tries to assume control of the browser before it starts it. This attempt causes the Launch Browser action fails.
-
-### Additional symptoms
-
-Running a desktop flow by using one of the respective actions might fail and return one of the error messages that's listed in "Scenario 1." This behavior is inconsistent.
+Starting the browser takes longer than the Launch Browser action's default timeout. The automation process tries to assume control of the browser before it starts, causing the Launch Browser action to fail. This behavior might be inconsistent, where some executions fail while others are successful.
 
 ### Solution 1: Increase timeouts
 
-In the **Launch new Edge**, **Launch new Chrome**, or **Launch new Firefox** action, increase the values of the **Timeout on webpage load** and **Timeout** parameters that are located in the **Advanced** section. For example, set these values to **120** seconds.
+In the [Launch new Edge](/power-automate/desktop-flows/actions-reference/webautomation#launch-new-microsoft-edge), [Launch new Chrome](/power-automate/desktop-flows/actions-reference/webautomation#launchchromebase), or [Launch new Firefox](/power-automate/desktop-flows/actions-reference/webautomation#launchfirefoxbase) action, increase the values of the **Timeout on webpage load** and **Timeout** parameters that are located in the **Advanced** section. For example, set these values to **120** seconds.
 
 If this adjustment doesn't resolve the issue, try the steps in [Solution 2](#solution-2-use-a-go-to-web-page-action) or [Solution 3](#solution-3-use-a-wait-action).
 
@@ -73,10 +63,10 @@ If this adjustment doesn't resolve the issue, try the steps in [Solution 2](#sol
 Use the **Launch Browser** action to start the process of the corresponding browser. Then, use a combination of an additional **Launch Browser** action that has the mode set to **Attach to running instance** and a [Go to web page](/power-automate/desktop-flows/actions-reference/webautomation#gotowebpagebase) action:
 
 1. Insert a new **Launch Browser** action as:
-    - **Launch new Microsoft Edge**
-    - **Launch new Chrome**
-    - **Launch new Firefox**
-    - **Launch new Internet Explorer**
+    - [Launch new Microsoft Edge](/power-automate/desktop-flows/actions-reference/webautomation#launch-new-microsoft-edge)
+    - [Launch new Chrome](/power-automate/desktop-flows/actions-reference/webautomation#launchchromebase)
+    - [Launch new Firefox](/power-automate/desktop-flows/actions-reference/webautomation#launchfirefoxbase)
+    - [Launch new Internet Explorer](/power-automate/desktop-flows/actions-reference/webautomation#launchinternetexplorerbase)
 
 1. Set up the parameters of the action:
     - Launch mode: **Launch new Instance**
@@ -123,10 +113,10 @@ Use the **Launch Browser** action to start the process of the corresponding brow
 Use the **Launch Browser** action to start the process of the corresponding browser. Then, use a combination of an additional **Launch Browser** action that has the mode set to **Attach to running instance** and a **Wait** action that's set to a duration of 90 seconds.
 
 1. Insert a new **Launch Browser** action as:
-    - **Launch new Microsoft Edge**
-    - **Launch new Chrome**
-    - **Launch new Firefox**
-    - **Launch new Internet Explorer**
+    - [Launch new Microsoft Edge](/power-automate/desktop-flows/actions-reference/webautomation#launch-new-microsoft-edge)
+    - [Launch new Chrome](/power-automate/desktop-flows/actions-reference/webautomation#launchchromebase)
+    - [Launch new Firefox](/power-automate/desktop-flows/actions-reference/webautomation#launchfirefoxbase)
+    - [Launch new Internet Explorer](/power-automate/desktop-flows/actions-reference/webautomation#launchinternetexplorerbase)
 
 1. Set up the parameters of the action:
     - Launch mode: **Launch new Instance**
@@ -164,18 +154,14 @@ To resolve the issue, make sure you start the browser by using the same system u
 
 ## Cause 4: Browser doesn't start because of profile conflicts
 
-The browser doesn't start, or it starts one time but doesn't start in subsequent attempts.
-
-### Additional symptoms
-
-Running a desktop flow by using a **Launch Browser** action fails, and the browser either doesn't appear or terminates immediately after launch.
-
-### Solution
+The browser doesn't start, or it starts one time but doesn't start in subsequent attempts. Running a desktop flow by using a **Launch Browser** action fails, and the browser either doesn't appear or terminates immediately after launch.
 
 Another session might be using the same browser profile. When you start a Chromium-based browser (such as Microsoft Edge or Google Chrome), the browser checks whether another instance is already using the same profile on disk. If another instance is using the same profile, the browser terminates immediately.
 
 This issue can occur if the same user signs in to multiple sessions on the same machine, and each session tries to open the browser. Only one session can successfully start the browser. The other attempts terminate on startup.
 
+### Solution
+
 To work around this issue, manually launch the browser from Power Automate for desktop by using a different profile on disk. Use the following example:
 
 ```powershell