A mapped network drive cannot reconnect after sign-in

Troubleshooting guideSources checked: 2026-09-05FaultNote editorial team

What to do first

A mapped network drive cannot reconnect after sign-in. Drive reconnection may run before Wi-Fi or VPN is ready, saved credentials may be stale, or the share name may have changed. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product: Windows mapped drives
Versions and conditions: Windows 11 (confirm the edition and hardware requirements for the feature)
Error codes and identifiers: 0x80070043

Symptoms

A mapped network drive cannot reconnect after sign-in.
The same condition can persist after a retry or restart.

Causes and conditions

Drive reconnection may run before Wi-Fi or VPN is ready, saved credentials may be stale, or the share name may have changed.

Before you start

Save open documents and allow time for a Windows restart if required.
Run administrative actions only on a personally managed PC or with administrator approval.
Save the diagnostic command output so the before and after states can be compared.
The Z: drive in commands is an example. Replace it with the affected mapped drive letter, and replace server and share with the actual UNC destination. Disconnecting a drive can interrupt open files.

Precautions

Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
Do not run unofficial scripts or unknown drivers with administrator rights.

Windows mapped drives troubleshooting sequence: Check the mapped path and VPN timing; Check the state with net; Repair through the supported path; Remap through File Explorer; Verify under the same conditions — Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

01
Check the mapped path and VPN timing
#
In File Explorer > This PC, record the drive letter and destination. If it fails only immediately after signing in, connect the required business VPN and reopen the drive. If it then works, you do not need to delete and recreate the mapping.
02
Check the state with net
#
List current mappings and record the drive letter, UNC path, and persistence state.
Command or path
```
net use
```
03
Repair through the supported path
#
After Wi-Fi or the required VPN is connected, remove only the stale mapping and map the same drive letter to the verified \\server\\share path with Reconnect at sign-in enabled.
Command or path
```
net use Z: /delete
```
04
Remap through File Explorer
#
Only if the destination changed, close files on the share, right-click the affected drive and choose Disconnect. Under This PC, choose … > Map network drive, select the original letter and correct UNC, and enable Reconnect at sign-in. Check that the letter is not already assigned elsewhere.
05
Verify under the same conditions
#
Run net use Z: \\server\share /persistent:yes and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
Check that no new critical event with the same timestamp and component appears in Event Viewer.
Command or path
```
net use Z: \\server\share /persistent:yes
```

Check the result

The feature starts, connects, or completes without the original error.
The verification command reports the expected enabled, healthy, or connected state.
The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Why does a red X disappear after I open the drive?

Sign-in reconnection may run before the network is ready. If it opens after VPN connects, investigate startup timing before remapping.

Must I change the drive letter?

Only if that letter conflicts with a local drive or another mapping.

Official sources and dates

Map a network drive in Windows ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides