Problem: Windows Installer Does Not Detect Unallocated Disk Space During Dual-Boot Setup

Minh Nguyen 0 Reputation points
2026-09-17T00:04:46.9333333+00:00

I am trying to set up a dual-boot system with Windows and Linux on my laptop. I am currently using a Dell Inspiron 15 3530 with a 1 TB drive.

I have already partitioned my drive and freed approximately 200 GB of space for a Windows installation. The space is currently intended to be used exclusively by Windows, while the remaining storage is used for my existing Linux installation.

However, when I boot from a Windows installation USB drive and reach the disk/partition selection screen during the Windows installation process, the installer does not recognize or display the approximately 200 GB of free space that I previously allocated for Windows.

Selected image presented in a lightbox.

I encountered a similar issue in the past, and a specialist was able to resolve it, but I did not determine exactly what was causing the problem or what changes were made to fix it. I would now like to understand the underlying cause and, if possible, resolve the issue myself rather than relying on someone else.

I would appreciate help determining:

Why the Windows installer is unable to detect the available 200 GB of space.

Whether the issue is related to the partition table (GPT/MBR), filesystem, existing Linux partitions, or the drive configuration.

Whether UEFI/BIOS settings or storage-controller settings (such as AHCI/RAID/VMD) could be causing the problem.

How I can safely diagnose the current disk configuration without accidentally deleting or modifying my existing Linux installation.

What steps I should follow to make the unused space available to the Windows installer.

I would also be happy to provide screenshots or outputs from tools such as GParted, lsblk, fdisk -l, or parted -l, as well as information about my current BIOS/UEFI configuration, if that would help diagnose the problem.

Hardware: Dell Inspiron 15 3530 Drive capacity: 1 TB Existing OS: Linux Space intended for Windows: ~200 GB Installation method: Windows bootable USB (UEFI)

I am specifically looking for a way to identify the root cause before making any changes, since I want to avoid accidentally damaging my existing Linux installation or losing data.

Windows for home | Windows 11 | Install and upgrade

4 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Igor Leyko 112.4K Reputation points Independent Advisor
    2026-09-18T15:53:52.9066667+00:00

    Make this partition active and see if this helps.

    Was this answer helpful?

    0 comments
  2. Igor Leyko 112.4K Reputation points Independent Advisor
    2026-09-17T13:15:49.38+00:00

    You are using Linux tools, they may not explain why Windows does not see the unallocated space.

    Please boot Recovery environment, run command prompt, run diskpart tool and check if it is possible to create NTFS partition.

    Was this answer helpful?

  3. Igor Leyko 112.4K Reputation points Independent Advisor
    2026-09-17T00:43:44.57+00:00

    Could it be that you have active partition on this drive already and this partition is Linux-style formatted?

    Please show a result of list disk command result mentioned in the previous answer.

    Was this answer helpful?

  4. AI answer

    2026-09-17T00:05:15.29+00:00

    The screenshot indicates that Windows Setup is not seeing the storage controller correctly, not just missing one partition. When Setup opens "Install driver to show hardware", the usual cause is that the disk itself is not currently accessible to the installer.

    Most likely causes supported by the available guidance:

    1. Storage controller driver is missing This is common when the system uses Intel Rapid Storage Technology drivers. In that case, Windows Setup may show no internal drive or ask to load a driver.
    2. UEFI/GPT mismatch is less likely to be the immediate issue GPT vs MBR matters for installation, especially in UEFI mode, but if the whole internal disk is not visible, the first issue to resolve is storage detection.
    3. Disk numbering can be misleading If multiple drives or USB devices are attached, Windows Setup disk numbers may not match physical expectations. This matters if using DiskPart so the wrong disk is not modified.

    Safe diagnosis path that avoids changing the Linux installation:

    1. Disconnect unnecessary external storage Leave only the Windows installation USB connected. This reduces confusion from extra USB disks appearing in Setup.
    2. At the Windows Setup screen, press Shift+F10 Open Command Prompt, then run: 
         diskpart
   list disk
      • If the internal 1 TB disk does not appear, Windows Setup is not detecting the storage controller properly.
      • If the internal disk does appear, then the issue is with partition visibility or allocation, not total disk detection.
    3. Do not run clean, convert gpt, or delete partitions Those actions are destructive and can remove the Linux installation. Only use list disk for identification unless a full wipe is intended.
    4. Verify the target disk carefully Microsoft notes that disk numbers during Setup may not correspond to SATA or RAID channel numbering. Check size and any visible volume information before selecting a disk.

    What to do if the internal disk does not appear:

    1. Load the storage driver in Windows Setup The accepted guidance for similar cases is to download the Intel Rapid Storage Technology driver from the PC manufacturer, extract it to a USB drive, then in Windows Setup select Load driver and browse to that folder.
    2. After the driver loads, the internal disk and partitions should appear At that point, the 200 GB area should be visible if it is truly unallocated space.

    What to do if the internal disk appears but the 200 GB does not:

    1. The space may not actually be unallocated in a way Windows Setup recognizes.
    2. The partition layout may need to be reviewed from Linux first using non-destructive tools before making changes.
    3. Since the system is being booted in UEFI mode, Windows installation should use GPT on the target disk.

    Important cautions:

    • Do not delete partitions unless a full reinstall is intended. Microsoft’s documented delete-and-install process wipes the selected drive layout.
    • Do not use clean or convert gpt on the disk containing Linux unless the goal is to erase it.
    • If the disk is larger than 2.2 TB, GPT is required to use full capacity, but with a 1 TB drive this is not the main issue.

    Root-cause summary based on the screenshot and available guidance:

    • The immediate problem is most consistent with a missing storage controller driver, especially Intel RST/RAID-type storage handling.
    • GPT/MBR and free-space layout become relevant only after the installer can actually see the internal disk.
    • The safest first check is Shift+F10 → diskpart → list disk, with no write operations.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.