Merge remote-tracking branch 'upstream/main' into AB#7617-Troubleshoot-Windows-Update-Error-0x8024001E

Author: v-tappelgate

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

@@ -110,6 +110,8 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070002.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error code 0x8007000d
       href: ../../../windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x8007000e or 0x800705aa
+      href: ../../../windows-client/installing-updates-features-roles/error-0x8007000e-0x800705aa-insufficient-virtual-memory.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error Code 0x8007045b
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error code 0x80070490

support/dynamics-365/supply-chain/procurement/media/unable-to-submit-pvrr/delete-vendor.png

@@ -0,0 +1,60 @@
+---
+title: Troubleshoot Failures When Submitting a Prospective Vendor Registration Request
+description: Learn how to fix errors when you submit a Prospective Vendor Registration Request (PVRR). Identify causes such as duplicate vendors or missing contact info.
+ms.reviewer: sugaur
+ms.date: 11/10/2025
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
+---
+
+# Troubleshoot failures when submitting a Prospective Vendor Registration Request
+
+This article provides troubleshooting guidance for failures that occur when you submit a Prospective Vendor Registration Request (PVRR).
+
+## Symptoms
+
+You experience one or more of the following symptoms:
+
+- You can't submit a PVRR in Microsoft Dynamics 365 Finance and Operations.
+- The _Vendor Registration Wizard_ doesn't finish or progress.
+
+## Cause 1: The vendor already exists
+
+A PVRR submission might fail if the vendor already exists in the system. In this situation, the submission creates duplicate records.
+
+### Solution
+
+To avoid duplicate records:
+
+1. Go to **Vendor collaboration > All contacts**.
+
+1. Find the correct vendor contact.
+
+1. To link the existing vendor without creating a new PVRR, select **Provision vendor user**.
+
+   :::image type="content" source="./media/unable-to-submit-pvrr/provision-vendor-user.png" alt-text="The vendor contact page that has the provision vendor user button highlighted.":::
+
+## Cause 2: Missing vendor contact information
+
+A PVRR submission might fail if the vendor contact information is missing in the **Vendor collaboration** > **All contacts** screen.
+
+### Solution
+
+To add the required vendor contact info:
+
+1. Go to **System administration** > **Users**, and delete the existing user record that's associated with the vendor.
+
+   :::image type="content" source="./media/unable-to-submit-pvrr/delete-vendor.png" alt-text="The users page that has the delete button highlighted.":::
+
+1. Reinvite the vendor by selecting **Procurement and Sourcing** > **Vendor collaboration requests** > **Prospective vendor request registration**.
+
+   :::image type="content" source="./media/unable-to-submit-pvrr/invite-user.png" alt-text="The Prospective vendor request registration page that has the Invite user button highlighted.":::
+
+This process creates both the user and vendor contacts.
+
+## Cause 3: Incorrect user provisioning steps
+
+A PVRR submission might fail if the user provisioning steps aren't followed correctly.
+
+### Solution
+
+Follow your configured vendor request approval process (automatic or manual). For more information, see: [Onboard vendors](/dynamics365/supply-chain/procurement/vendor-onboarding)

support/dynamics-365/supply-chain/procurement/media/unable-to-submit-pvrr/invite-user.png

@@ -151,6 +151,8 @@ items:
         href: procurement/default-tax-group-and-discount.md
       - name: Error "Object reference not set" occurs during purchase order confirmation
         href: procurement/object-reference-not-set.md
+      - name: Failures when submitting a Prospective Vendor Registration Request
+        href: procurement/unable-to-submit-pvrr.md
       - name: Imported purchase orders show incorrect line numbers
         href: procurement/line-number-increments.md
       - name: Order taker not auto-filled when creating purchase or sales orders

support/dynamics-365/supply-chain/procurement/media/unable-to-submit-pvrr/provision-vendor-user.png

@@ -54,17 +54,17 @@ To fix the problem, unregister the device by running `dsregcmd /leave` at an ele
 ## Get a list of pending devices
 
 1. The [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true) must be installed to execute Microsoft Graph PowerShell commands.
-2. Use the `Connect-MgGraph` command to sign in to your Microsoft Entra tenant. For more information, see [Get started with the Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/get-started?view=graph-powershell-1.0&preserve-view=true).
-3. Count all pending devices:
-
-    ```powershell
-    (Get-MgDevice -All -Filter "TrustType eq 'ServerAd'" | Where-Object{($_.ProfileType -ne "RegisteredDevice") -and (-not $_.AlternativeSecurityIds)}).count
-    ```
+1. Use the `Connect-MgGraph` command to sign in to your Microsoft Entra tenant. For more information, see [Get started with the Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/get-started?view=graph-powershell-1.0&preserve-view=true).
+1. Count all pending devices:
 
+   ```powershell
+   (Get-MgDevice -All -Filter "TrustType eq 'ServerAd'" | Where-Object{((-not $_.AlternativeSecurityIds)}).count
+   ```
+    
     You can also save the returned data in a CSV file:
-
-    ```powershell
-    Get-MgDevice -All -Filter "TrustType eq 'ServerAd'" | Where-Object{($_.ProfileType -ne "RegisteredDevice") -and (-not $_.AlternativeSecurityIds)} | select-object -Property AccountEnabled, Id, DeviceId, DisplayName, OperatingSystem, OperatingSystemVersion, TrustType | export-csv pendingdevicelist-summary.csv -NoTypeInformation
-    ```
-
+   
+   ```powershell
+   Get-MgDevice -All -Filter "TrustType eq 'ServerAd'" | Where-Object{(-not $_.AlternativeSecurityIds)} | select-object -Property AccountEnabled, Id, DeviceId, DisplayName, OperatingSystem, OperatingSystemVersion, TrustType | export-csv pendingdevicelist-summary.csv -NoTypeInformation
+   ```
+    
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/dynamics-365/supply-chain/procurement/unable-to-submit-pvrr.md

@@ -1,17 +1,18 @@
 ---
 title: Troubleshoot Windows Update Error Code 0x8007000e or 0x800705aa
 description: Discusses how to resolve Windows Update error code 0x8007000e or 0x800705aa.
-ms.date: 10/15/2025
+ms.date: 11/26/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
 ms.reviewer: kaushika
 ms.custom:
-- sap:windows servicing, updates and features on demand\windows update - install errors unknown or code not listed
+- sap:windows servicing, updates and features on demand\windows update - install errors starting with 0x8007 (error)
 - pcy:WinComm Devices Deploy
 appliesto:
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
 - ✅ <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/lifecycle/products/azure-virtual-machine target=_blank>Supported versions of Azure Virtual Machine</a>
 ---
 
 # Troubleshoot Windows Update error code 0x8007000e or 0x800705aa
@@ -33,11 +34,15 @@ Insufficient system resources exist to complete the requested service.
 ```
 
 > [!NOTE]  
-> The second message typically occurs when you use `dism /online /add-package /packagepath:<path of .cab file>`to install the update.
+> The second message typically occurs if you use `dism /online /add-package /packagepath:<path of .cab file>`to install the update.
+
+When you review events in Event Viewer, you might also find Event ID 2004 recorded. The description of this event resembles the following example:
+
+> Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: java.exe (1152) consumed 33821605888 bytes, java.exe (6316) consumed 5259997184 bytes, and java.exe (12536) consumed 1569894400 bytes.
 
 ## Cause
 
-This issue occurs if the computer doesn't have enough available virtual memory for Windows to install the update. The most common causes of this issue are the following conditions:
+This issue occurs if the computer or virtual machine (VM) doesn't have enough available virtual memory for Windows to install the update. The most common causes of this issue are the following conditions:
 
 - Third-party applications are consuming lots of virtual memory.
 - The computer's virtual memory isn't managed automatically. Instead, it's manually configured.
@@ -61,13 +66,20 @@ After the computer restarts, try again to update it.
 
 ## Resolution
 
-To configure the computer to automatically manage its virtual memory, follow these steps.
+> [!IMPORTANT]  
+> Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
+
+> [!NOTE]  
+> If the affected computer is a VM, consider upgrading the virtual hardware of the VM to increase its available memory resources.
+
+To configure the computer to automatically manage its virtual memory, follow these steps:
 
-1. To open **System Properties**, select Search and then enter **sysdm.cpl**.
-1. In **System Properties**, select **Advanced**, and then under **Performance**, select **Settings**.
-1. In **Performance Options**, select **Advanced**, and then under **Virtual memory**, select **Change**.
+1. Open **System Properties**: Select **Search**, and enter **sysdm.cpl**.
+1. In **System Properties**, select **Advanced** > **Performance** > **Settings**.
+1. In **Performance Options**, select **Advanced** > **Virtual memory** > **Change**.
 1. Make sure that **Automatically manage paging file size for all drives** is selected, and then select **OK**.
 1. Restart the computer.
+1. To make sure that this issue doesn't reoccur, monitor the computer's available memory resources.
 
 ## More information