update article-fix

Author: TobyTu

articles/virtual-machines/troubleshooting/media/unresponsive-vm-apply-group-policy/Applying-Group-Policy.png renamed to articles/virtual-machines/troubleshooting/media/unresponsive-vm-apply-group-policy/applying-group-policy-1.png

@@ -16,26 +16,26 @@ ms.date: 05/07/2020
 ms.author: v-mibufo
 ---
 
-# VM is unresponsive while applying ‘Group Policy Local Users & Groups’ policy
+# VM becomes unresponsive while applying ‘Group Policy Local Users & Groups’ policy
 
-This article provides steps to resolve issues where the load screen is stuck applying a policy during boot in an Azure VM.
+This article provides steps to resolve issues where the load screen is stuck when applying a policy during boot in an Azure VM.
 
 ## Symptoms
 
-When you use [Boot diagnostics](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/boot-diagnostics) to view the screenshot of the VM, you will see that the screen is stuck loading with the message: ‘*Applying Group Policy Local Users and Groups policy*’.
+When using [Boot diagnostics](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/boot-diagnostics) to view a screenshot of the VM, the screen is stuck loading with the message: ‘*Applying Group Policy Local Users and Groups policy*’.
 
-![Screen showing Applying Group Policy Local Users and Groups policy loading (Windows Server 2012 R2)](media/unresponsive-vm-apply-group-policy/Applying-Group-Policy.png)
+:::image type="content" source="media//unresponsive-vm-apply-group-policy/applying-group-policy-1.png" alt-text="Screenshot of Applying Group Policy Local Users and Groups policy loading (Windows Server 2012 R2).":::
 
-![Screen showing Applying Group Policy Local Users and Groups policy loading (Windows Server 2012).](media/unresponsive-vm-apply-group-policy/Applying-Group-Policy2.png)
+:::image type="content" source="media/unresponsive-vm-apply-group-policy/applying-group-policy-2.png" alt-text="Screenshot of Applying Group Policy Local Users and Groups policy loading (Windows Server 2012).":::
 
 ## Cause
 
-This issue is caused by conflicting locks when the policy is attempting to cleanup old user profiles.
+There are conflicting locks when the policy attempts to cleanup old user profiles.
 
 > [!NOTE]
-> This applies only on Windows Server 2012 and Windows Server 2012 R2.
+> This applies only to Windows Server 2012 and Windows Server 2012 R2.
 
-The policy being applied that won’t finish its processes is:
+Here’s the problematic policy:
 
 `Computer Configuration\Policies\Administrative Templates\System/User Profiles\Delete user profiles older than a specified number of days on system restart`
 
@@ -49,7 +49,7 @@ The policy being applied that won’t finish its processes is:
 4. [Rebuild the VM](#step-4-rebuild-the-vm)
 
 > [!NOTE]
-> When encountering this boot error, the Guest OS is not operational. You will be troubleshooting in offline mode to resolve this issue.
+> If your encounter this boot error, the Guest OS isn’t operational. You must troubleshoot in Offline mode.
 
 ### Step 1: Create and access a repair VM
 
@@ -59,37 +59,38 @@ The policy being applied that won’t finish its processes is:
 ### Step 2: Disable the policy
 
 1. On the repair VM, open the Registry Editor.
-2. Locate the key **HKEY_LOCAL_MACHINE** and then select **File** > **Load Hive...** from the menu.
+2. Locate the key **HKEY_LOCAL_MACHINE** and select **File** > **Load Hive...** from the menu.
 
-    ![Screenshot shows highlighted HKEY_LOCAL_MACHINE, as well as the menu containing “Load Hive…”](media/unresponsive-vm-apply-group-policy/registry.png)
+    :::image type="content" source="media/unresponsive-vm-apply-group-policy/registry.png" alt-text="Screenshot shows highlighted HKEY_LOCAL_MACHINE and the menu containing “Load Hive…".":::
 
-    - Load Hive allows you to load a registry key from an offline system, which in this case is your broken disk attached to your repair VM.
-    - **HKEY_LOCAL_MACHINE** is where all the system-wide settings are stored and may be abbreviated as “HKLM”.
-3. In the attached disk, navigate to the `\windows\system32\config\SOFTWARE` file and open it.
+    - Load Hive allows you to load registry keys from an offline system, in this case the broken disk attached to the repair VM.
+    - System-wide settings are stored on `HKEY_LOCAL_MACHINE` and can be abbreviated as “HKLM”.
+3. In the attached disk, go to the `\windows\system32\config\SOFTWARE` file and open it.
 
-    a) When you open it, you will be prompted for a name. Enter BROKENSOFTWARE as the name.<br/>
-    b) To verify that BROKENSOFTWARE was loaded, you can expand **HKEY_LOCAL_MACHINE** and look for the added BROKENSOFTWARE key.
-4. Navigate to the BROKENSOFTWARE and validate if the CleanupProfile key exists in the hive that was loaded.
+    a) You will be prompted for a name. Enter BROKENSOFTWARE.<br/>
+    b) To verify that BROKENSOFTWARE was loaded, expand **HKEY_LOCAL_MACHINE** and look for the added BROKENSOFTWARE key.
+4. Navigate to BROKENSOFTWARE and check if the CleanupProfile key exists in the loaded hive.
 
-    a) If the key does not exist, then the CleanupProfile policy is not set up. In this case, you should [submit a support ticket](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade), including the memory.dmp file located in the Windows directory of the attached OS disk.<br/>
-    b) If the key does exist, then it means that the CleanupProfile policy is set up. Its value represents the retention policy in days. Continue to delete the key.
-5. Delete the CleanupProfiles key using the command below:
+    a) If the key exists, then the CleanupProfile policy is set, its value represents the retention policy in days. Continue deleting the key.<br/>
+    b) If the key doesn't exist, the CleanupProfile policy isn't set. [Submit a support ticket](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade), including the memory.dmp file located in the Windows directory of the attached OS disk.
+
+5. Delete the CleanupProfiles key using this command:
 
     ```
     reg delete "HKLM\BROKENSOFTWARE\Policies\Microsoft\Windows\System" /v CleanupProfiles /f
     ```
-6.	Unload the BROKENSOFTWARE hive using the command below:
+6.	Unload the BROKENSOFTWARE hive using this command:
 
     ```
     reg unload HKLM\BROKENSOFTWARE
     ```
 
 ### Step 3: Enable Serial Console and memory dump collection
 
-To enable memory dump collection and Serial Console, run the script below:
+To enable memory dump collection and Serial Console, run this script:
 
 1. Open an elevated command prompt session (Run as administrator).
-2. Run the following commands:
+2. Run these commands:
 
     **Enable Serial Console**: 
     
@@ -100,9 +101,9 @@ To enable memory dump collection and Serial Console, run the script below:
     ```
     bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200 
     ```
-3. Verify if the free space on the OS disk is as much as the memory size (RAM) on the VM.
+3. Verify if the free space on the OS disk is at least equal to the VM’s memory size (RAM).
 
-    If there's not enough space on the OS disk, you should change the location where the memory dump file will be created and refer that to any data disk attached to the VM that has enough free space. To change the location, replace “%SystemRoot%” with the drive letter (for example “F:”) of the data disk in the below commands.
+    If there isn’t enough space on the OS disk, change the memory dump location and refer it to an attached data disk with enough free space. To change the location, replace “%SystemRoot%” with the drive letter (e.g. “F:”) of the data disk in the commands below.
 
     **Suggested configuration to enable OS dump**:
 
@@ -138,8 +139,8 @@ To enable memory dump collection and Serial Console, run the script below:
 
 Use [step 5 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands#repair-process-example) to reassemble the VM.
 
-If this fixed the issue, then you have disabled this policy locally. For a permanent solution, do not to use the CleanupProfiles policy on VMs, and use another method to perform the profile cleanup.
+If the issue is fixed, the policy has been disabled locally. For a permanent solution, don’t use CleanupProfiles policy on VMs. Use a different method to perform profile cleanups.
 
-Policy to stop using:
+Don’t use this policy:
 
-Machine\Admin Templates\System\User Profiles\Delete user profiles older than a specified number of days on system restart
+`Machine\Admin Templates\System\User Profiles\Delete user profiles older than a specified number of days on system restart`