> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/compute/guides-for-server-management/reset-your-password-in-windows.md).

# Reset your password in Windows

***

{% hint style="danger" %}
In case anything goes wrong, make sure you have a backup of your Windows server before starting this operation. For instructions on how to make a backup, see [KVM → Manage virtual machines](/products/compute/kvm-virtual-machines/how-tos/manage-virtual-machines.md) or [VMware → Manage virtual machine](/products/compute/vmware-virtual-machines/how-tos/manage-virtual-machines.md), depending on which platform your server is on. If it's a dedicated server, see [Bare metal → Backup your server with Bacula](/products/bare-metal/dedicated-servers/how-tos/backup-your-server-with-bacula.md).\
\
**Note:** This procedure is not officially supported by Microsoft. You perform it at your own risk, and Glesys cannot provide support for issues that arise as a result.
{% endhint %}

## Initial reboot to complete any pending updates

To reset your password, you'll need to reboot your server several times. You'll also need to abort the boot a couple of times, depending on the platform and the OS, by performing a power reset. To make sure you don't abort a pending Windows Update and break the system, this first reboot ensures all updates can finish without being aborted.

{% tabs %}
{% tab title="KVM/VMware" %}
Use **Actions → Reboot** from the Glesys control panel. This will initiate a graceful reboot.

<figure><img src="/files/VWrWAxgtFNWhcnDDY4gf" alt=""><figcaption></figcaption></figure>

Once you have clicked on **Reboot**, open the console using **Actions → Console**. Watch the console, and let any Windows Updates or other tasks finish during the reboot process before proceeding. For more information about the console, please see [KVM → Connect to the VM console](/products/compute/kvm-virtual-machines/how-tos/connect-to-the-vm-console.md) or [VMware → Connect to the VM console](/products/compute/vmware-virtual-machines/how-tos/connect-to-the-vm-console.md), depending on which platform you are using.

<figure><img src="/files/zh17EMIVcrJCNXT33Z6w" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Dedicated server" %}
Use [**IPMI**](/products/bare-metal/dedicated-servers/how-tos/connect-to-the-server-using-ipmi.md) **→ Power control → Software shutdown** to gracefully power off the server.

<figure><img src="/files/pSo2Vm2MbvRmX7ai4ewS" alt=""><figcaption></figcaption></figure>

Watch the console, and let any Windows Updates or other tasks finish during the shutdown process before proceeding.

Once the server is powered off, turn it back on using **Power Control → Set Power On**. Let any remaining updates finish.

<figure><img src="/files/7GwNMvVq1Pw9qJgtYhzB" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

The server should now boot to the login screen, as shown below.

<figure><img src="/files/Af0J6LhtFpIXbN5yELH0" alt=""><figcaption></figcaption></figure>

## Boot into Windows Recovery Environment

To boot Windows Server into the *Windows Recovery Environment*, you must now trick Windows into believing there is a boot problem. This works for all VM templates. However, if you have installed Windows Server from an ISO file, the command prompt in the Windows Recovery Environment might be password-protected. In these cases, you need to boot from a virtual CD/DVD with an ISO file instead.

{% tabs %}
{% tab title="KVM/VMware" %}
Start by clicking on **Actions → Reboot** once again, while keeping an eye on the console. As soon as you see the Glesys logo and the spinning icon, click **Actions → Power off (forced)**. The console will now disappear.

<figure><img src="/files/W2TDvZxygkokXytfx7Am" alt=""><figcaption></figcaption></figure>

Here comes the tricky part. Now you must power on the server using **Actions → Power on**, and then quickly, as soon as the option becomes available, turn it off again using **Actions → Power off (forced)**. This process must be repeated at least three times in a row.

After performing the power-cycle operation as described, let the server boot and open a new console window. The previous console window won't have any output after the power cycle. If it was successful, you should now see the Windows Recovery Environment. Here, click **Advanced options**.

<figure><img src="/files/MWGpQenU55FNY031Q7rk" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Dedicated server" %}
Start by clicking **Power Control → Software Shutdown** and wait until it's powered off. Then, power on the server using **Power Control → Set Power On** while keeping an eye on the console. As soon as you see that Windows is booting (when the spinning circle appears), click **Power Control → Set Power Reset**.

<figure><img src="/files/Gj25GgdHIOOTNDk4QjSU" alt=""><figcaption></figcaption></figure>

Wait until you see Windows booting again, and then click **Power Control → Set Power Reset** again. This process must be repeated at least three times in a row, or until you see the Windows Recovery Environment start.

After performing the power-cycle operation as described, let the server boot and keep the console window open. If it was successful, you should now see the Windows Recovery Environment. Here, click **Advanced options**.

<figure><img src="/files/91GzwjNSfeCTFPZrhfHA" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Dedicated server (ISO file)" %}
You need a copy of the Windows Server ISO file matching the version installed on your server. You then need to boot your server from this ISO file using the [IPMI Java console](/products/bare-metal/dedicated-servers/how-tos/connect-to-the-server-using-ipmi.md#console-access-java-based). To boot your server from an ISO file, follow the process described in [Reinstall the server's operating system from an ISO file](/products/bare-metal/dedicated-servers/how-tos/connect-to-the-server-using-ipmi.md#reinstall-the-servers-operating-system-from-an-iso-file) (but don't reinstall the operating system, only boot the ISO file).

When the Windows ISO file is read, you'll be presented with a text saying *Press any key to boot from CD or DVD*. Press any key here to boot from the virtual CD-ROM (ISO file).

When the Windows installer starts and asks for the language to install, click **Next**.

<figure><img src="/files/nkxPgXrCrPoTi27IpELE" alt=""><figcaption></figcaption></figure>

On the next screen, click **Repair your computer**.

<figure><img src="/files/h7Yqk2DMXleiq12LH688" alt=""><figcaption></figcaption></figure>

The *Windows Recovery Environment* will now start. You might be asked to select a keyboard layout as the first question in the Windows Recovery Environment before you can move on.
{% endtab %}

{% tab title="VMware (ISO file)" %}
Start by mounting a matching ISO for the Windows Server version running on your VMware server. Click the **CD/DVD** tab on the overview, select the ISO file from the dropdown menu, and click **Mount ISO**.

<figure><img src="/files/4PVVoew67R7KcI10feR6" alt=""><figcaption></figcaption></figure>

Next, shut down the VM by clicking **Actions → Power off**. Then, click **Actions → Power on into BIOS**. This will boot the VM into the BIOS, allowing you to boot from the virtual DVD with the ISO file.

<figure><img src="/files/IujWCJUaMOasGHHCfgE1" alt=""><figcaption></figcaption></figure>

Open the console using **Actions → Console**. When the VM has booted into BIOS, select **EFI VMware Virtual IDE CDROM Drive** and press <kbd>Enter</kbd>.

<figure><img src="/files/3GzNeETxdsdsx9BG9yRH" alt=""><figcaption></figcaption></figure>

You'll then be presented with a text saying *Press any key to boot from CD or DVD*. Press any key here to boot from the virtual CD-ROM (ISO file).

Windows Server Setup will then start. Click **Next** when asked to select a language, and then again if asked to select a keyboard setting.

<figure><img src="/files/WKoSF4oS73iiSfHnZqjH" alt=""><figcaption></figcaption></figure>

At the *Select setup option* screen, select **Repair my PC**, and click **Next**.

<figure><img src="/files/qe7qVfdzl6ODdCsTUxfM" alt=""><figcaption></figcaption></figure>

The *Windows Recovery Environment* will now start. You might be asked to select a keyboard layout as the first question in the Windows Recovery Environment. It's safest to select a US keyboard layout here to match VMware.
{% endtab %}
{% endtabs %}

Next, click **Troubleshoot**.

<figure><img src="/files/NusjmCJVgqNVGurdUd5u" alt=""><figcaption></figcaption></figure>

On the next screen, click **Advanced options**.

<figure><img src="/files/T0GBZWMCcAmACWG7xiwe" alt=""><figcaption></figcaption></figure>

On the last screen, click **Command Prompt**.

<figure><img src="/files/rTmBzEqhjKgfJiVQA2fx" alt=""><figcaption></figcaption></figure>

A command prompt will now start.

When the command prompt is first started, it's in `X:\Windows\System32`, the Recovery Environment. Change to the C-drive by typing `C:`. The prompt will change to `C:\>`.

{% code title="Command" %}

```
C:
```

{% endcode %}

Then, change the directory to `Windows/System32` by typing:

{% code title="Command" %}

```
cd Windows/System32
```

{% endcode %}

The prompt should now read `C:\Windows\System32>`.

You are now going to replace the Windows accessibility tool with a command prompt. First, rename the original file (`utilman.exe`) using the following command (so that you can change it back once you have reset your password):

{% code title="Command" %}

```
rename utilman.exe utilman.exe.bak
```

{% endcode %}

Make a copy of `cmd.exe` to `utilman.exe`, effectively replacing the accessibility tool with a command prompt:

{% code title="Command" %}

```
copy cmd.exe utilman.exe
```

{% endcode %}

Type `exit` and press <kbd>Enter</kbd> to exit from the command prompt.

<figure><img src="/files/xDhA3C21Yy4cFRnZhOx0" alt=""><figcaption></figcaption></figure>

Once you exit the command prompt, you'll go back to the Windows Recovery Environment. Click **Continue** to boot the server as normal.

<figure><img src="/files/8llS2LBpbw7N4VecyOHD" alt=""><figcaption></figcaption></figure>

When the server has booted, you are presented with the login screen.&#x20;

{% tabs %}
{% tab title="KVM/VMware" %}
Click **Send Ctrl-Alt-Del** at the top of the console to unlock the screen.
{% endtab %}

{% tab title="Dedicated server" %}
Click **Macro → Macro → Ctrl+Alt+Del** in the console menu to unlock the screen.
{% endtab %}
{% endtabs %}

Click the **accessibility** icon in the lower right corner. This will launch a command prompt as the SYSTEM account, since you have replaced the accessibility tool with it.

<figure><img src="/files/BaBmY8r4e4rbj5IpIvnk" alt=""><figcaption></figcaption></figure>

You can now reset your password using the command prompt. In the example below, the username is *glesys*, and *myNewPassword123* is the new password for that user.

```
net user glesys myNewPassword123
```

Once you have executed the above command, exit from the command prompt using `exit`.

<figure><img src="/files/JG4WCheifZo3meZXoe2T" alt=""><figcaption></figcaption></figure>

You can now use your new password to log in to Windows.

## Revert the changes made to the system

Once you have logged in to Windows successfully through the console, you must put the original `utilman.exe` back into place, or the server will be insecure.

While still logged in through the console, click the start menu, search for ***startup options***, and then click **Change advanced startup options**.

<figure><img src="/files/DfnExPjPwhIYEy4dkjoG" alt=""><figcaption></figcaption></figure>

In the window that opens, click the **Restart now** button to restart the server. A dialog box will appear, asking you to confirm that you want to restart. Click **Restart now**.

<figure><img src="/files/t4nIcdzpaSWRJithk6Pf" alt=""><figcaption></figcaption></figure>

The server will now reboot to the Windows Recovery Environment, and you'll be presented with the following screen.

<figure><img src="/files/dCIzZQ3RIW9FIbgEXNT5" alt=""><figcaption></figcaption></figure>

Click **Troubleshoot → Advanced options → Command prompt** to open a command prompt. It's the same steps you took before. If the server was installed from an ISO file, you might need to enter your new password to open the command prompt.

In the command prompt, change to the C-drive by typing `C:` .

{% code title="Command" %}

```
C:
```

{% endcode %}

Then, change the directory to `Windows/System32`:

{% code title="Command" %}

```
cd Windows/System32
```

{% endcode %}

The prompt should now read `C:\Windows\System32>`. Revert the changes made earlier by executing the following commands:

{% code title="Multiple commands" %}

```
del utilman.exe
rename utilman.exe.bak utilman.exe
```

{% endcode %}

Finally, type `exit` to exit the command prompt.

<figure><img src="/files/jsgVpJxU2TAEz2N0AyWF" alt=""><figcaption></figcaption></figure>

When you see the options for the Recovery Environment, click **Continue** to boot the server as normal.

<figure><img src="/files/vEa2pYEf1CiHecfxKeBt" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="KVM/VMware" %}
When the system has booted to the login screen, click **Send Ctrl-Alt-Del** in the console to unlock it.
{% endtab %}

{% tab title="Dedicated server" %}
When the system has booted to the login screen, click **Macro → Macro → Ctrl+Alt+Del** in the console menu to unlock it.
{% endtab %}
{% endtabs %}

Now, click the **accessibility** icon to make sure the accessibility tool starts. No command prompt should start this time. The system is now back to normal.

<figure><img src="/files/1Jc3L1Y5plXwLonfkzJs" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glesys.com/products/compute/guides-for-server-management/reset-your-password-in-windows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.