What is a mapped drive?
A network share is normally reached by its UNC path, \\servername\sharename. Mapping assigns that path a drive letter, such as S:, so users and older programs can treat the share like a local disk. The data still lives on the file server and travels over SMB. Mappings belong to the user who created them: another account on the same PC does not see them, and a mapping set to reconnect is saved in that user's profile and restored at each sign-in.
Mapping a drive in File Explorer
- Open File Explorer and select This PC.
- In Windows 11, open the command bar's See more (...) menu and choose Map network drive.
- Pick a drive letter and enter the folder path, such as
\\fs01\sales, or click Browse. - Check Reconnect at sign-in to make it persistent, and Connect using different credentials if the share needs another account.
- Click Finish. The drive appears under This PC in the Network locations group.
Mapping from the command line
net use S: \\fs01\sales /persistent:yesmaps S: and reconnects it at sign-in.net use S: \\fs01\sales * /user:CORP\jsmithconnects as another account and prompts for its password.net useon its own lists current connections and their status.net use S: /deleteremoves one mapping, andnet use * /deleteremoves all of them.- PowerShell:
New-PSDrive -Name S -PSProvider FileSystem -Root \\fs01\sales -Persist, orNew-SmbMapping -LocalPath S: -RemotePath \\fs01\sales.
Mapping drives for many users
In organizations, drives are rarely mapped by hand. A login script containing net use commands, Group Policy Preferences Drive Maps, or an MDM platform maps the right drives for each user or group at sign-in. A home folder set on the Profile tab of an Active Directory user account can also map a personal drive letter automatically.
Troubleshooting mapped drives
| Symptom | Think |
|---|---|
| Drive shows a red X and Disconnected after sign-in | The server or network was not ready when Windows reconnected; open the drive to retry, then check the server and network |
| System error 53: the network path was not found | Name resolution, a firewall, the server being off, or a mistyped server name |
| System error 67: the network name cannot be found | The server answers but the share name is wrong or no longer shared |
| System error 5: access is denied | Share or NTFS permissions, or the wrong credentials |
| System error 85: the local device name is already in use | The drive letter is taken; choose another or delete the old mapping |
| System error 1219: multiple connections with more than one user name | A connection to that server already exists under different credentials; remove it with net use and reconnect |
| Wrong account keeps being used | Remove the saved entry in Credential Manager > Windows Credentials and reconnect |
| Drive visible in File Explorer but missing in an elevated Command Prompt | Under UAC the elevated session is separate, so its mappings differ; use the UNC path or map the drive again in that window |
| A scheduled task or service cannot find S: | Mappings are per user session; scripts that run as another account should use UNC paths |
Mapped drive on the CompTIA A+ exam
Mapped drives are part of Core 2 (220-1202) objective 1.7, which covers Windows networking features such as shares, mapping and connections. Know both the File Explorer method and the net use syntax, the UNC format \\server\share, what the persistent option does, and that administrators can also map hidden administrative shares such as \\PC01\C$. When a scenario says users need the same network folder at the same letter every day, think persistent mapping, a login script or Group Policy.