Skip to content

Commit 39f6e89

Browse files
committed
Initial edits
1 parent 1346baf commit 39f6e89

1 file changed

Lines changed: 16 additions & 16 deletions

File tree

support/power-platform/power-automate/desktop-flows/browser-automation/web-extensions-policies.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -259,27 +259,27 @@ Follow these steps:
259259

260260
- MSIX Windows 10: `AppData\Local\Packages\Microsoft.PowerAutomateDesktop_8wekyb3d8bbwe\TempState\webextensions\PAD.ChromiumManifest.json`
261261

262-
263262
### Check whether cmd.exe execution is disabled
264263

265-
Power Automate Desktop (PAD) relies on the browser extension to communicate with the native messaging host. If execution of cmd.exe is blocked by Group Policy, Intune, or registry restrictions, the browser cannot launch the native messaging host, which may cause the PAD browser extension to fail.
264+
Power Automate for desktop relies on the browser extension to communicate with the native messaging host. If `cmd.exe` execution is blocked by Group Policy, Intune, or registry restrictions, the browser can't launch the native messaging host, and the Power Automate browser extension might fail.
265+
266+
Restoring access to `cmd.exe` ensures that the browser can correctly launch the native messaging host that's required by the Power Automate browser extension.To re-enable `cmd.exe` by using one of the following methods.
267+
268+
#### Re-enable cmd.exe by using Group Policy
266269

267-
How to resolve the issue:
268-
1. Re-enable command prompt via Group Policy
269-
- Press Win + R, type gpedit.msc, and press Enter.
270-
- Navigate to: User Configuration → Administrative Templates → System
271-
- Open Prevent access to the command prompt.
272-
- Set the policy to Disabled or Not configured.
273-
- Select OK to save the changes.
274-
2. Re-enable cmd.exe via Registry Editor
275-
- Open regedit.
276-
- Navigate to: HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System
277-
- Find the DisableCMD value and:
278-
- Set it to 0, or
279-
- Delete the value entirely.
270+
1. Press <kbd>Win</kbd>+<kbd>R</kbd>, enter `gpedit.msc`, and then press <kbd>Enter</kbd>.
271+
1. Go to **User Configuration** > **Administrative Templates** > **System**.
272+
1. Open **Prevent access to the command prompt**.
273+
1. Set the policy to **Disabled** or **Not configured**.
274+
1. Select **OK** to save the changes.
280275

281-
Restoring access to cmd.exe ensures that the browser can correctly launch the native messaging host required by the PAD browser extension.
276+
#### Re-enable cmd.exe by using Registry Editor
282277

278+
1. Open **Start**, search for and select **Registry Editor**.
279+
1. Go to `HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System`.
280+
1. Find the `DisableCMD` value, and then do one of the following:
281+
- Set the value to `0`.
282+
- Delete the value.
283283

284284
### Check for the ComSpec variable
285285

0 commit comments

Comments
 (0)