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

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.

• Windows Setup: Installing using the MBR or GPT partition style
• Disk drive numbers may not correspond to the SATA channel numbers when you install Windows on a computer that has multiple SATA or RAID disks
• Windows installation issue - Microsoft Q&A
• Problems with creating a partition from a fully formatted drive - Microsoft Q&A