Updates for 8287

Author: ryanberg-aquent

support/azure/virtual-machines/windows/in-place-system-upgrade.md

@@ -7,21 +7,21 @@ ms.service: azure-virtual-machines
 ms.collection: windows
 ms.custom: sap:Windows Update, Guest Patching and OS Upgrades
 ---
-# In-place upgrade for supported VMs running Windows in Azure (Windows Client)
+# In-place upgrade for supported VMs running Windows in Azure (Windows client)
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
 _Original product version:_   Windows 10, version 1803, all editions, Windows 10, version 1709, all editions, Virtual Machine running Windows, Windows 10, Windows 8.1, Windows 7 Enterprise  
 _Original KB number:_   4014997
 
-This article describes how to do an in-place system upgrade of supported Windows 10-based and Windows-11-based Azure Virtual Machines (VM). This article also describes workarounds for Azure VMs that aren't supported for in-place system upgrades. 
+This article describes how to do an in-place system upgrade of supported Windows 10-based and Windows-11-based Azure Virtual Machines (VMs). This article also describes workarounds for Azure VMs that aren't supported for in-place system upgrades. 
 
 > [!NOTE]  
 > **Looking for Windows Server?**  
 > For Azure VMs running Windows Server, see [In-place upgrade for supported Windows Server VMs](/azure/virtual-machines/windows-in-place-upgrade).
 
 > [!CAUTION]
-> Following the process in this article causes a disconnection between the data plane and the [control plane](/azure/architecture/guide/multitenant/considerations/control-planes#responsibilities-of-a-control-plane) of the virtual machine (VM). Azure capabilities such as [Auto guest patching](/azure/virtual-machines/automatic-vm-guest-patching#how-does-automatic-vm-guest-patching-work), [Auto OS image upgrades](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade), [Hotpatching](/windows-server/get-started/hotpatch?toc=%2Fazure%2Fvirtual-machines%2Ftoc.json#supported-updates), and [Azure Update Manager](/azure/update-manager/overview) won't be available. To utilize these features, create a new VM using your preferred operating system instead of performing an in-place upgrade.
+> Following the process in this article causes a disconnection between the data plane and the [control plane](/azure/architecture/guide/multitenant/considerations/control-planes#responsibilities-of-a-control-plane) of the VM. Azure capabilities like [Auto guest patching](/azure/virtual-machines/automatic-vm-guest-patching#how-does-automatic-vm-guest-patching-work), [Auto OS image upgrades](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade), [Hotpatching](/windows-server/get-started/hotpatch?toc=%2Fazure%2Fvirtual-machines%2Ftoc.json#supported-updates), and [Azure Update Manager](/azure/update-manager/overview) won't be available. To utilize these features, create a new VM using your preferred operating system instead of performing an in-place upgrade.
 
 
 [!INCLUDE [Azure VM Windows Update / Windows OS Upgrade Diagnostic Tools](~/includes/azure/virtual-machines-runcmd-wu-tools.md)]
@@ -51,7 +51,7 @@ In-place system upgrades are supported for specific versions of Azure Windows VM
 
 ### Windows versions not yet supported for in-place system upgrades (consider using a workaround)
 
-- Windows 10 and 11 single-session -> Enterprise multi-session, all versions
+- Windows 10 and 11 single-session (includes Enterprise multi-session, all versions)
 - Windows 8.1
 - Windows 7 Enterprise
 
@@ -62,16 +62,17 @@ This process requires 45-60 minutes to complete and for the VM to restart. To do
 1. Run [Azure Virtual Machine (VM) Windows OS Upgrade Assessment Tool](windows-vm-osupgradeassessment-tool.md) to validate the OS upgrade path and any known issues.
 2. Verify that the Windows 10 VM doesn't use [Ephemeral OS Disk](/azure/virtual-machines/ephemeral-os-disks). This feature is currently not supported.
 3. Verify that the Windows 10 VM has at least 2 GB of RAM, and 12 GB of free disk space on the system disk.
-4. To prevent data loss, back up the Windows 10 VM by using [Azure Backup](/azure/backup/). Or use a third-party backup solution from [Azure Marketplace Backup & Recovery](https://azuremarketplace.microsoft.com/marketplace/apps?search=Backup%20%26%20Recovery&page=1).
+4. To prevent data loss, back up the Windows 10 VM by using [Azure Backup](/azure/backup/). You can also use a third-party backup solution from [Azure Marketplace Backup & Recovery](https://azuremarketplace.microsoft.com/marketplace/apps?search=Backup%20%26%20Recovery&page=1).
 5. To check whether the backup was successful, turn off the original Windows 10 VM and verify that a new VM can be successfully restored from the backup and that all applications are running successfully.
 
    > [!NOTE]  
-   > Either the original Windows 10 VM or the restored VM can be used as a source for in-place system upgrade. Both VMs cannot run simultaneously unless one VM's system name and IP address are changed to avoid conflicts.
+   > Either the original Windows 10 VM or the restored VM can be used as a source for in-place system upgrade. Both VMs can't run simultaneously unless one VM's system name and IP address are changed to avoid conflicts.
   
-6. Connect to the Windows 10 VM, and go to **Settings** > **Updates & Security** > **Windows Update**.
+6. Connect to the Windows 10 VM and then go to **Settings** > **Updates & Security** > **Windows Update**.
 7. In Windows Update, select **Check for updates**.
 8. When the Feature Update item appears, select **Download and install now**.
-9. The update will download and install. User settings and data will be preserved, and the VM will restart automatically.
+
+The update downloads and installs. User settings and data will be preserved, and the VM will restart automatically.
 
 If you have general questions about this procedure, post to [Microsoft Q&A](/answers/topics/azure-virtual-machines.html) and add the `azure-virtual-machines` tag to your question.
 
@@ -99,9 +100,10 @@ Follow the steps in the following article to upload the VHD to Azure and to depl
 > [!NOTE]  
 > When performing an in-place upgrade on Azure Windows VMs, the VM properties on the Azure portal aren't updated; the changes are only reflected within the OS. This means that the source image information in the VM properties, including the publisher, offer, and plan, remains unchanged. The image used to deploy the VM remains the same, and only the OS is upgraded.
 
-
 ## References
 
 [Microsoft server software support for Microsoft Azure virtual machines](https://support.microsoft.com/help/2721672).
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/virtual-machines/windows/reset-rdp.md

@@ -1,5 +1,5 @@
 ---
-title: Reset Remote Desktop Services or its administrator password in a Windows VM
+title: Reset Remote Desktop Services or its Admin Password in a Windows VM
 description: Learn how to reset an account password or Remote Desktop Services on a Windows VM by using the Azure portal or Azure PowerShell.
 services: virtual-machines
 documentationcenter: ''
@@ -16,13 +16,13 @@ ms.date: 03/26/2025
 ms.author: jarrettr
 ms.reviewer: herensin, v-monicaba
 ---
-# Reset Remote Desktop Services or its administrator password in a Windows VM
+# Reset Remote Desktop Services or its admin password in a Windows VM
 
 **Applies to:** :heavy_check_mark: Windows VMs
 
 [!INCLUDE [Feedback](../../../includes/feedback.md)]
 
-If you can't connect to a Windows virtual machine (VM), you can reset Remote Desktop Services and credentials by using the 'VM Access extension. Here are the available methods to do this:
+If you can't connect to a Windows virtual machine (VM), you can reset Remote Desktop Services and credentials by using the VMAccess Extension. Here are the available methods to do this:
 
 - [Reset by using the Azure portal](#reset-by-using-the-azure-portal)
 - [Reset by using the Azure PowerShell](#reset-by-using-the-azure-powershell)
@@ -39,13 +39,13 @@ If you're using PowerShell, make sure that you have the [latest PowerShell modul
 
 First, sign in to the [Azure portal](https://portal.azure.com) and then select **Virtual machines** on the left menu.
 
-### **Reset the local administrator account password**
+### **Reset the local admin account password**
 
 1. Select your Windows VM and then select **Reset password** under **Help**. The **Reset password** window is displayed.
 
 2. Select **Reset password**, enter a username and a password, and then select **Update**.
     > [!TIP]
-    > If you enter a different name than the current local administrator account on your VM, the VMAccess extension adds a local administrator account with that name, and assign your specified password to that account. If the local administrator account on your VM exists, the VMAccess extension resets the password. If the account is disabled, the VMAccess extension enables it.
+    > If you enter a different name than the current local admin account on your VM, the VMAccess extension adds a local admin account with that name, and assign your specified password to that account. If the local admin account on your VM exists, the VMAccess extension resets the password. If the account is disabled, the VMAccess extension enables it.
 3. Try connecting to your VM again.
 
 ### **Reset the Remote Desktop Services configuration**
@@ -62,9 +62,9 @@ This process will enable Remote Desktop service in the VM, and create a firewall
 
 First, make sure that you have  the [latest PowerShell module installed and configured](/powershell/azure/) and are signed in to your Azure subscription by using the [Connect-AzAccount](/powershell/module/az.accounts/connect-azaccount) cmdlet.
 
-### **Reset the local administrator account password**
+### Reset the local admin account password
 
-- Reset the administrator password or user name with the [Set-AzVMAccessExtension](/powershell/module/az.compute/set-azvmaccessextension) PowerShell cmdlet. The `typeHandlerVersion` setting must be 2.0 or greater, because version 1 is deprecated.
+- Reset the admin password or user name with the [Set-AzVMAccessExtension](/powershell/module/az.compute/set-azvmaccessextension) PowerShell cmdlet. The `typeHandlerVersion` setting must be 2.0 or greater, because version 1 is deprecated.
 
     ```powershell
     $SubID = "<SUBSCRIPTION ID>" 
@@ -77,7 +77,7 @@ First, make sure that you have  the [latest PowerShell module installed and conf
     ```
 ### **Reset the Remote Desktop Services configuration**
 
-1. Reset remote access to your VM with the [Set-AzVMAccessExtension](/powershell/module/az.compute/set-azvmaccessextension) PowerShell cmdlet. The following example resets the access extension named `VMAccessAgent` on a VM in the resource group:
+ - Reset remote access to your VM with the [Set-AzVMAccessExtension](/powershell/module/az.compute/set-azvmaccessextension) PowerShell cmdlet. The following example resets the access extension named `VMAccessAgent` on a VM in the resource group:
 
     ```powershell
     $SubID = "<SUBSCRIPTION ID>" 
@@ -92,7 +92,7 @@ First, make sure that you have  the [latest PowerShell module installed and conf
     > [!TIP]
     > At any point, a VM can have only a single VM access agent. To set the VM access agent properties, use the `-ForceRerun` option. When you use `-ForceRerun`, ensure you use the same name for the VM access agent that you used in any previous commands.
 
-1. If you still can't connect remotely to your virtual machine, see [Troubleshoot Remote Desktop connections to a Windows-based Azure virtual machine](troubleshoot-rdp-connection.md). If you lose the connection to the Windows domain controller, restore it from a domain controller backup.
+If you still can't connect remotely to your VM, see [Troubleshoot Remote Desktop connections to a Windows-based Azure virtual machine](troubleshoot-rdp-connection.md). If you lose the connection to the Windows domain controller, restore it from a domain controller backup.
 
 ## Troubleshoot and support
 

support/azure/virtual-machines/windows/windows-11-support-azure-virtual-machines.md

@@ -88,37 +88,37 @@ This article provides details about the applicable processors for Microsoft Azur
 
 > [!NOTE]
 >
-> - [Windows 11 on Arm](/windows/arm/overview) is currently in Preview release. Current Arm CPUs in Azure meet the CPU requirements for Windows 11 support. However, Windows 11 Arm images in Azure Marketplace don't meet the requirements for some security options (trusted launch, secure boot, and trusted platform module (TPM), in particular).
+> - [Windows 11 on Arm](/windows/arm/overview) is currently in Preview release. Current Arm CPUs in Azure meet the CPU requirements for Windows 11 support. However, Windows 11 Arm images in Azure Marketplace don't meet the requirements for some security options (Trusted Launch, secure boot, and trusted platform module (TPM), in particular).
 >
 > - The Azure portal might let you choose some VM products to deploy Windows 11 on, even if those VM products don't actually support Windows 11.
 >
-> - You currently can't upgrade to Windows 11, version 22H2 on Azure VMs that were deployed without trusted launch.
+> - You currently can't upgrade to Windows 11, version 22H2 on Azure VMs that were deployed without Trusted Launch.
 >
-> - You can set trusted launch only during VM creation and only on Azure generation 2 VMs. There is no option to set trusted launch after you create the VM.
+> - You can set Trusted Launch only during VM creation and only on Azure Generation 2 VMs. There's no option to set Trusted Launch after you create the VM.
 
 ## Criteria for Windows 11 eligibility
 
 There are multiple [criteria for Windows 11 eligibility](/windows/whats-new/windows-11-requirements#virtual-machine-support):
 
 - **Generation**: 2nd
 - **Storage**: At least 64 GB
-- **Security**: Secure boot capable, trusted launch, virtual TPM (vTPM) enabled
+- **Security**: Secure boot capable, Trusted Launch, virtual TPM (vTPM) enabled
 - **Memory**: At least 4 GB
 - **Processor**: Two or more virtual processors, and a VM host processor that meets Windows 11 processor requirements
 
-The following sections provide more detail about the three main criteria: VM generation (version), trusted launch, and CPU.
+The following sections provide more detail about the three main criteria: VM generation (version), Trusted Launch, and CPU.
 
 ### VM generation
 
-VMs must be generation 2. You can upgrade VMs from Generation 1 to Generation 2 by [upgrading to the Trusted launch security type](/azure/virtual-machines/trusted-launch-existing-vm-gen-1).
+VMs must be Generation 2. You can upgrade VMs from Generation 1 to Generation 2 by [upgrading to the Trusted Launch security type](/azure/virtual-machines/trusted-launch-existing-vm-gen-1).
 
-### Trusted launch
+### Trusted Launch
 
-VMs must be enabled for Trusted launch together with secure boot and virtual TPM. [Upgrading VMs from standard security to Trusted launch](/azure/virtual-machines/trusted-launch-existing-vm-gen-1) is supported. Many VMs are affected by this requirement. Before [June 28, 2023](https://techcommunity.microsoft.com/t5/azure-confidential-computing/announcing-trusted-launch-as-default-in-azure-portal/ba-p/3854872), trusted launch wasn't the default security type option when you created a VM in the Azure portal. Also, when Windows 11 was released, trusted launch wasn't available as a feature in Microsoft Azure.
+VMs must be enabled for Trusted Launch together with secure boot and virtual TPM. [Upgrading VMs from standard security to Trusted Launch](/azure/virtual-machines/trusted-launch-existing-vm-gen-1) is supported. Many VMs are affected by this requirement. Before [June 28, 2023](https://techcommunity.microsoft.com/t5/azure-confidential-computing/announcing-trusted-launch-as-default-in-azure-portal/ba-p/3854872), Trusted Launch wasn't the default security type option when you created a VM in the Azure portal. Also, when Windows 11 was released, Trusted Launch wasn't available as a feature in Azure.
 
 ### CPU
 
-With CPU requirements for Windows 11 evolving, review the up-to-date list of supported [Windows processor requirements](/windows-hardware/design/minimum/windows-processor-requirements). The listed processors represent the processor models that meet the minimum floor for the supported processor generations through the latest processors at the time of publication. These processors meet the design principles regarding security and reliability, and they meet the minimum system requirements for Windows 11. Subsequently released and future generations of processors that meet the same principles are considered as supported, even if they aren't explicitly listed.
+As CPU requirements for Windows 11 evolve, review the up-to-date list of supported [Windows processor requirements](/windows-hardware/design/minimum/windows-processor-requirements). The listed processors represent the processor models that meet the minimum for the supported processor generations through the latest processors at the time of publication. These processors meet the design principles regarding security and reliability, and they meet the minimum system requirements for Windows 11. Subsequently released and future generations of processors that meet the same principles are considered as supported, even if they aren't explicitly listed.
 
 The processor list might specify the latest offerings from processor manufacturers between updates. In the [Windows 11 Minimum Hardware Requirements download file](https://download.microsoft.com/download/7/8/8/788bf5ab-0751-4928-a22c-dffdc23c27f2/Minimum%20Hardware%20Requirements%20for%20Windows%2011.pdf#page=12), the *Processor* section (section 3.5) specifies a 1 GHz or faster processor that conforms to the following requirements: