When you pin a network share to Quick Access in Windows 11, the shortcut often breaks after a reboot. A red X appears on the folder icon, and clicking it shows an error message saying the network path was not found. This happens because Windows does not automatically reconnect mapped network drives or Quick Access shortcuts on startup. In this article, you will learn how to use a startup script and persistent drive mapping to keep your network share pinned and accessible after every restart.
Key Takeaways: Keep Network Share Pinned in Quick Access After Reboot
- Map network drive with /persistent:Yes option: Ensures the drive letter is remembered across reboots so Quick Access shortcuts stay connected.
- Startup script in Task Scheduler: Runs a net use command at logon to reconnect the share before Windows loads Quick Access.
- Enable Credential Manager entry: Stores the network credentials so the connection does not prompt for a password on each boot.
Why Network Share Shortcuts Break After a Reboot in Windows 11
Windows 11 uses Quick Access to show frequently used folders and recently accessed files. When you pin a network share by dragging it to the Quick Access section in File Explorer, Windows stores a shortcut that points to the UNC path. The problem is that Quick Access does not automatically re-establish the network connection when the computer restarts. If the network share requires authentication or if the network adapter initializes after File Explorer loads, the shortcut fails.
The underlying cause is that Quick Access shortcuts are not network-aware connections. They are simple pointers. Windows does not retry the connection if it fails during startup. In contrast, a mapped network drive with the persistent flag enabled tells Windows to attempt reconnection at each logon. The solution is to map the network share as a persistent drive and then pin that drive letter to Quick Access. This way, the drive letter reconnects automatically, and the Quick Access shortcut follows.
Steps to Pin a Network Share to Quick Access That Survives Reboots
Follow these steps to map a network share as a persistent drive, pin it to Quick Access, and configure a startup script for reliable reconnection.
Step 1: Map the Network Drive with Persistent Flag
- Open File Explorer
Press Win + E to open File Explorer. Click the three-dot menu in the toolbar and select Map network drive. - Choose a drive letter
In the Drive dropdown, select an unused letter such as Z. Do not use letters already assigned to local drives. - Enter the network path
In the Folder field, type the UNC path of the share, for example\ServerName\SharedFolder. Check the box labeled Reconnect at sign-in. This sets the /persistent:Yes flag. - Finish the mapping
Click Finish. If credentials are required, enter them and check Remember my credentials.
Step 2: Pin the Mapped Drive to Quick Access
- Locate the mapped drive
In File Explorer, under This PC, find the drive letter you assigned, for example Z:. - Pin to Quick Access
Right-click the drive and select Pin to Quick Access. Alternatively, drag the drive to the Quick Access section. - Verify the pin
Click Quick Access in the left pane. You should see the drive letter listed under Frequent folders or Pinned.
Step 3: Create a Startup Script with Task Scheduler
Even with the persistent flag, some network shares disconnect if the network is slow or if credentials expire. A startup script forces the connection at each logon.
- Open Task Scheduler
Press Win + R, typetaskschd.msc, and press Enter. - Create a new task
In the right pane, click Create Task. Give it a name such as Reconnect Network Share. - Set the trigger
Go to the Triggers tab. Click New. Set Begin the task to At log on. Select any user. Click OK. - Add the action
Go to the Actions tab. Click New. Set Action to Start a program. In Program/script, typenet use. In Add arguments, typeZ: \ServerName\SharedFolder /persistent:Yes. Replace Z and the path with your values. Click OK. - Configure conditions
Go to the Conditions tab. Uncheck Start the task only if the computer is on AC power. Uncheck Stop if the computer switches to battery power. This ensures the script runs on laptops. - Save the task
Click OK. Enter your Windows password if prompted. The task now runs at every logon.
Step 4: Store Credentials in Credential Manager
- Open Credential Manager
Press Win + R, typecontrol /name Microsoft.CredentialManager, and press Enter. - Add Windows credentials
Click Windows Credentials. Click Add a Windows credential. - Enter the network resource details
In Internet or network address, type the server name or IP, for exampleServerName. Type the user name and password. Click OK.
After completing these steps, restart your computer. When you log in, open File Explorer and click Quick Access. The network share should appear without a red X and open immediately.
Common Issues with Persistent Network Shares in Quick Access
Red X still appears on the Quick Access shortcut after reboot
If the red X persists, the mapped drive did not reconnect before File Explorer loaded. Open File Explorer and check if the drive letter appears under This PC. If it shows a red X there too, the Task Scheduler script may not have run. Open Task Scheduler, find your task, and click Run to test it. Check the event log under Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational for errors.
Network share requires different credentials on each reboot
If you are prompted for credentials every time, the stored credentials in Credential Manager may be incorrect. Delete the existing entry and add it again. Ensure the user name includes the domain, for example DOMAIN\UserName. For workgroup computers, use the computer name as the domain, for example ComputerName\UserName.
Drive letter is already in use by another device
If the drive letter you assigned conflicts with a USB drive or another network share, the mapping fails. Open Disk Management by pressing Win + X and selecting Disk Management. Right-click the volume using the conflicted letter and choose Change Drive Letter and Paths. Select a different letter. Then update your net use command and Task Scheduler script with the corrected letter.
Mapped Drive vs Direct UNC Path: Quick Access Behavior
| Item | Mapped Drive (Z:) | Direct UNC Path (\Server\Share) |
|---|---|---|
| Persistence after reboot | Works with /persistent:Yes flag and startup script | Breaks unless you manually reconnect |
| Credential storage | Stored in Credential Manager or net use with /savecred | Not stored — requires password each time |
| Speed of access | Faster because drive letter is resolved at logon | Slower — Windows resolves path each time you click |
| Compatibility with older apps | Required for many legacy programs | Works with modern apps that support UNC |
| Ease of pinning to Quick Access | Drag and drop works | Drag and drop works but breaks on reboot |
The mapped drive method is more reliable for Quick Access because the drive letter reconnects as a system resource. The direct UNC path shortcut in Quick Access is a simple link that does not trigger reconnection logic.
You can now pin any network share to Quick Access and trust that it will remain available after each reboot. For shares that require frequent credential changes, update the Credential Manager entry and the net use arguments in Task Scheduler. To verify the connection is active, press Win + E and look for the drive letter under This PC before opening Quick Access.