Windows network drives – Mapped drive disappears after every reboot A previously working network drive mapping vanishes on each restart. What is the most likely reason?

Introduction / Context:
In Windows environments, network shares can be mapped to drive letters for quick access. Users sometimes report that the mapping “disappears” after a reboot. Understanding how persistent mappings work avoids repeated remapping and support calls.

Given Data / Assumptions:

• Standard Windows client joined to a network domain or workgroup.
• The mapping works during the session but is gone after restart.
• No Group Policy or logon scripts overriding user mappings (most typical home or small office scenario).

Concept / Approach:

Windows offers a checkbox (or equivalent option) “Reconnect at logon” or “Reconnect at sign-in” when creating a mapped drive. If this is not selected, the mapping is non-persistent and exists only for the current session, vanishing after reboot or logoff.

Step-by-Step Solution:

Verification / Alternative check:

From Command Prompt: use net use Z: \server\share /persistent:yes to enforce persistence. After reboot, net use should list the drive as reconnected (assuming network availability and credentials).

Why Other Options Are Wrong:

Physical relocation of the server is irrelevant unless it changed network addressing. AUTOEXEC.BAT and BIOS drive letters are legacy and unrelated in modern Windows. Video drivers do not clear mappings.

Common Pitfalls:

Forgetting stored credentials or trying to reconnect before networking is up; Group Policy logon scripts that remap drives; using different user accounts that lack permissions to the share.

Final Answer:

You did not select “Reconnect at logon” when mapping the drive.