Merge pull request #10287 from MicrosoftDocs/main

Auto Publish – main to live - 2025-12-03 18:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -45,11 +45,6 @@
       "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios",
       "redirect_document_id": false
     },
-    {
-      "source_path": "support/windows-client/windows-tss/gather-information-using-tss-wufb-reports.md",
-      "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios",
-      "redirect_document_id": false
-    },
     {
       "source_path": "support/windows-client/windows-tss/gather-information-using-tss-group-policy.md",
       "redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios",

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

@@ -1,13 +1,13 @@
 ---
 title: Troubleshoot issues in Power Automate browser extensions
 description: Provides a resolution for the Failed to assume control of browser (Internal error or communication failure) error or Get Extension message.
-ms.reviewer: nimoutzo, gtrantzas, jspantouris 
-ms.date: 08/08/2025
+ms.reviewer: nimoutzo, gtrantzas, jspantouris, v-shaywood 
+ms.date: 12/01/2025
 ms.custom: sap:Desktop flows\UI or browser automation
 ---
 # Troubleshoot issues in Power Automate browser extensions
 
-This article provides tips to troubleshoot and resolve issues that are related to Power Automate browser extensions when you use web automation in desktop flows.
+This article provides tips to troubleshoot and resolve issues related to Power Automate browser extensions when you use web automation in desktop flows.
 
 ## Symptoms
 
@@ -53,7 +53,7 @@ Follow these steps:
 
 1. If PAD.BrowserNativeMessageHost.exe isn't running, follow these steps:
 
-   1. Check whether the Power Automate web extension is installed and enabled. If it isn’t installed, see the [Prerequisites](#prerequisites) section.
+   1. Check whether the Power Automate web extension is installed and enabled. If it isn't installed, see the [Prerequisites](#prerequisites) section.
 
    1. If the extension is installed, run the **Troubleshoot UI/Web automation issues** diagnostic in [Power Automate for desktop troubleshooter](/power-automate/desktop-flows/troubleshooter).
 
@@ -77,7 +77,7 @@ Follow these steps:
 
    The error message, "Access to the native messaging host was disabled by the system administrator," indicates that the **NativeMessagingBlocklist** policy is enabled for the Power Automate for desktop native messaging host or all native messaging hosts.
 
-### Check for policies that are blocking the message host
+### Check for policies that block the message host
 
 Follow these steps:
 
@@ -96,15 +96,15 @@ Follow these steps:
 
        #### [Microsoft Edge](#tab/microsoft-edge)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist
        Name = {number}
        Data = com.robin.messagehost
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist
@@ -114,15 +114,15 @@ Follow these steps:
 
        #### [Google Chrome](#tab/google-chrome)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist
        Name = {number}
        Data = com.robin.messagehost
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist
@@ -132,15 +132,15 @@ Follow these steps:
 
        #### [Mozilla Firefox](#tab/mozilla-firefox)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\NativeMessagingAllowlist
        Name = {number}
        Data = com.robin.messagehost
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Mozilla\NativeMessagingAllowlist
@@ -154,15 +154,15 @@ Follow these steps:
 
        #### [Microsoft Edge](#tab/microsoft-edge)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist
        Name = {number}
        Data = com.microsoft.pad.messagehost
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist
@@ -172,15 +172,15 @@ Follow these steps:
 
        #### [Google Chrome](#tab/google-chrome)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist
        Name = {number}
        Data = com.microsoft.pad.messagehost
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\NativeMessagingAllowlist
@@ -190,14 +190,14 @@ Follow these steps:
 
        #### [Mozilla Firefox](#tab/mozilla-firefox)
 
-       For adding policy in Local Machine level:
+       To add a policy at the local machine level:
 
        ```console
        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Mozilla\NativeMessagingAllowlist
        Name = {number}
        ```
 
-       For adding policy in Current User level:
+       To add a policy at the current user level:
 
        ```console
        Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Mozilla\NativeMessagingAllowlist
@@ -210,7 +210,7 @@ Follow these steps:
     1. Check the [NativeMessagingUserLevelHosts](/deployedge/microsoft-edge-browser-policies/nativemessaginguserlevelhosts) policy. If **NativeMessagingUserLevelHosts** is disabled, enable it or make sure that `com.robin.messagehost` for the legacy browser extension and `com.microsoft.pad.messagehost` for the default browser extension are added to your **NativeMessagingAllowlist** policy in HKLM (Local Machine level).
 
         > [!NOTE]
-        > **NativeMessagingUserLevelHosts** must be enabled when using the [Microsoft Store (MSIX) version of Power Automate for desktop](/power-automate/desktop-flows/install#install-power-automate-from-microsoft-store).
+        > You must enable **NativeMessagingUserLevelHosts** when using the [Microsoft Store (MSIX) version of Power Automate for desktop](/power-automate/desktop-flows/install#install-power-automate-from-microsoft-store).
 
 ### Check whether the message host points to the correct location
 
@@ -276,7 +276,7 @@ To check if more than one profile exists, select the profile icon in the browser
 If more than one browser profile exists:
 
 1. Uninstall the Power Automate web extension from each existing browser profile.
-1. Close the browser and [install the extension](/power-automate/desktop-flows/install-browser-extensions) only in the browser profile that will be used by the automation.
+1. Close the browser and [install the extension](/power-automate/desktop-flows/install-browser-extensions) only in the browser profile that you use for the automation.
 
 ### Check for errors in Windows Event Viewer
 
@@ -290,4 +290,14 @@ Follow these steps:
 
 Try disabling all other web extensions except the Power Automate extension to see whether the issue persists.
 
+### Disable browser background settings
+
+Some browser settings can interfere with the Power Automate extension. To resolve this issue, disable the following settings in your browser:
+
+1. Open Microsoft Edge or Google Chrome.
+1. Go to **Settings** > **System and performance**.
+1. Turn off the following settings:
+   1. **Continue running background extensions and apps when Microsoft Edge is closed** (or **Continue running background apps when Google Chrome is closed**).
+   1. **Startup boost** (Microsoft Edge only).
+
 [!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

support/sql/database-engine/startup-shutdown/toc.yml

@@ -3,7 +3,7 @@ items:
   href: event-id-7000-access-denied.md
 - name: Error 17113 when you start SQL Server service
   href: error-17113-start-service.md
-- name: Error 1068 when starting SQL Server
+- name: Error 1068 when starting SQL Server and SQL Agent
   href: agent-service-fails-start-stand-alone-server.md
 - name: Error 1069 when starting SQL Server
   href: error-1069-service-cannot-start.md

support/windows-client/toc.yml

@@ -1461,6 +1461,8 @@ items:
       href: ./windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios.md
     - name: Collect data to analyze and troubleshoot Group Policy scenarios
       href: ./windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios.md
+    - name: Collect data to analyze and troubleshoot Hyper-V related issues
+      href: ./windows-tss/collect-data-analyze-troubleshoot-hyperv-scenarios.md
     - name: Collect data to analyze and troubleshoot licensing and activation scenarios
       href: ./windows-tss/collect-data-analyze-troubleshoot-licensing-activation-scenarios.md
     - name: Collect data to analyze and troubleshoot Windows networking scenarios
@@ -1469,15 +1471,15 @@ items:
       href: ./windows-tss/collect-data-analyze-troubleshoot-performance-scenarios.md
     - name: Collect data to analyze and troubleshoot Remote Desktop Services scenarios
       href: ./windows-tss/collect-data-analyze-troubleshoot-remote-desktop-services-scenarios.md
-    - name: Collect data to analyze and troubleshoot shell experience scenarios
-      href: ./windows-tss/collect-data-analyze-troubleshoot-shell-experiences-scenarios.md
     - name: Collect data to analyze and troubleshoot Windows servicing, updates, and Features on Demand scenarios
       href: ./windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md
-    - name: Collect data to analyze and troubleshoot system management components scenarios
-      href: ./windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
-    - name: Collect data to analyze and troubleshoot Hyper-V related issues
-      href: ./windows-tss/collect-data-analyze-troubleshoot-hyperv-scenarios.md
+    - name: Collect data to analyze and troubleshoot shell experience scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-shell-experiences-scenarios.md
     - name: Collect data to analyze and troubleshoot SQL cluster (AG/FCI) related issues
       href: ./windows-tss/collect-data-analyze-troubleshoot-sql-cluster-ag-fci-scenarios.md
+    - name: Collect data to analyze and troubleshoot system management components scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
+    - name: Collect Data to Analyze and Troubleshoot Windows Update for Business Reports Scenarios
+      href: ./windows-tss/gather-information-using-tss-wufb-reports.md
     - name: Use the xray feature of TSS
       href: ./windows-tss/use-the-xray-feature-of-tss-to-identify-known-issues.md

support/windows-client/windows-tss/gather-information-using-tss-wufb-reports.md

@@ -0,0 +1,46 @@
+---
+title: Collect Data to Analyze and Troubleshoot Windows Update for Business Reports Scenarios
+description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Windows Update for Business reports-related issues.
+ms.date: 12/1/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, warrenw, v-lianna
+ms.custom: sap:Support Tools\TSS DnD, csstroubleshoot
+appliesto:
+  - ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+  - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
+---
+# Collect data to analyze and troubleshoot Windows Update for Business Reports scenarios
+
+This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Windows Update for Business reports-related issues.
+
+Before contacting Microsoft support, you can gather information about your issue.
+
+## Prerequisites
+
+Refer to [Introduction to TroubleShootingScript toolset (TSS)](/windows-client/windows-tss/introduction-to-troubleshootingscript-toolset-tss#prerequisites) for prerequisites for the toolset to run properly.
+
+## Gather key information before contacting Microsoft support
+
+1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
+2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
+    > [!NOTE]
+    > Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
+3. Run the following cmdlets:
+
+    ```powershell
+    Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
+    ```
+
+    ```powershell
+    .\TSS.ps1 -Collectlog DND_WUfBReport
+    ```
+
+4. Enter *A* for "Yes to All" for the execution policy change.
+
+> [!NOTE]
+>
+> - The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
+> - If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running `-Collectlog DND_WUfBReport`.
+

support/windows-server/toc.yml

@@ -3311,13 +3311,15 @@ items:
       href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios.md?context=/troubleshoot/windows-server/context/context
     - name: Collect data to analyze and troubleshoot Group Policy scenarios
       href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios.md?context=/troubleshoot/windows-server/context/context
-    - name: Collect data to analyze and troubleshoot Windows servicing, updates, and Features on Demand scenarios
-      href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md?context=/troubleshoot/windows-server/context/context
-    - name: Collect data to analyze and troubleshoot system management components scenarios
-      href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md?context=/troubleshoot/windows-server/context/context
     - name: Collect data to analyze and troubleshoot Hyper-V related issues
       href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-hyperv-scenarios.md?context=/troubleshoot/windows-server/context/context
+    - name: Collect data to analyze and troubleshoot Windows servicing, updates, and Features on Demand scenarios
+      href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md?context=/troubleshoot/windows-server/context/context
     - name: Collect data to analyze and troubleshoot SQL cluster (AG/FCI) related issues
       href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-sql-cluster-ag-fci-scenarios.md?context=/troubleshoot/windows-server/context/context
+    - name: Collect data to analyze and troubleshoot system management components scenarios
+      href: ../windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md?context=/troubleshoot/windows-server/context/context
+    - name: Collect Data to Analyze and Troubleshoot Windows Update for Business Reports Scenarios
+      href: ../windows-client/windows-tss/gather-information-using-tss-wufb-reports.md?context=/troubleshoot/windows-server/context/context
     - name: Use the xray feature of TSS
       href: ../windows-client/windows-tss/use-the-xray-feature-of-tss-to-identify-known-issues.md?context=/troubleshoot/windows-server/context/context