Added troubleshooting guidance for temporary paging file issue

azure-local/manage/troubleshoot-arc-enabled-vms.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Local Virtual Machines enabled by Azure Arc
 description: Learn how to troubleshoot issues you experience with Azure Local Virtual Machines (VMs).
 author: alkohli
 ms.topic: how-to
-ms.date: 05/29/2025
+ms.date: 06/16/2025
 ms.author: alkohli
 ms.reviewer: vlakshmanan
 ms.service: azure-local
@@ -162,7 +162,30 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
         }
 ```
 
+## "Windows created a temporary paging file" message appears at startup
 
+**Error:**
+
+When you deploy an Azure Local VM using the SQL Server 2022 on Windows Server 2022 Azure marketplace images (Standard or Enterprise), you might see the following warning at startup:
+
+*Windows created a temporary paging file...*
+
+**Resolution:**
+
+To resolve this issue, follow these steps:
+
+1. Select **OK** on the warning popup. Or, go to **System Properties** > **Advanced** > **Performance** > **Settings** to open the **Performance Options** window.
+1. In the **Performance Options** window, select **Change** under the **Virtual memory** section.
+
+    :::image type="content" source="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-1.png" alt-text="Screenshot of the Performance Options window highlighing the Change button." lightbox="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-1.png":::
+
+1. In the **Virtual Memory** window, select **System managed size**.  Also ensure that the **Automatically manage paging file size for all drives** checkbox is cleared.
+
+    :::image type="content" source="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-2.png" alt-text="Screenshot of the Virtual Memory window showing options to configure the paging file size for each drive." lightbox="./media/troubleshoot-arc-enabled-vms/temporary-paging-file-2.png":::
+
+1. Select **Set**, then select **OK** to apply the changes.
+
+1. Restart the VM. After the restart, the warning message should no longer appear.
 
 ## Next steps