Merge pull request #9328 from MicrosoftDocs/main

Auto push to live 2025-07-14 10:02:11

Author: Simonx Xu

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-installation.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure File Sync agent installation and server registration
 description: Troubleshoot common issues with installing the Azure File Sync agent and registering Windows Server with the Storage Sync Service. 
 author: khdownie
 ms.service: azure-file-storage
-ms.date: 07/11/2025
+ms.date: 07/14/2025
 ms.author: kendownie
 ms.custom: sap:File Sync
 ---
@@ -124,26 +124,26 @@ To learn about installing the Azure File Sync Agent for Windows, see [Install an
 1. Navigate to your **Arc Server** in the Azure portal.
 1. Go to the **Extensions** blade for the server.
 1. Locate `AzureFileSyncAgentExtension` and select **View Details** under the **Status** column.
-1. Review the **Error Message** field for detailed information on why the extension deployment failed.
+1. Review the **Error Message** field for detailed information about the cause of the extension deployment failure.
 
 > [!IMPORTANT]
-> The failed extension must be uninstalled and then reinstalled **after** performing the required remediation steps. Save the error message details for troubleshooting or when contacting Azure File Sync support. Uninstalling the extension will remove these details.
+> The failed extension must be uninstalled and then reinstalled after performing the required remediation steps. Save error message details for troubleshooting or contacting Azure File Sync support, as uninstalling the failed extension will delete these details.
 
 #### Error code reference and remediation
 
-| **Error Message** | **Error Code** | **Remediation Steps** |
+| **Error Message** | **Error Code** | **Remediation steps** |
 |-------------------|----------------|------------------------|
-| Cannot install Azure File Sync agent because .NET Framework 4.7.2 or later is required. Install the latest .NET Framework and try again | 206 | Install .NET Framework 4.7.2 or higher. Reboot the machine afterward. |
+| Cannot install Azure File Sync agent because .NET Framework 4.7.2 or later is required. Install the latest .NET Framework and try again | 206 | Install .NET Framework 4.7.2 or later, then restart your computer. |
 | Azure File Sync agent is already installed. No further action needed. | 0 | No action required. The extension is installed, but no customization is applied. |
 | The Azure File Sync agent is only supported on RTM (Release to Manufacturing) versions of supported operating systems. | 51 | Azure File Sync agent and extension are supported only on RTM versions of Windows Server 2016, 2019, 2022, and 2025. |
-| Proxy settings error. `UseCustomProxy` is enabled but ProxyAddress is missing or invalid. ProxyAddress must be specified without port and length must be less than 255 characters. | 201 | Ensure `ProxyAddress` is specified. Must be under 255 characters. |
-| Proxy settings error. `UseCustomProxy` is enabled but ProxyPort is missing or invalid. Proxy port must be a number between 1 and 65535 | 202 | Provide a valid `ProxyPort` (numeric value between 1 and 65535) when `UseCustomProxy` is enabled. |
+| Proxy settings error. `UseCustomProxy` is enabled but ProxyAddress is missing or invalid. ProxyAddress must be specified without port and length must be less than 255 characters. | 201 | Ensure that the `ProxyAddress` is specified and doesn't exceed 255 characters in length. |
+| Proxy settings error. `UseCustomProxy` is enabled but ProxyPort is missing or invalid. Proxy port must be a number between 1 and 65535 | 202 | Provide a valid `ProxyPort` (a numeric value between 1 and 65535) when `UseCustomProxy` is enabled. |
 | Proxy settings error. `ProxyAuthRequired` is enabled but ProxyUsername is missing or invalid. `ProxyUsername` length must be between 3 and 255 characters | 203 | Ensure `ProxyUsername` is specified and its length is between 3 and 255 characters. |
 | Proxy settings error. `ProxyAuthRequired` is enabled but ProxyPassword is missing or empty | 204 | Provide a non-empty `ProxyPassword` when `ProxyAuthRequired` is enabled. |
-| A system reboot is pending due to Storage Sync file rename operations. Restart your server before installing the Azure File Sync agent. | 83 | A reboot is required. Restart the server before attempting agent installation again. |
-| The file signature is not valid. Or Signature validation failed for the downloaded MSI file | 86 | The installer file might be corrupted or tampered with. Re-download the MSI file from a trusted source. |
-| Certificate chain validation failed. | 86 | Ensure the required root certificates are installed. Refer to [this documentation](/azure/aks/aksarc/aks-edge-howto-offline-install).<br><br>**If using a proxy**, ensure the following domains are bypassed:<br>`login.microsoftonline.com`, `management.azure.com`, `go.microsoft.com`, `download.microsoft.com`, `download.windowsupdate.com`, `crl.microsoft.com`, `oneocsp.microsoft.com`, `ocsp.msocsp.com`, `www.microsoft.com`.<br><br>Restart the machine to apply any updates. |
-| Azure File Sync agent download or configuration failed. Details: Failed to configure auto update settings: Agent install directory not found in registry. Please check the installation. | 214 | 1. Open an elevated PowerShell session and check if .NET 4.7.2 or higher is installed:<br>```$releaseKey = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" -ErrorAction SilentlyContinue).Release```<br>2. If `$releaseKey` is less than `461808`, .NET 4.7.2 isn't installed.<br>3. Download and install .NET Framework 4.7.2 or later from the [official .NET download site](https://dotnet.microsoft.com/download/dotnet-framework). |
+| A system reboot is pending due to Storage Sync file rename operations. Restart your server before installing the Azure File Sync agent. | 83 | A reboot is required. Restart the server before installing the agent again. |
+| The file signature is not valid. Or Signature validation failed for the downloaded MSI file | 86 | The installer file might be corrupted or tampered with. Download the MSI file again from a trusted source. |
+| Certificate chain validation failed. | 86 | Ensure the required root certificates are installed. Refer to [Prerequisites for AKS Edge Essentials offline installation](/azure/aks/aksarc/aks-edge-howto-offline-install).<br><br>If using a proxy, ensure the following domains are bypassed:<br>`login.microsoftonline.com`, `management.azure.com`, `go.microsoft.com`, `download.microsoft.com`, `download.windowsupdate.com`, `crl.microsoft.com`, `oneocsp.microsoft.com`, `ocsp.msocsp.com`, `www.microsoft.com`.<br><br>Restart the computer to apply any updates. |
+| Azure File Sync agent download or configuration failed. Details: Failed to configure auto update settings: Agent install directory not found in registry. Please check the installation. | 214 | Open an elevated PowerShell session and check if .NET 4.7.2 or higher is installed:<br>```$releaseKey = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" -ErrorAction SilentlyContinue).Release```<br><br>If `$releaseKey` is less than `461808`, .NET 4.7.2 isn't installed. In this case, download and install .NET Framework 4.7.2 or later from the [official .NET download site](https://dotnet.microsoft.com/download/dotnet-framework). |
 
 ## Server registration
 

support/azure/virtual-machines/windows/kernel-mode-exception-not-handled.md

@@ -0,0 +1,31 @@
+---
+title: Bug Check 0x0000001E - KMODE_EXCEPTION_NOT_HANDLED
+description: Describes an issue where an Azure virtual machine (VM) experiences the KMODE_EXCEPTION_NOT_HANDLED bug check (0x0000001E).
+ms.date: 07/14/2025
+ms.reviewer: cwhitley
+ms.service: azure-virtual-machines
+ms.collection: windows
+ms.custom: sap:My VM is not booting
+---
+
+# Azure Windows VM displays bug check 0x0000001E - KMODE_EXCEPTION_NOT_HANDLED
+
+**Applies to:** :heavy_check_mark: Windows VMs
+
+This article helps you resolve an issue where a Microsoft Azure virtual machine (VM) experiences the **KMODE_EXCEPTION_NOT_HANDLED** bug check with the stop code 0x0000001E.
+
+## Symptoms
+
+When you use [Boot diagnostics](./boot-diagnostics.md) to view the screenshot of a VM, the Windows operating system (OS) displays the **KMODE_EXCEPTION_NOT_HANDLED** bug check (0x0000001E).
+
+:::image type="content" source="media/kernel-mode-exception-not-handled/kernel-mode-exception-not-handled-screen.png" alt-text="Screenshot of Windows operating system bug check KMODE_EXCEPTION_NOT_HANDLED (0x0000001E).":::
+
+## Cause
+
+This indicates that a kernel-mode program generated an exception that the error handler didn't catch. To interpret it, you must identify which exception was generated with a memory dump.
+
+## Collect a memory dump for troubleshooting
+
+If you experience this issue, [collect an OS memory dump file](./collect-os-memory-dump-file.md) and then [create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot) for Azure support to troubleshoot and diagnose the issue.
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/virtual-machines/windows/media/kernel-mode-exception-not-handled/kernel-mode-exception-not-handled-screen.png

@@ -344,6 +344,8 @@
       href: bad-pool-header.md
     - name: Bug check 0x0000001A - MEMORY_MANAGEMENT
       href: bug-check-memory-management.md
+    - name: Bug check 0x0000001E - KMODE_EXCEPTION_NOT_HANDLED
+      href: kernel-mode-exception-not-handled.md
     - name: Troubleshoot Windows VM OS with missing boot manager
       href: os-bootmgr-missing.md
     - name: OS isn't found
@@ -358,6 +360,7 @@
       href: azure-vm-cannot-rdp-driver-irql-not-less-equal.md
     - name: Azure VM cannot RDP - working on features
       href: azure-vm-cannot-rdp-working-features.md
+    
 
 - name: Cannot start or stop my VM
   items:

support/azure/virtual-machines/windows/toc.yml

@@ -3,9 +3,9 @@ title: Troubleshoot desktop flow run queue-based errors
 description: Provides solutions to desktop flow queue-based error codes like NoCandidateMachine or No machine able to run the desktop flow has been found.
 author: rpapostolis # GitHub alias
 ms.author: appapaio # Microsoft alias
-ms.reviewer: befrey, lulubran, johndund, guco, fredg
+ms.reviewer: befrey, lulubran, johndund, guco, fredg, ermathon
 ms.custom: sap:Desktop flows\Power Automate for desktop errors
-ms.date: 10/08/2024
+ms.date: 07/14/2025
 ---
 # Troubleshoot desktop flow run queue errors
 
@@ -27,6 +27,10 @@ You might also receive one of these common suberror codes:
 - [AttendedUserNotLoggedIn](#attendedusernotloggedin)
 - [UIFlowAlreadyRunning](#uiflowalreadyrunning)
 
+## How to investigate
+
+You can view lifecycle events for desktop flows in the queue from the monitor run details page, specifically in the [queue events section](/power-automate/desktop-flows/monitor-run-details#view-queue-events). These events provide detailed information about each launch attempt and can help you identify the underlying root cause of queue-based errors.
+
 ## Cause
 
 When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after six hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.

support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.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: 07/11/2025
+ms.date: 07/14/2025
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -50,7 +50,7 @@ _Original KB number:_   4555406
 |EndpointDoNotExist|404|Attended</br>Unattended|The endpoint wasn't found.</br>Register your machine again and schedule new runs.</br>This error typically occurs when the machine registration is deleted during the run, such as when the machine is re-registered.|
 |GroupIsEmpty|400|Attended</br>Unattended|The machine group is empty.</br> Add machines to the group, then reschedule new runs.|
 |MSEntraMachineAlwaysPromptingForPassword|400|Unattended|For more information about this error code, see [An unattended desktop flow run fails with the MSEntraMachineAlwaysPromptingForPassword error](msentramachinealwayspromptingforpassword-error.md).|
-|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.|
+|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.</br>To solve this issue, see [Troubleshoot desktop flow run queue-based errors](troubleshoot-desktop-flow-run-queue-errors.md) and inspect the [queue events in the monitor run details page](/power-automate/desktop-flows/monitor-run-details#view-queue-events).|
 |DesktopFlowsActionThrottled|429|Attended</br>Unattended|The desktop flow action failed because of throttling. This error code appears when too many desktop flows use the same connection. Check your connection usage and assign your desktop flows to multiple connections.|
 |DesktopFlowsActionTimeout|400|Attended</br>Unattended|The execution of the desktop flow action exceeded maximum duration.</br> Increase the time-out value that's set on the action or split the desktop flow into several shorter desktop flows.|
 |OnPremiseDataGatewayNotAvailable|502|Attended</br>Unattended|This error code only occurs when using an on-premises data gateway (deprecated) to connect to the machine. Check that the targeted machine and the data gateway on that machine are up and running.|