Troubleshooting guide
Network Drive Disconnected After Reboot: Restore the Persistent Mapping
Category: File Sharing
You mapped a shared folder from another LAN PC, but after restarting Windows the drive letter is missing and you are stuck before you can diagnose it properly.
Check whether the mapping is set to persist
Open Command Prompt and run net use. Look at the entry for the missing drive. If it is absent, the mapping was not saved for this logon session. If it appears with a status like Unavailable or Disconnected, the mapping exists but the connection is failing. In either case, remove the stale entry with net use Z: /delete (replace Z: with your drive letter), then recreate it with net use Z: \\ServerName\ShareName /persistent:yes. Using the server name rather than its IP address avoids failures when the address changes.
Check for conflicting stored credentials
Open Credential Manager and review Windows Credentials. A saved credential for the server that no longer matches its current account can silently break reconnection at logon. Remove the old entry, then reconnect and enter the correct credentials when prompted.
Verification test
Restart the PC and sign in. Run net use again and confirm the drive shows as Available, then open it in File Explorer and create a small test file. If the drive returns but the file operation fails, the share permissions, not the mapping, need attention.
Rollback and recovery
If a change makes things worse, delete the mapping and recreate it with the original settings. Keep a note of the exact net use command that worked so you can restore it quickly. If the network drive disconnected after reboot persists after these checks, the cause is likely policy or logon timing rather than the mapping itself.

Ask for help with your net use output and Credential Manager details for a targeted diagnosis.