Edit

Reset local Windows password for Azure VM offline

  • Article
  • 6 minutes to read

You can reset the local Windows password of a VM in Azure using the Azure portal or Azure PowerShell provided the Azure guest agent is installed. This method is the primary way to reset a password for an Azure VM. If you encounter issues with the Azure guest agent not responding, or failing to install after uploading a custom image, you can manually reset a Windows password. This article details how to reset a local account password by attaching the source OS virtual disk to another VM. The steps described in this article do not apply to Windows domain controllers.

Warning

Only use this process as a last resort. Always try to reset a password using the Azure portal or Azure PowerShell first.

Overview of the process

The core steps for performing a local password reset for a Windows VM in Azure when there is no access to the Azure guest agent is as follows:

  1. Stop the affected VM.
  2. Create a snapshot for the OS disk of the VM.
  3. Create a copy of the OS disk from the snapshot.
  4. Attach and mount the copied OS disk to another Windows VM, then create some config files on the disk. The files will help you to reset the password.
  5. Unmount and detach the copied OS disk from the troubleshooting VM.
  6. Swap the OS disk for the affected VM.

Detailed steps for the VM with Resource Manager deployment

Note

The steps do not apply to Windows domain controllers. It only works on standalone server or a server that is a member of a domain.

Always try to reset a password using the Azure portal or Azure PowerShell before trying the following steps. Make sure you have a backup of your VM before you start.

  1. Take a snapshot for the OS disk of the affected VM, create a disk from the snapshot, and then attach the disk to a troubleshoot VM. For more information, see Troubleshoot a Windows VM by attaching the OS disk to a recovery VM using the Azure portal.

  2. Connect to the troubleshooting VM using Remote Desktop.

  3. Create gpt.ini in \Windows\System32\GroupPolicy on the source VM's drive (if gpt.ini exists, rename to gpt.ini.bak):

    Warning

    Make sure that you do not accidentally create the following files in C:\Windows, the OS drive for the troubleshooting VM. Create the following files in the OS drive for your source VM that is attached as a data disk.

    Add the following lines into the gpt.ini file you created:

    [General]
gPCFunctionalityVersion=2
gPCMachineExtensionNames=[{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}]
Version=1

    Screenshot shows the updates made to the gpt.ini file.

  4. Create scripts.ini in \Windows\System32\GroupPolicy\Machine\Scripts\. Make sure hidden folders and file name extensions are shown. If needed, create the Machine or Scripts folders.

    Add the following lines the scripts.ini file you created:

    [Startup]
0CmdLine=FixAzureVM.cmd
0Parameters=

    Screenshot shows the updates made to the script.ini file.

  5. Create FixAzureVM.cmd in \Windows\System32\GroupPolicy\Machine\Scripts\Startup\ with the following contents, replacing <username> and <newpassword> with your own values:

    net user <username> <newpassword> /add /Y
net localgroup administrators <username> /add
net localgroup "remote desktop users" <username> /add

    Screenshot shows the newly created FixAzureVM.cmd file where you update the username and password.

    You must meet the configured password complexity requirements for your VM when defining the new password.

  6. In Azure portal, detach the disk from the troubleshooting VM.

  7. Change the OS disk for the affected VM.

  8. After the new VM is running, connect to the VM using Remote Desktop with the new password you specified in the FixAzureVM.cmd script.

  9. From your remote session to the new VM, remove the following files to clean up the environment:

    • From %windir%\System32\GroupPolicy\Machine\Scripts\Startup
      • remove FixAzureVM.cmd
    • From %windir%\System32\GroupPolicy\Machine\Scripts
      • remove scripts.ini
    • From %windir%\System32\GroupPolicy
      • remove gpt.ini (if gpt.ini existed before, and you renamed it to gpt.ini.bak, rename the .bak file back to gpt.ini)

Detailed steps for Classic VM

Important

Classic VMs will be retired on March 1, 2023.

If you use IaaS resources from ASM, please complete your migration by March 1, 2023. We encourage you to make the switch sooner to take advantage of the many feature enhancements in Azure Resource Manager.

For more information, see Migrate your IaaS resources to Azure Resource Manager by March 1, 2023.

Note

The steps do not apply to Windows domain controllers. It only works on standalone server or a server that is a member of a domain.

Always try to reset a password using the Azure portal or Azure PowerShell before trying the following steps. Make sure you have a backup of your VM before you start.

  1. Delete the affected VM in Azure portal. Deleting the VM only deletes the metadata, the reference of the VM within Azure. The virtual disks are retained when the VM is deleted:

    • Select the VM in the Azure portal, then click Delete:

      Screenshot shows the Delete button in an existing Classic VM page.

  2. Attach the source VM's OS disk to the troubleshooting VM. The troubleshooting VM must be in the same region as the source VM's OS disk (such as West US):

    1. Select the troubleshooting VM in the Azure portal. Click Disks | Attach existing:

      Screenshot shows the Attach existing button of the troubleshooting VM.

    2. Select VHD File and then select the storage account that contains your source VM:

      Screenshot shows the location to select storage account.

    3. Check the box marked Show classic storage accounts, then select the source container. The source container is typically vhds:

      Screenshot shows the Show classic storage accounts option is cleared.

      Screenshot shows the vhds is selected as storage container.

    4. Select the OS vhd to attach. Click Select to complete the process:

      Screenshot shows the selected source virtual disk.

    5. Click Ok to attach the disk

      Screenshot shows the Attach existing disk page, at the bottom of which, there's an OK button.

  3. Connect to the troubleshooting VM using Remote Desktop and ensure the source VM's OS disk is visible:

    1. Select the troubleshooting VM in the Azure portal and click Connect.

    2. Open the RDP file that downloads. Enter the username and password of the troubleshooting VM.

    3. In File Explorer, look for the data disk you attached. If the source VM's VHD is the only data disk attached to the troubleshooting VM, it should be the F: drive:

      Screenshot shows the F local disk in File Explorer.

  4. Create gpt.ini in \Windows\System32\GroupPolicy on the source VM's drive (if gpt.ini exists, rename to gpt.ini.bak):

    Warning

    Make sure that you do not accidentally create the following files in C:\Windows, the OS drive for the troubleshooting VM. Create the following files in the OS drive for your source VM that is attached as a data disk.

    Add the following lines into the gpt.ini file you created:

    [General]
gPCFunctionalityVersion=2
gPCMachineExtensionNames=[{42B5FAAE-6536-11D2-AE5A-0000F87571E3}{40B6664F-4972-11D1-A7CA-0000F87571E3}]
Version=1

    Screenshot shows the updates made to the gpt.ini file for Classic VM.

  5. Create scripts.ini in \Windows\System32\GroupPolicy\Machine\Scripts\. Make sure hidden folders and file name extensions are shown. If needed, create the Machine or Scripts folders.

    Add the following lines the scripts.ini file you created:

    [Startup]
0CmdLine=FixAzureVM.cmd
0Parameters=

    Screenshot shows the updates made to the scripts.ini file for Classic VM.

  6. Create FixAzureVM.cmd in \Windows\System32\GroupPolicy\Machine\Scripts\Startup\ with the following contents, replacing <username> and <newpassword> with your own values:

    net user <username> <newpassword> /add /Y
net localgroup administrators <username> /add
net localgroup "remote desktop users" <username> /add

    Screenshot shows the newly created FixAzureVM.cmd file where you update the username and password for Classic VM.

    You must meet the configured password complexity requirements for your VM when defining the new password.

  7. In Azure portal, detach the disk from the troubleshooting VM:

    1. Select the troubleshooting VM in the Azure portal, click Disks.

    2. Select the data disk attached in step 2, click Detach, then click OK.

    Screenshot shows the detached disk in step 2.

    Screenshot shows the Detach button.

  8. Create a VM from the source VM's OS disk:

    Screenshot shows the Disk (classic) item.

    Screenshot shows the subscriptions.

    Screenshot highlights the Create VM button.

Complete the Create virtual machine experience

  1. After the new VM is running, connect to the VM using Remote Desktop with the new password you specified in the FixAzureVM.cmd script.

  2. From your remote session to the new VM, remove the following files to clean up the environment:

    • From %windir%\System32\GroupPolicy\Machine\Scripts\Startup\
      • remove FixAzureVM.cmd
    • From %windir%\System32\GroupPolicy\Machine\Scripts
      • remove scripts.ini
    • From %windir%\System32\GroupPolicy
      • remove gpt.ini (if gpt.ini existed before, and you renamed it to gpt.ini.bak, rename the .bak file back to gpt.ini)

Next steps

If you still cannot connect using Remote Desktop, see the RDP troubleshooting guide. The detailed RDP troubleshooting guide looks at troubleshooting methods rather than specific steps. You can also open an Azure support request for hands-on assistance.

Contact us for help

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure community support.