{"id":877,"date":"2026-10-19T18:00:00","date_gmt":"2026-10-19T18:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=877"},"modified":"2026-10-19T18:00:00","modified_gmt":"2026-10-19T18:00:00","slug":"update-windows-disk-info","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/10\/19\/update-windows-disk-info\/","title":{"rendered":"How to Update Windows Disk Info After a VPS Resize"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To update Windows disk info after a VPS resize, rescan the virtual disk and extend the correct volume with DiskPart. The process usually takes a few minutes and lets Windows report the added capacity without reinstalling the operating system.<\/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 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025, Windows 10, or Windows 11.<\/li>\n\n\n<li>An active RDP session, VPS console, or local console with a local administrator account.<\/li>\n\n\n<li>Extra disk capacity already added to the same virtual disk in your provider&#8217;s control panel. This guide does not create storage that has not been assigned to the VPS.<\/li>\n\n\n<li>A backup or VPS snapshot taken before changing a production disk, especially when working on the system volume.<\/li>\n\n\n<li>If you need a Windows environment for this task, <a href=\"https:\/\/vpslake.com\/buy-windows-rdp\">VPSLake Windows RDP hosting<\/a> provides a remote Windows server with administrator access.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm that the VPS disk was expanded<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Windows can only use capacity that the virtual disk already exposes, so check the VPS control panel before changing partitions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open the VPSLake client area at <code>https:\/\/my.vpslake.com<\/code>, open the relevant service, and launch the <strong>VPS control panel (Virtualizor)<\/strong>. Confirm that the disk resize or storage change has completed. If the panel still shows the old disk size, wait for that operation to finish or contact support; DiskPart cannot add capacity that the hypervisor has not presented.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After the provider-side resize, connect to Windows over RDP or the VPS console. Open <strong>Start \u2192 Windows Administrative Tools \u2192 Computer Management \u2192 Storage \u2192 Disk Management<\/strong>. The disk should show the new total size with unallocated space after the existing partition. Do not initialize, format, or delete a disk that already contains your Windows installation or data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If Disk Management still shows the previous size, right-click the disk area and choose <strong>Rescan Disks<\/strong>. You can also perform the rescan from DiskPart in the next step.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Open DiskPart with administrator rights<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DiskPart changes partition metadata, so an elevated command window is required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open <strong>Start<\/strong>, search for <code>Command Prompt<\/code>, right-click it, and select <strong>Run as administrator<\/strong>. Then enter:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>diskpart\nrescan\nlist disk\nlist volume<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>rescan<\/code> command asks Windows to discover the new disk geometry. <code>list disk<\/code> lets you compare the disk size, while <code>list volume<\/code> displays the drive letters and current volume sizes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The output will differ on each server, but the target should be identifiable by its drive letter and expected size:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>DISKPART&gt; list volume\n\n  Volume ###  Ltr  Label       Fs     Type        Size     Status     Info\n  ----------  ---  ----------  -----  ----------  -------  ---------  ---------\n  Volume 0     C               NTFS   Partition    80 GB  Healthy    Boot\n  Volume 1     D     DATA      NTFS   Partition   200 GB  Healthy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not choose a volume only because it is the largest one. The EFI, recovery, reserved, or data volume may be larger than the partition you actually intend to grow.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Inspect and select the target volume<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Selecting the volume by its drive letter and checking its details reduces the chance of modifying the wrong partition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>C<\/code> below with the drive letter that should receive the new space:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>select volume=C\ndetail volume<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">DiskPart accepts a drive letter for <code>select volume<\/code>; if your environment requires the volume number instead, use the number shown by <code>list volume<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>select volume=0\ndetail volume<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Check that <code>detail volume<\/code> shows the expected drive letter, NTFS filesystem, and disk. A normal selection looks similar to this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>DISKPART&gt; detail volume\n  Disk ###  Status         Size     Free     Dyn  Gpt\n  --------  -------------  -------  -------  ---  ---\n  Disk 0    Online          300 GB  220 GB\n\n  Volume 0   Ltr C   Label       Fs     Type        Size     Status     Info\n  ----------  --- --- ---------- -----  ----------  -------  ---------  ---------\n  Volume 0       C              NTFS   Partition     80 GB  Healthy    Boot<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the free space is not on the same disk or does not immediately follow this volume, stop before running an extension command. Windows cannot move an intervening partition with DiskPart.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Extend the volume and filesystem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The standard <code>extend<\/code> command grows the selected volume into contiguous unallocated space and, for NTFS, normally grows the filesystem with it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With the correct volume selected, run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>extend<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For a successful operation, DiskPart reports:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>DiskPart successfully extended the volume.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to add only part of the available space, specify the amount in megabytes. For example, this adds 50 GB rather than consuming all contiguous free space:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>extend size=51200<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not use the <code>size<\/code> form unless you have deliberately calculated how much capacity to leave unallocated. On a basic disk, the available space must be immediately after the selected partition. Microsoft documents the command syntax and those layout requirements in its <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/administration\/windows-commands\/extend\" target=\"_blank\" rel=\"noopener\">DiskPart extend command reference<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the partition has already been extended but Windows still reports the old filesystem size, keep the same volume selected and run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>extend filesystem<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That form is specifically for extending a filesystem after the underlying volume was enlarged separately. It is not a substitute for adding unallocated space to the partition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When finished, leave DiskPart:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>exit<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the updated disk information<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Verification confirms that both the partition and the filesystem now expose the added capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Open an elevated PowerShell window and run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-Volume -DriveLetter C | Format-Table DriveLetter,FileSystem,HealthStatus,Size,SizeRemaining\nGet-Partition -DriveLetter C | Format-Table DiskNumber,PartitionNumber,DriveLetter,Size<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Change <code>C<\/code> to the target drive letter. The result should show a larger <code>Size<\/code>, a healthy volume, and the expected filesystem:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>DriveLetter FileSystem HealthStatus         Size SizeRemaining\n----------- ---------- ------------         ---- -------------\nC           NTFS       Healthy      300000000000 220000000000<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also reopen <strong>Computer Management \u2192 Storage \u2192 Disk Management<\/strong> and confirm that the former black <strong>Unallocated<\/strong> region has been absorbed by the selected volume. If the volume hosts a database, backup repository, or application, check its own storage display as well.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Need more disk space?\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Windows VPS storage<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Need more disk space?<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Get a Windows VPS with administrator access for storage-heavy workloads and server management.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-windows-rdp\" aria-label=\"View Windows VPS\">View Windows VPS<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">\u201cThe volume cannot be extended\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The selected volume may not be NTFS, or the unallocated space may be separated from it by another partition. Run <code>detail volume<\/code>, then inspect the order in <strong>Disk Management<\/strong>. On a basic disk, the free area must be on the same disk and immediately after the target volume.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>extend<\/code> reports that there is not enough usable free space<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Windows may not have detected the provider-side resize yet, or the free space may belong to another disk. Run <code>rescan<\/code> in DiskPart and compare <code>list disk<\/code> with the new size shown in the VPS control panel. If the disk remains unchanged, do not initialize it; resolve the virtual-disk resize first.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u201cExtend Volume\u201d is unavailable in Disk Management<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The unallocated area is probably not adjacent to the selected volume, or you selected a recovery or reserved partition. Do not delete a recovery partition just to make the option available. Back up the server and plan a supported partition move or use a separate volume instead.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Windows still shows the old capacity after a successful extension<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Refresh Disk Management and run <code>Get-Volume<\/code> again. If the partition size increased but the filesystem did not, select the correct volume in DiskPart and run <code>extend filesystem<\/code>; if both values are unchanged, you likely extended a different volume or are viewing a stale application cache.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening after the resize<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Keep the backup or snapshot until the enlarged volume has passed a normal read and write test.<\/li>\n\n\n<li>Leave EFI, Microsoft Reserved, and recovery partitions untouched.<\/li>\n\n\n<li>Set a free-space alert so the next capacity issue is found before applications stop writing.<\/li>\n\n\n<li>If BitLocker is enabled, keep the recovery key available and confirm its protection status after storage maintenance.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does updating Windows disk info delete my files?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The built-in DiskPart extension is designed to enlarge the selected volume while preserving its existing data. A current backup is still important because a wrong volume selection, storage fault, or interrupted provider-side operation can create a separate recovery problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I extend the C: drive while Windows is running?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Usually, yes. NTFS volumes can generally be extended online when contiguous unallocated space is available, so a reboot is not normally required. The provider-side virtual-disk resize may have separate maintenance requirements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why is the disk larger but the C: drive unchanged?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The virtual disk and the partition are different layers. Windows may see a larger disk while the C: partition still ends at its old boundary; selecting the correct volume and running <code>extend<\/code> connects the adjacent unallocated space to that partition.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is <code>extend filesystem<\/code> the same as <code>extend<\/code>?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. <code>extend<\/code> grows the selected partition or volume into unallocated space, while <code>extend filesystem<\/code> updates a filesystem after its underlying volume has already been enlarged. Use the latter only when the partition is already larger but the filesystem still reports the old size.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does updating Windows disk info delete my files?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The built-in DiskPart extension is designed to enlarge the selected volume while preserving its existing data. A current backup is still important because a wrong volume selection, storage fault, or interrupted provider-side operation can create a separate recovery problem.\"}}, {\"@type\": \"Question\", \"name\": \"Can I extend the C: drive while Windows is running?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Usually, yes. NTFS volumes can generally be extended online when contiguous unallocated space is available, so a reboot is not normally required. The provider-side virtual-disk resize may have separate maintenance requirements.\"}}, {\"@type\": \"Question\", \"name\": \"Why is the disk larger but the C: drive unchanged?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The virtual disk and the partition are different layers. Windows may see a larger disk while the C: partition still ends at its old boundary; selecting the correct volume and running `extend` connects the adjacent unallocated space to that partition.\"}}, {\"@type\": \"Question\", \"name\": \"Is `extend filesystem` the same as `extend`?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. `extend` grows the selected partition or volume into unallocated space, while `extend filesystem` updates a filesystem after its underlying volume has already been enlarged. Use the latter only when the partition is already larger but the filesystem still reports the old size.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Update Windows disk info after a VPS resize with DiskPart, verify the new capacity, and fix the errors that prevent a volume from expanding.","protected":false},"author":1,"featured_media":878,"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":[54,89,68,42],"class_list":["post-877","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-windows-server","tag-disk-management","tag-diskpart","tag-vps","tag-windows-server","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/877","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=877"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/877\/revisions"}],"predecessor-version":[{"id":3646,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/877\/revisions\/3646"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/878"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=877"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=877"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}