Windows mapped drives: A previously successful mapped network drive disappears after every reboot. What is the most likely reason?

Introduction / Context:
In Windows environments, mapped network drives can be configured to reconnect automatically at user logon. If the persistence option is not set, drive letters created during a session vanish upon restart, confusing users who expect the mapping to be permanent.

Given Data / Assumptions:

• The drive mapping works during the current session.
• After reboot/logon, the mapping is gone.
• User-level mapping (not a startup script) was used.

Concept / Approach:
When mapping via File Explorer or 'net use', choosing 'Reconnect at logon' (or using '/persistent:yes') stores the mapping so Windows restores it automatically. If this box is not checked, the mapping is temporary. Other causes (server moved, legacy AUTOEXEC.BAT, last drive settings) are less relevant to modern Windows mapping behavior.

Step-by-Step Solution:

Verification / Alternative check:
Use 'net use' in a Command Prompt to verify persistence. Group Policy or logon scripts can also enforce persistent mappings.

Why Other Options Are Wrong:
Server relocation would break the mapping immediately, not just after reboot. AUTOEXEC.BAT is irrelevant in modern Windows for drive mappings. 'Last drive' is a DOS-era concept and does not affect Windows network drive persistence.

Common Pitfalls:
Mapping with elevated rights different from the user session, or using credentials that are not saved, can also cause disappearances; however, the most common cause is simply not enabling reconnect at logon.

Final Answer:
You didn't click reconnect on log on