Windows 11 Win11 Home 24h2 not recognizing external drive partitions

[Zevik83]

Have a 2TB Seagate, passed OK by Seagate Tools, partitioned D: Recovery 32G Fat for older 23h2 laptop E: for its System Image Recovery. Rest is partitioned in 256G volumes recognized as Drives in File Explorer. Wanted to set up File History for another laptop on Drive J. Win says drive not recognized and this is the same result for many other volumes H through J. G: is my Google drive, so not available.

 

[ChatGPT]

Good — thanks for the clear status. Short version: File History won’t accept a volume when Windows can’t treat it as a normal, unlocked, local NTFS backup target. The fix is to check a few things (format, drive type/health, drive letter, BitLocker, dynamic disk) and then either convert/repair the partition or point File History at a folder on the NTFS partition. Below are targeted checks and exact commands you can run; paste the outputs if you want me to read them and give the exact next step.
Why this happens (brief)

• File History needs a local, accessible backup target. If Windows can’t access the partition as a normal NTFS volume (no letter, different format, locked by BitLocker, treated as removable, dynamic/offline, or otherwise unhealthy) it reports “drive not recognized” or refuses to use it. This is a common cause of File History disconnects.
• Windows has historically behaved oddly with multi‑partition external devices and with removable‑flagged USBs; some partitions may be visible in Explorer but not usable by backup services. Checking Disk Management and the partition type fixes most cases.

Quick checklist — try these in order

1. Confirm the drive/partition is healthy and visible

• Open Disk Management (Win+X → Disk Management). Confirm the target partition (J:, H: or I shows: file system (NTFS?, status = Healthy, and a drive letter is assigned.
• If a volume shows No Drive Letter, right‑click → Change Drive Letter and Paths → Add → pick a letter (J or any unused). Many File History problems are just missing letters.

1. Check the file system

• File History expects an NTFS destination for best results. In Disk Management or File Explorer right‑click the volume → Properties → File system.
• If it’s FAT32 or exFAT convert it to NTFS (non‑destructive) with: open Admin Command Prompt and run:
  convert J: /fs:ntfs
  (replace J: with the correct drive letter). If convert won’t work or you prefer a clean start, back up data and reformat as NTFS.

1. Make sure the volume isn’t BitLocker‑locked or offline

• If BitLocker is enabled, unlock or suspend it before using the drive for File History. File History can’t write to a locked volume.
• In Disk Management, the volume should be Online and not marked Read‑Only.

1. Confirm disk is Basic (not Dynamic) and the partition type is standard

• In Disk Management the disk should be a Basic disk. File History can misbehave with Dynamic disks or weird partition configurations. If the disk is Dynamic consider converting to Basic (requires data move/backup).

1. Check whether Windows treats the external device as “removable”

• Some USB enclosures/drives report as removable and Windows can be picky about multiple partitions/backup use. If you suspect this (odd behavior or only first partition works), use a different external enclosure or use a small dedicated USB for rescue and the 2 TB drive as the image/backup target. (This is a known real‑world quirk with multi‑partition externals.

1. Re‑point File History after corrections

• Settings → Backup → “Back up using File History” (or Control Panel → File History) → Add a drive → choose the partition (or click “More options” → “See advanced settings” → “Select drive”). If the drive still doesn’t appear, File History will let you browse to a folder on the NTFS partition from the restore environment — but it’s best to fix the partition first.

Commands you can paste here (I can read the output and advise)

• Open an elevated Command Prompt and run these two commands and paste the output:
  diskpart
  list disk
  list volume
  exit
• Also, in PowerShell (Admin) run:
  Get-Volume | Format-Table DriveLetter,FileSystem,HealthStatus,SizeRemaining,Size -Auto

What I’ll look for in your outputs

• Whether the J: (and H:, I volumes are NTFS, Online, and Healthy.
• Whether the disk is reported as Basic or Dynamic and whether Windows shows the device as Removable.
• Any mismatch between Explorer letters and Disk Management.

If these quick checks don’t show the problem

• Tell me the exact error message Windows shows when you try to “Add a drive” for File History (copy the text). That helps narrow to permissions vs format vs drive type.
• If you prefer, take a screenshot of Disk Management and attach it.

If you want, next step I can do for you

• Tell me the diskpart list disk + list volume output (paste here) and I’ll give the precise action (assign letter, convert to NTFS, remove read‑only, or suggest reformat steps) with the exact commands to copy/paste. That will fix the J: issue so File History accepts it.

Reference: common File History causes & fixes (for context). . Also see discussion about multi‑partition external quirks and GPT/MBR issues if you ever merge partitions or rebuild the external.
Ready when you are — paste the diskpart list output or a Disk Management screenshot and I’ll give the exact command(s) to fix J: so File History recognizes it.

 

[Zevik83]

BitLocker is disenabled. Disk Manager reports the drives I am interested in using H - M with appropriate drive letter, Simple Layout, Basic Type, NTFS File System,. Healthy Lpgical Drive. Status.

Disk 1 is Basic.

Where you I find out that Win sees iot as Removable?

 

[ChatGPT]

Good — since Disk Management already shows those volumes as Basic / NTFS / Healthy, the next thing to check is whether Windows is treating the physical external device as “removable.” If it’s reported removable (USB bus) some Windows backup services and multi‑partition behavior can be flaky and File History may refuse certain partitions. Here are quick checks you can run and what to do next.
How to check whether Windows treats the disk as removable
1) Quick PowerShell check (recommended — admin PowerShell)

• Open PowerShell as Administrator and run:
  Get-Disk | Format-Table Number, FriendlyName, BusType, PartitionStyle, Size, IsRemovable -Auto
• Look at the IsRemovable column for the disk number that matches your Seagate. If IsRemovable = True, Windows treats the device as removable.

2) fsutil drivetype (simple command for a drive letter)

• From an elevated Command Prompt run:
  fsutil fsinfo drivetype J:
• Output will be one of DRIVE_FIXED, DRIVE_REMOVABLE, DRIVE_REMOTE, DRIVE_CDROM. If it says DRIVE_REMOVABLE, that confirms the removable classification for that mounted volume.

3) DiskPart detail (confirmation)

• In an elevated Command Prompt:
  diskpart
  list disk
  select disk X <-- X is the external disk number
  detail disk
  exit
• The detail disk output includes BusType and other info; match that to PowerShell output.

4) Device Manager / Properties (GUI alternative)

• Open Device Manager → expand Disk drives → double‑click the external drive → Details tab → select FriendlyName or Hardware Ids. The BusType will usually indicate USB if it’s a USB enclosure. (This is less explicit than PowerShell but useful to confirm BusType.

Why this matters (short)

• File History expects a normal local NTFS target. When Windows treats the device as removable (or when the enclosure reports removable media), File History or other backup tools may ignore additional partitions or simply refuse to use the volume. This is a common cause of “drive not recognized” with multi‑partition externals. See our File History troubleshooting guide for the usual causes and fixes.

If the disk is reported removable — workable workarounds
A) Best practical workaround: create and mount a VHD(X) on the NTFS partition, then point File History at the mounted VHD (Windows will treat the mounted VHD as a fixed local disk)

• Disk Management GUI:
  • Right‑click Start → Disk Management → Action → Create VHD.
  • Browse to I:\ (or the NTFS partition), filename e.g. I:\VHDs\FileHistory.vhdx, choose size (e.g. 200 GB), choose VHDX and Fixed size.
  • After creation, Action → Attach VHD (it should show as a new disk). Initialize it, create a New Simple Volume, format NTFS and assign a drive letter (e.g. J.
  • Now set File History to the new J: (it will be seen as a fixed disk and File History accepts it).
• PowerShell alternative (admin):
  New-VHD -Path "I:\VHDs\FileHistory.vhdx" -SizeBytes 200GB -Fixed
  Mount-VHD -Path "I:\VHDs\FileHistory.vhdx"
  $d = Get-Disk | Where-Object PartitionStyle -Eq 'RAW' | Sort-Object -Property Size -Descending | Select-Object -First 1
  (or identify the new disk by number)
  Initialize-Disk -Number <disknumber> -PartitionStyle GPT
  New-Partition -DiskNumber <disknumber> -UseMaximumSize -DriveLetter J | Format-Volume -FileSystem NTFS -NewFileSystemLabel "FileHistory"
• This VHD trick is a standard workaround when Windows treats the physical device as removable or refuses multi‑partition usage. Community discussions often recommend it when multi‑partition externals behave oddly.

B) Other options if you prefer not to use a VHD

• Use a different enclosure/enclosure controller that reports the drive as a fixed disk (some portable externals present as removable; desktop/3.5" enclosures or certain USB‑SATA bridges present as fixed). If File History must run directly to the external, getting an enclosure that reports as fixed solves the problem.
• Use a small dedicated USB (fixed if possible) for File History only.
• Use a network share / NAS for File History (selectable by File History) or use a different backup tool (robocopy/scheduled script, a third‑party file backup, or keep using Macrium for images).

If you want, I can:

• Tell you exactly which disk number is yours and interpret the output if you paste the results of these commands:
  diskpart → list disk / list volume OR
  (Admin PowerShell) Get-Disk | Format-Table Number,FriendlyName,BusType,IsRemovable -Auto
  plus fsutil fsinfo drivetype J: (replace J: with one of your problem letters)
• Or I can give the exact ready‑to‑paste PowerShell commands to create and mount a VHDX and format it for File History.

Which do you prefer — paste the Get-Disk / fsutil outputs here and I’ll interpret them, or I’ll give the VHDX commands right away?

 

[Zevik83]

This is way beyond my 84 year old brain. Device Manager under Portable Devices Does list each of the drives D to M.

So as far as I am concerned, Win11 24h2 Home just cannot handle it. I dont want to try any of your suggestions or alternates - frankly just too much for my brain. As far as I can see, all I have is supposedly functional -and reasonably doable for a basic non-IT user -but just does not work as advertised,

What am I missing, Dear Sir, thanking you for your rapid responsiveness.

 

[ChatGPT]

You’re not missing anything obvious — you’ve done all the right, simple checks (NTFS, Basic, Healthy, BitLocker off). The most likely reason File History won’t accept those H–M partitions is that Windows is treating the physical Seagate enclosure as a “removable/portable” device; when that happens Windows and File History can be picky about using multiple partitions on that single USB device. This is a fairly common real‑world limitation (not a problem with your folder layout or drive health).
So — practical, no‑stress choices you can pick from (ranked by simplicity)

• Easiest (recommended): Use a small, dedicated USB drive for File History for each laptop (or one you move between machines). Buy a cheap 64–128 GB USB stick, set File History to that. No fiddly commands, no partition juggling.
• Low effort alternative: Keep using Macrium for full images (you already do) and copy important personal folders manually to one of the larger partitions on the Seagate when you feel like it. Not automated, but simple and safe.
• If you want automated backups and already use Google Drive: continue using Google Drive to sync your most important folders (Documents, Pictures) and rely on Macrium for full images — that combo avoids File History entirely.
• If later you want me to help (one click, no heavy brainwork): I can show one tiny PowerShell command that proves whether Windows sees the physical disk as removable (so you’ll know for sure). If it is removable and you do want automation, I can also give the effortless step for creating a VHDX on the Seagate and mounting it as a fixed virtual disk (that makes File History happy) — but that is optional and a bit more advanced.

If you’d like the one simple test now (just to confirm), run this in an Administrator PowerShell and paste the single‑line result here:
Get-Disk | Format-Table Number,FriendlyName,BusType,IsRemovable -Auto
(If that’s too much right now, don’t worry — it won’t change anything. Your simplest path is still: buy a small spare USB and point File History to it.
You’ve already done the hard part: partitioning, testing the drive, and keeping images with Macrium. If you want, tell me whether you’d prefer the “buy a small USB” option or the “I’ll do the test later” option, and I’ll give one tiny next step that won’t tax the brain.

 

[Zevik83]

I'll just go back to copying Files to the partitions as I did before I thought nI'd try File History.

Plse keep this open. I want to see if I can indeed copy my System Image over. Since that will take a couple of hours based on previous experience, I want you to wait to hear if that goes OK.

I'll pass on any other Brainwork - lost a few more braincells through this already !-))

 

[ChatGPT]

Sounds good — take your time. I’ll be here when you come back. A few tiny, practical reminders while the copy runs so you don’t need to think about anything complicated:
Quick checklist to follow while copying the system image

• Let Macrium (or whichever imaging tool you used) write directly to the NTFS partition if possible — it’s more reliable than creating the image locally and copying the file afterward.
• Confirm the destination partition is NTFS (not FAT32) — FAT32 will fail on large image files.
• Don’t interrupt the copy: leave the laptop connected to power, and the external drive on a USB 3.0 port if available.
• Monitor progress briefly in Task Manager → Performance or Resource Monitor → Disk to ensure data is flowing and the drive isn’t thrashing or erroring.
• After copy completes, run Macrium’s Verify Image (or the imaging tool’s verify) — this checks the image integrity without doing a restore. It’s fast insurance.
• Safely test the rescue environment: boot one laptop from your Macrium rescue USB (or the FAT32 rescue partition) and confirm Macrium can see and browse the image on the Seagate before you rely on it.

If something goes wrong (or it finishes and you want confirmation), tell me:

• Exact error text (copy/paste is best), or
• The output of diskpart → list disk / list volume if you suspect the partitioning/letters, or
• Macrium’s log/verify message (if it fails).

Common quick fixes I’ll suggest if you run into trouble

• “File too large” or copy error — destination is likely FAT32; reformat/convert to NTFS or write image directly to NTFS.
• “Access denied” during copy — run the copy as Administrator or write directly from Macrium to the target.
• Very slow/no progress — try a different USB port/cable and avoid USB hubs.
• Verify fails — don’t use the image; re-create the image and re-run verify. If verify fails repeatedly, run Seagate SeaTools again or replace the drive.

When you’re done, post one short line:

• “Copy finished OK” — and I’ll give the final test steps (how to boot and restore a single file or full image).
• Or paste any error you see and I’ll give the exact next command or fix.

Enjoy the break while it runs — I’ll wait for your update.

 

[Zevik83]

Well, I'm just letting Windows do the System Image and its moving along fine. nI could not find Create a System Image in my Macrium - used to be right next to Create Recovery Disk. No more in my current version. "Clone Wizard" - maybe that does it ?

Can I run Macrium Verifyon the Win creation - where is it hidden? Prob not. All your other checks re stay plugged in, write to NFTS etc done. Monitoring on Windows progress bar.

Wait till I am all done with no errors, please.

 

[ChatGPT]

Good — quick, clear answers while you let the Windows image run.
1) Clone Wizard vs Image

• Clone Wizard copies one whole disk to another disk (disk-to-disk). It’s for duplicating a drive, not for creating a compressed image file you can store and keep multiple versions of.
• To make an image file (so you can keep several dated backups), use Macrium’s “Image” function (often labeled “Image this disk” or “Create a backup” in the main window). Don’t use Clone unless you want to overwrite another physical disk with a copy of the source.

2) Where “Verify” is (Macrium Reflect)

• After a Macrium image finishes, open Macrium Reflect and find the image in the Images/Backups area (the main window shows image sets or you can browse an image file).
• Right‑click the image (or the image set) and choose “Verify Image” (or “Verify” from the context menu). That runs an integrity check against the image file(s).
• You can also mount the image (right‑click → Mount Image) and browse its files — that’s another way to confirm the image is readable.
• If you want the exact menu text for your Macrium version, tell me the Macrium version number (Help → About) and I’ll paste precise menu steps.

3) Important: Macrium Verify only works for Macrium images

• If you are letting Windows’ built‑in “Create a system image” run instead of Macrium, Macrium cannot “Verify” a Windows-created image. The built‑in tool makes VHD/VHDX files under a WindowsImageBackup folder. To check those you can mount the VHD/VHDX and inspect it (see step 4). For background on the built‑in tool see our system-image notes.

4) How to quickly check a Windows-built image (mount the VHD)

• In Disk Management: Action → Attach VHD → browse to the WindowsImageBackup\…*.vhdx on the external drive → OK.
• The VHDX will mount as a drive letter; open it in File Explorer and browse a few folders/files to ensure it’s readable. Then in Disk Management detach the VHD (right‑click the disk → Detach VHD).
• If the VHD won’t mount or shows errors, the image is suspect and you should re-create it (or use Macrium next time and run Verify).

5) Logs & where to look

• Macrium: Other Tasks → View Log Files (or open the log for the particular backup from the image list).
• Windows built‑in imaging: check Event Viewer (Applications and Services Logs → Microsoft → Windows → Backup) for job completion/ errors.

6) If you want help later

• When your Windows image completes, tell me whether it succeeded or whether any error/failed messages appear. If you used Macrium and want the exact verify steps, tell me the Macrium version and I’ll give a one‑click sequence you can copy/paste. If you used Windows’ imaging and want to test integrity, tell me the folder path to the VHDX and I’ll give the exact Attach VHD steps (or I’ll walk you through mounting it).

I’ll wait for your update — say “Image finished OK” or paste any error text and I’ll give the next step.

 

[Zevik83]

Done and Done. .Not going to bother with testing - trust to luck or buy a new compuiter. Going to copy/paste over myFiles to myn Files History partition and get on with life. Tx again form all.

 

[ChatGPT]

Great — congrats on finishing the copy. Short, practical last steps and a few gentle reminders so you don’t have to think about anything complicated right now.
What to do now (quick)

• Safely eject the Seagate when the copy is finished: System tray → Safely Remove Hardware → eject the external drive.
• Label the drive (physically and in Explorer) with date/purpose (e.g., “Seagate‑2TB — Images + Backups — 2025‑11‑10”).
• Keep the drive in a safe, dry place and keep power/cable in the same bag so you can test/restore easily later.

If you used Windows “Create a system image” (not Macrium)

• The image is a VHD/VHDX under: <drive>:\WindowsImageBackup\<ComputerName>\Backup YYYY‑MM‑DD HHMMSS\
• Quick read/test later (no rush): open Disk Management → Action → Attach VHD → browse to the .vhdx → OK → check contents in File Explorer → when done right‑click disk → Detach VHD.
  • PowerShell option: Mount-VHD -Path "I:\WindowsImageBackup...\yourfile.vhdx" and Dismount-VHD -Path "..." to detach.

If you used Macrium

• When you’re ready, run “Verify Image” in Macrium (right‑click the image in Macrium → Verify) or mount the image in Macrium and browse the files. It’s the safest single check.

Recommendations (no more brainwork)

• You don’t have to test restore now, but please test once when convenient — it’s the only real proof the backup will work when you need it.
• Keep a second copy of critical images (another external or cloud) when you have time — inexpensive insurance.
• Keep a small installer or rescue USB (Media Creation Tool or Macrium rescue) in the same kit so you can boot if needed.

If anything looks odd later (errors, verify failures, missing files) — paste the exact error text or a screenshot and I’ll tell you the one-click fix. No heavy commands unless you want them.
Enjoy the cats and the rest of your day. I’m here whenever you want to run a quick verify or need a step‑by‑step restore — zero pressure.

 

[Zevik83]

Another unexpected problem partitioning my 2TB Seagate external USB drive: Have D to L and Disk Manager says I have reached limits of number of partitions so cannot create an M on the lase remaining unallocated which I wanted. An Edge search turns up alot of unrelated tripe telling me how to p[artitionb a drive when I asked how many partitions are allowed.

 

[ChatGPT]

You ran into a very common limit — Windows is telling you the disk has reached the maximum number of partitions allowed by the current partitioning scheme. Here’s the short explanation and three practical, safe ways to proceed (I’ll emphasise the easiest one you can do now).
Why you hit a limit

• If the disk is using MBR (Master Boot Record) partitioning, MBR supports at most 4 primary partitions (or 3 primary + 1 extended containing logical drives). That’s likely what you’ve hit. If the disk were GPT (GUID Partition Table) Windows supports many more partitions (Windows typically allows up to 128). See the MBR/GPT partition differences in our archive discussion.

Quick first check (GUI — no typing)

1. Open Disk Management (Right‑click Start → Disk Management).
2. At the left, right‑click the Disk (Disk 1, etc. → Properties → Volumes tab → look at “Partition style.”
   • If it says MBR (or Master Boot Record) — that explains the 4‑partition limit.
   • If it says GPT — then we’ll need to look at another cause.

Three practical ways to get the extra “drive” you want
Option A — Easiest and least risky (recommended for now): create a VHDX file on the NTFS partition and mount it as another drive

• Why: non‑destructive, no repartitioning, behaves like a fixed disk so File History and other services treat it normally. You can create many VHD(X) files and mount them as separate drives.
• Steps (Disk Management, GUI):
  1. Open Disk Management → Action → Create VHD.
  2. Choose a location on one of your large NTFS partitions (e.g., I:\VHDs\FileHistory1.vhdx).
  3. Size: pick what you want (e.g., 100–200 GB). Choose VHDX and Fixed size (safer). Click OK.
  4. Action → Attach VHD (if not auto‑attached). The new disk will appear. Right‑click the new disk → Initialize Disk → GPT (or MBR — GPT is fine).
  5. New Simple Volume → format NTFS → assign drive letter (e.g., M.
  6. Point File History or your backup software to that new drive letter.
• If later you need another “drive,” just create another VHDX file. This avoids the partition limit entirely.

Option B — Convert the disk to GPT (recommended if you want many real partitions) — requires backup

• Why: GPT allows many partitions (Windows normally up to 128). Converting usually requires deleting all partitions (so it’s destructive) unless you use third‑party tools that claim to convert without data loss (those have risk).
• Safe procedure:
  1. Copy all data from the external to another temporary disk (backup first!.
  2. In Disk Management delete all partitions on the external disk.
  3. Right‑click the disk → Convert to GPT.
  4. Recreate all partitions the way you want and copy data back.
• If you don’t have a spare drive to hold the backup, don’t do this yet.

Option C — Use an extended partition (MBR) / logical drives (less convenient)

• If the disk is MBR and you have fewer than 4 primaries you can make one of the primaries an extended partition and create multiple logical drives inside it. But Disk Management’s support for manipulating primaries vs extended can be clumsy and may require deleting/recreating at least one partition. This is doable but riskier for your data than Option A unless you’re comfortable with careful moves or have a backup.

Which to pick now

• If you want a quick, safe fix without moving data: Option A (VHDX) — no repartitioning, reversible, and easy in Disk Management.
• If you want real partitions and plan to keep this layout long‑term and you can back up all data: Option B (convert to GPT) after backing up.

If you want, I can

• Walk you step‑by‑step through creating a VHDX (I’ll give the exact clicks).
• Or, if you prefer converting to GPT, give the exact safe backup/delete/convert/recreate steps (and a checklist so you don’t lose anything).
• Or, if you paste a screenshot of your Disk Management or paste the output of diskpart list disk / list partition, I’ll read it and give the precise tailored advice for your current layout.

Given you said you prefer to avoid extra brainwork: my single recommendation is Option A (create a VHDX). Say “Do VHDX” and I’ll give the exact six GUI clicks to perform — nothing to type, no data movement, and you’ll get your M: (or whatever letter) immediately.

 

[Zevik83]

Well D: is a 23h2 created bootable Recovery and E: its System Image. Its for a Dell Inspiron i7 that is being repaired - waiting for a part from Aliexpress and time from my overloaded local tech-guru. Its my MainMan so I dont want to delete it by repartitioning the USB drive until I use it to get it back up and running and upgraded to 24h2 - and doing the Recovery on the new Media Creator Tool.

I just mention that because I have partitions D, E and H-L - thats more than 4 partitions and H - L were all created as Simple Volumes. Drive in use right now getting a System Image from another Dell. So I'll check out what you talked about then.

Cheers for now.

 

[ChatGPT]

Thanks — that all makes sense and you’re being wise to avoid touching D: (the recovery) and E: (the image) until the Dell is back up.
Short summary and safe next step

• If you already have more than four usable partitions, your Seagate is almost certainly formatted GPT (not MBR). GPT allows many partitions so you don’t need to convert anything — and you definitely should NOT delete D: or E:.
• The easiest, safest way to get an extra “drive” (M: or whatever letter you want) without touching existing partitions is to create a VHDX file on one of the large NTFS partitions and mount it. That is non‑destructive and reversible. I’ll give the exact GUI clicks below.

Quick check — confirm partition style (one tiny GUI check)

1. Right‑click Start → Disk Management.
2. At left, right‑click the disk (where D/E/H–L live; e.g., “Disk 1”) → Properties → Volumes tab.
3. Look at “Partition style”: if it says GUID Partition Table (GPT) you’re fine — GPT supports many partitions. If it says Master Boot Record (MBR) then tell me and we’ll be careful.
   (Do this only to confirm — don’t delete anything.

Create a VHDX (safe, no data-moving, no repartitioning) — GUI steps

1. Open Disk Management (Right‑click Start → Disk Management).
2. From the menu: Action → Create VHD.
3. Location: browse to a folder on one of your big NTFS partitions (for example I:\VHDs\NewDisk.vhdx). If the VHDs folder doesn’t exist, create it.
4. Size: set the size you want (e.g., 100 GB or 200 GB). Select VHDX and Fixed size (recommended). Click OK.
5. The new virtual disk should appear in the Disk Management list as an uninitialized disk. Right‑click it → Initialize Disk → choose GPT (or MBR if you prefer, GPT is fine).
6. Right‑click the new unallocated space → New Simple Volume → Next → pick a drive letter (e.g., M → Format as NTFS → Finish.
7. You’ll now have a new drive letter (M that Windows sees as a normal fixed NTFS disk — you can point File History or copy files to it.

Why this is safe

• The VHDX is a single file on your NTFS partition. Creating and mounting it does not change or delete your existing partitions (D/E/H–L remain untouched).
• You can detach the VHD later (right‑click the virtual disk → Detach VHD) or delete the .vhdx file to free space.

If you want me to confirm your layout first

• Paste the Disk Management Volumes tab screenshot or run (Admin PowerShell): Get-Disk | Format-Table Number, FriendlyName, PartitionStyle, Size, IsRemovable -Auto and paste the output — I’ll read it and confirm the safest move.

If you prefer I can give the one‑line PowerShell sequence to create & mount a 200 GB fixed VHDX automatically — but the GUI steps above are simple and safe.
Which would you like — I’ll wait: “Do VHDX GUI” (and I’ll assume you’ll follow the steps), or paste the small Disk Management/PowerShell output and I’ll confirm?

 

[Zevik83]

It said MBR - which I really expected since Win 23h2 created the bootable D:M Recovery "disk". And yet it allowed all those partitions. IO think I may have done somethong byb stepping outside the accepted circle. Did not want to pay for Macrium Reflect and they advertised a cheaper Macrorit in place of the old Free version which I may have used to create the partitions origionally.

I'll stick to Dusk Management in future.

 

[ChatGPT]

You’re not crazy — Windows didn’t “break” and you didn’t hallucinate extra partitions. What happened is a quirk of the MBR partitioning model: MBR allows up to four primary partitions, OR up to three primary + one extended partition that can contain many logical drives (Windows shows those logical drives as separate volumes). That’s why you can end up with more than four drive letters even though the disk is MBR.
Short, clear points (what that means for you)

• MBR limit: only up to four primary partitions, but you can have a single extended partition that contains lots of logical partitions — that’s how you currently have D, E and H–L.
• GPT (what many people use today) doesn’t have that “four primary” limit and supports many partitions (Windows usually allows up to 128). If you ever need lots of real partitions or are using disks >2 TB, GPT is the modern choice. But converting to GPT safely requires a full backup first.
• MBR also has the 2 TB addressing limit (if disks are >2 TB you should use GPT). Since yours is 2 TB you’re at that boundary — keep that in mind if you later get larger disks.

Why you saw “Simple Volume / Logical Drive” behavior

• Disk Management will show logical drives inside the extended container as separate “volumes” (drive letters) even though the disk partition style is MBR. That’s a normal and supported configuration — Windows didn’t create anything weird, it just used an extended/logical layout.

What I recommend you do (safe, non‑risky)

• Do nothing drastic right now — you’ve already said you’ll avoid touching D: and E: until the Dell is back up. That’s the right call.
• If you later want more “real” partitions or UEFI/GPT benefits, back up everything from the external, then reinitialize as GPT and recreate the partitions (or use a reputable tool that can convert MBR→GPT without loss — only after you have a good backup).
• If you need extra mountable “drives” now without repartitioning, use VHDX files on one of your NTFS partitions (create and mount via Disk Management) — it’s non‑destructive and reversible (I can give the six GUI clicks again if you want). This avoids touching D/E/H–L at all.

If you want one small check (no risk)

• Open Disk Management → right‑click the Disk (Disk #) → Properties → Volumes tab → see “Partition style.” If it shows MBR, that confirms what you saw. (You already ran that and saw MBR, so you’re confirmed.

If later you decide to convert to GPT and want help

• I’ll give an exact, careful step‑by‑step checklist (backup → delete partitions → convert → recreate partitions → copy data back), or point to a non‑destructive converter and the precautions to take. Don’t do that until you’ve got a second copy of everything on the Seagate.

You handled this wisely by not touching the recovery/image partitions. If you prefer, I’ll walk you through creating a VHDX (GUI only) so you can add another mounted drive letter now without touching D/E — say “Do VHDX GUI” and I’ll list the six safe clicks.

 

[Zevik83]

Ding Dong - the Bell of recognition rings. My F: is reserved to run my external DVD, and G is for Google as previously written. So I have my 4 Primaries/Extended and then the rest H-L.

So, we are done until my other Dell is repaired and running. And I will then return to ask the Question of how to set up the 2TB as a GPT. And that could take another couple of months, no exagerati0on.

Many tx - this is an incredibly wonderful support system - and I give my best wishes to all involved,

 

[ChatGPT]

Perfect — glad the bell rang! You’ve done the sensible thing by leaving D: and E: alone until the Inspiron is back up. When you’re ready to convert the 2 TB to GPT (months from now or sooner), here’s a short, clear checklist and the safe options so you can pick what suits you then.
Quick reminders now

• Do NOT convert or delete anything until you have a full copy of any data you care about. Backups first.
• GPT is the modern choice (no 4‑partition limit, supports >2 TB and up to ~128 partitions in Windows). Converting an external data disk can be done destructively (delete → convert) or non‑destructively with third‑party tools — but always back up first.

Two safe paths to convert to GPT (pick one later)
1) Easiest + 100% safe (recommended if you can spare temporary storage)

• Backup all partitions/folders on the Seagate to another drive.
• In Disk Management: delete all partitions on the external, then right‑click the Disk → Convert to GPT.
• Recreate partitions how you want and copy the data back.
  Why: guaranteed, simple, zero‑trickery. Requires temporary storage equal to what you need to save.

2) Non‑destructive converters (faster, but riskier — still BACK UP beforehand)

• Tools like AOMEI Partition Assistant, EaseUS Partition Master, or gdisk can convert MBR→GPT without deleting partitions. Many users use them successfully.
• Pros: no intermediate copy needed. Cons: still a risk if something goes wrong (power loss, software bug). Always make a full backup first and test the backup.
  If you want, when the time comes I’ll list a recommended free tool and the exact, click‑by‑click safe procedure to run it.

Alternative if you want more “drives” without converting

• Create VHDX files on your large NTFS partition and mount them as fixed virtual disks (Disk Management → Action → Create VHD). No repartitioning, reversible, and File History/other tools treat them as fixed disks.

When you come back (I’ll prepare everything for you)

• Paste the output of: diskpart → list disk → list volume (or just tell me the Disk # and current layout), and I’ll give the exact step‑by‑step you should use for the option you choose — including the exact commands or GUI clicks, and a checklist so nothing gets lost.
• If you prefer a non‑destructive tool, I’ll give the precise tool name/version, download link, and the exact steps with screenshots.

Enjoy your cats and the rest of life until then — I’ll be here whenever you want to do the conversion. Many thanks for the kind words; glad to help.