0X0000008B

Fix ERROR_SUBST_TO_SUBST (0x0000008B) on Windows 10/11

Trying to substitute a drive letter to a folder that's already on a substituted drive? That's the trigger. Here's why it fails and how to fix it cleanly.

When does this error show up?

You run something like subst X: C:\Users\You\ProjectA, then later try subst Y: X:\SomeSubfolder. Windows kicks back with ERROR_SUBST_TO_SUBST (0x0000008B) — “The system tried to substitute a drive to a directory on a substituted drive.”

This also happens if you already have subst Z: D:\Work and then attempt subst D: Z:\Temp. The moment you point a new drive letter to a path that lives on an already-substituted drive, Windows rejects it.

Why does this happen?

The subst command maps a drive letter to a local folder path. Under the hood, Windows creates a symbolic link-like object in the object manager namespace. The key rule: you can't chain or nest these mappings. Windows won't let you create a subst that resolves through another subst — it sees a circular dependency risk and a namespace ambiguity.

What's actually happening here is that the target path X:\SomeSubfolder isn't a real physical path; it's a virtual path that only exists because X: is already substituted. So when you try to substitute Y: to that virtual path, Windows checks if the target is itself a subst drive, and it is — so it blocks the operation.

The fix: unmap and remap in the correct order

Skip any workarounds with junction points or symbolic links for this specific error — they won't solve the nesting constraint. The real fix is to restructure your substitutes so no drive points through another substitute.

  1. List all current substitutes
    Open Command Prompt as Admin (yes, you need admin rights for subst changes on some systems). Run:
    subst
    This shows every drive you've mapped. Write them down.
  2. Remove the conflicting substitutes
    Suppose you had X: -> C:\Users\You\ProjectA and then tried Y: -> X:\Subfolder. Remove both:
    subst X: /d
    subst Y: /d
  3. Remap the parent, then the child using the real physical path
    First, map the drive that holds the folder:
    subst X: C:\Users\You\ProjectA
    Now — don't use X: as part of the target for Y:. Instead, point Y: directly to the physical path:
    subst Y: C:\Users\You\ProjectA\Subfolder
    Now Y: resolves to the same physical folder without passing through X:. Windows is happy.
  4. Verify it worked
    Run subst again. You'll see both drives listed. Test accessing each.

If it still fails

Three things to check:

  • Are you trying to substitute a drive letter that's already a network drive or a removable disk? You can't use subst on a drive letter assigned to a network share or an active USB drive. Remove the network mapping first (net use X: /delete).
  • Did you accidentally leave leftover subst drives? Run subst and remove any that mention the same drive letter you're trying to use.
  • Is the target folder on an NTFS volume? subst works on NTFS and FAT32, but if you're on an exFAT external drive, it might silently fail — check with fsutil fsinfo volumeinfo C:\.

If none of that works, restart Explorer or reboot. The object manager sometimes holds stale references after failed subst attempts.

Related Errors in Hardware – Hard Drives
0X00030202 Retry error 0x00030202 on external drives – fix it now 0X00000022 Fix ERROR_WRONG_DISK (0X00000022) on Windows 10/11 0x8007045D (often accompanies this) Fix 'File System Journaling Recovery Failure' on Windows 10/11 0X8011045A Fix COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES (0X8011045A) Fast

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.