{"id":861,"date":"2026-10-17T18:00:00","date_gmt":"2026-10-17T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=861"},"modified":"2026-10-17T18:00:00","modified_gmt":"2026-10-17T18:00:00","slug":"reset-password-windows-server-2022","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/10\/17\/reset-password-windows-server-2022\/","title":{"rendered":"How to Reset Password on Windows Server 2022"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To reset password on Windows Server 2022 when RDP no longer accepts the old credential, use the VPS console and Windows installation media to recover the local account. The process usually takes 10\u201320 minutes, including a required cleanup pass that restores the accessibility executable before you return the server to normal boot.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Windows Server 2022, with the system disk attached through a VirtIO storage controller or another virtual storage controller.<\/li>\n\n\n<li>Access to the <a href=\"https:\/\/my.vpslake.com\" target=\"_blank\" rel=\"noopener\">VPSLake client area<\/a>, the VPS control panel (Virtualizor), and its VNC console. You need permission to power-cycle the server and mount or eject virtual media.<\/li>\n\n\n<li>A Windows Server 2022 installation ISO and, if the disk is not visible in recovery, a VirtIO driver ISO supplied through your virtualization setup.<\/li>\n\n\n<li>A local administrator account to recover. This method does not reset a Microsoft account or an Active Directory domain password.<\/li>\n\n\n<li>A safe place to create a strong replacement password. Use a long unique value; do not put it in the command line or paste it into a ticket.<\/li>\n\n\n<li>A Windows VPS with administrator access, such as <a href=\"https:\/\/vpslake.com\/buy-windows-rdp\">VPSLake Windows RDP hosting<\/a>, if you need a server for this recovery procedure.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Boot Windows Server 2022 into recovery<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Windows Recovery Environment gives you a command prompt before the installed system signs in, which is necessary when the normal desktop is unavailable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open the server in the VPS control panel and launch its VNC console. Attach the Windows Server 2022 ISO to the virtual CD\/DVD drive, reboot the VPS, and choose the virtual CD\/DVD device if the panel shows a boot-device prompt. On the setup screen, select the language and keyboard layout, then choose <strong>Next \u2192 Repair your computer \u2192 Troubleshoot \u2192 Command Prompt<\/strong>. Microsoft documents this installation-media route in its <a href=\"https:\/\/learn.microsoft.com\/en-us\/troubleshoot\/windows-server\/performance\/use-winre-to-troubleshoot-startup-issue\" target=\"_blank\" rel=\"noopener\">WinRE troubleshooting guide<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You are now in a temporary recovery environment, so drive letters can differ from those used during a normal boot. If the command prompt opens on <code>X:<\/code>, that is the recovery image, not your Windows installation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Load the storage driver and identify Windows<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WinRE cannot edit the account database until it can see the installed Windows volume.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If <code>diskpart<\/code> does not show the VPS disk, use the control panel to eject the Windows ISO and attach the VirtIO driver ISO without closing the VNC window. Identify the driver disc letter by checking its contents:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dir D:\\\ndir D:\\viostor \/ad<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For a current driver ISO, load the Windows Server 2022 x64 storage driver from the matching folder. The common path is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>drvload D:\\viostor\\2k22\\amd64\\viostor.inf<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the ISO uses a different Windows-compatible folder name, use the <code>viostor.inf<\/code> file inside its <code>viostor<\/code> directory. A successful load reports that the driver was added; then eject the driver ISO and reattach the Windows installation ISO.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">List the volumes and leave DiskPart:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>diskpart\nlist volume\nexit<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Look for the large NTFS volume containing the <code>Windows<\/code> directory. Confirm the candidate rather than assuming it is <code>C:<\/code> or <code>E:<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dir C:\\Windows\\System32\ndir D:\\Windows\\System32\ndir E:\\Windows\\System32<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The correct result contains files such as <code>cmd.exe<\/code> and <code>utilman.exe<\/code>. In the commands below, replace <code>WINDOWS_DRIVE<\/code> with that drive letter, without the trailing placeholder text\u2014for example, <code>E:<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Temporarily open an elevated recovery command<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Replacing the accessibility executable lets the sign-in screen start a SYSTEM-level command prompt once; use it only on a server you own or are authorized to administer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Change to the installed system directory and make a backup before copying the command interpreter into its place. If <code>utilman.exe.bak<\/code> already exists, stop and use the cleanup step to restore it; do not delete an existing backup.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>WINDOWS_DRIVE:\ncd Windows\\System32\nren utilman.exe utilman.exe.bak\ncopy cmd.exe utilman.exe<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The last command should report that one file was copied. If <code>ren<\/code> reports that <code>utilman.exe<\/code> is missing, stop and recheck the drive letter; do not continue against a different volume.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Close Command Prompt, select <strong>Continue<\/strong> to boot from the internal disk, and eject the Windows ISO or set the VPS to boot from its virtual disk. At the Windows sign-in screen, select the <strong>Ease of access<\/strong> button. A command prompt should open instead of the accessibility panel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Set a new local account password<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Using <code>net user<\/code> with an asterisk keeps the replacement password out of command history and out of the visible console.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">First list local accounts so you use the exact name, then reset the intended account interactively:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net user\nnet user YOUR_LOCAL_USERNAME *<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>YOUR_LOCAL_USERNAME<\/code> with the local account name shown by the first command. Type the new password twice when prompted. A successful result is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Type a password for the user:\nRetype the password to confirm:\nThe command completed successfully.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the built-in account is disabled, enable it before setting its password:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net user Administrator \/active:yes\nnet user Administrator *<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This works for a local account on the installed server. The <code>\/domain<\/code> option is intentionally not used: a domain account must be reset through the domain controller or its approved administration process. See Microsoft\u2019s <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/administration\/windows-commands\/net-user\" target=\"_blank\" rel=\"noopener\"><code>net user<\/code> reference<\/a> for the command\u2019s supported syntax.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Restore the accessibility file<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Leaving the replacement in place would give anyone who reaches the sign-in screen an elevated command prompt, so restore the original file immediately after the reset.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From the temporary command prompt, reboot into the Windows ISO again and open <strong>Repair your computer \u2192 Troubleshoot \u2192 Command Prompt<\/strong>. Load the VirtIO driver again if the Windows volume is absent, identify the system drive as in Step 2, and run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>WINDOWS_DRIVE:\ncd Windows\\System32\ndel utilman.exe\nren utilman.exe.bak utilman.exe<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>ren<\/code> command should complete without an error. Verify that both the restored file and the backup are in the expected state:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dir utilman.exe\nif exist utilman.exe.bak echo BACKUP_STILL_PRESENT<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The listing should show <code>utilman.exe<\/code>; <code>BACKUP_STILL_PRESENT<\/code> should not appear. Eject the ISO, set the VPS to boot from its virtual disk, and choose <strong>Continue<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the new Windows Server 2022 password<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A successful <code>net user<\/code> message proves only that Windows accepted the local change; a fresh sign-in proves that the complete recovery worked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At the normal sign-in screen, select the account you changed and sign in with the new password. Then test a new RDP connection while keeping the VNC session available. For a local account, use <code>SERVER_NAME\\YOUR_LOCAL_USERNAME<\/code> or <code>.\\YOUR_LOCAL_USERNAME<\/code> as the username format; do not use a domain prefix unless this is a domain account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After signing in, open <strong>Start \u2192 Windows Tools \u2192 Computer Management \u2192 Local Users and Groups \u2192 Users<\/strong>, or run the following from an elevated terminal:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net user YOUR_LOCAL_USERNAME<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The account should show <code>Account active Yes<\/code> and a recent <code>Password last set<\/code> value:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Account active               Yes\nPassword last set            &lt;recent date and time&gt;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Finally, press <code>Windows key + L<\/code> and confirm that the <strong>Ease of access<\/strong> control opens the normal accessibility options, not Command Prompt. That check confirms the temporary recovery change was removed.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Need a Windows VPS?\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Windows server recovery<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Need a Windows VPS?<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Get administrator-ready Windows hosting with console access for remote recovery and management.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-windows-rdp\" aria-label=\"View Windows RDP\">View Windows RDP<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">The Windows volume does not appear in <code>list volume<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">WinRE is missing the VirtIO storage driver, or the driver ISO is not actually attached. Mount the driver ISO in Virtualizor, inspect the <code>viostor<\/code> directory, run <code>drvload<\/code> against the matching <code>amd64\\viostor.inf<\/code>, and then repeat <code>diskpart<\/code> \u2192 <code>list volume<\/code>. Do not format or initialize a disk from this environment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>ren utilman.exe utilman.exe.bak<\/code> says the file is not found<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You are probably working on <code>X:<\/code> or another recovery volume instead of the installed Windows volume. Test each candidate drive with <code>dir DRIVE:\\Windows\\System32\\utilman.exe<\/code>, then use the one that returns the file; if none does, stop and investigate the disk or driver state.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The Ease of access button still opens accessibility tools<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The replacement was not copied to the installed system directory, or the server booted from the ISO again. Recheck the drive letter, confirm <code>copy cmd.exe utilman.exe<\/code> reported one file copied, eject the ISO, and boot from the virtual disk. Do not repeat the reset until the correct volume is confirmed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>net user<\/code> cannot find the account<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The account name may be misspelled, localized, or a domain identity rather than a local user. Run <code>net user<\/code> by itself and use the exact local name; for a domain account, contact the domain administrator instead of changing files offline.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening after recovery<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Keep the replacement password in a password manager and remove it from temporary notes or clipboard history.<\/li>\n\n\n<li>Restrict RDP to trusted source addresses or a VPN, and avoid exposing the built-in Administrator account unnecessarily.<\/li>\n\n\n<li>Take a provider-level backup or snapshot after confirming the server boots normally, then remove any temporary ISO attachments.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I reset a Windows Server 2022 domain password this way?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The offline <code>net user<\/code> command targets local accounts in the installed server. Domain credentials are managed by Active Directory and should be reset through the domain controller or the organization\u2019s approved identity-management workflow.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do I need the VirtIO driver ISO on every VPS?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. You need it only when WinRE cannot see a disk attached through VirtIO. If <code>diskpart<\/code> already lists the Windows volume and you can find its <code>Windows\\System32<\/code> directory, continue without loading a driver.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Will resetting the password disconnect existing RDP sessions?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not necessarily. Existing sessions can remain active, but every new authentication uses the new password. Keep the VNC console available until a fresh RDP connection succeeds and the accessibility file has been restored.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What if I cannot mount an ISO or open VNC?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The offline method depends on console and virtual-media access. Use another authorized local administrator if one exists, or open a support ticket through the VPSLake client area; do not use an untrusted password-bypass utility.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I reset a Windows Server 2022 domain password this way?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The offline `net user` command targets local accounts in the installed server. Domain credentials are managed by Active Directory and should be reset through the domain controller or the organization\u2019s approved identity-management workflow.\"}}, {\"@type\": \"Question\", \"name\": \"Do I need the VirtIO driver ISO on every VPS?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. You need it only when WinRE cannot see a disk attached through VirtIO. If `diskpart` already lists the Windows volume and you can find its `Windows\\\\System32` directory, continue without loading a driver.\"}}, {\"@type\": \"Question\", \"name\": \"Will resetting the password disconnect existing RDP sessions?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not necessarily. Existing sessions can remain active, but every new authentication uses the new password. Keep the VNC console available until a fresh RDP connection succeeds and the accessibility file has been restored.\"}}, {\"@type\": \"Question\", \"name\": \"What if I cannot mount an ISO or open VNC?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The offline method depends on console and virtual-media access. Use another authorized local administrator if one exists, or open a support ticket through the VPSLake client area; do not use an untrusted password-bypass utility.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Learn how to reset password on Windows Server 2022 from the VPS console, recover a local Administrator account, restore system files, and verify RDP access.","protected":false},"author":1,"featured_media":862,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,11],"tags":[84,32,85,52],"class_list":["post-861","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-windows-server","tag-password-reset","tag-rdp","tag-virtualizor","tag-windows-server-2022","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/861","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=861"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/861\/revisions"}],"predecessor-version":[{"id":3553,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/861\/revisions\/3553"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/862"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}