A surprising number of "my NAS drive won't install software / won't show up in backups" problems come down to one distinction that Windows makes very quietly: a mapped network drive is not a disk.
Both give you a letter you can double-click. Underneath, they are different.
What "map network drive" actually creates
When you right-click a share and choose "Map network drive", Windows hands the path to the SMB redirector (or the WebDAV MiniRedirector for HTTPS/SharePoint-style URLs). Your app opens a file by calling into a client-side network provider. No new device appears in the disk stack, because there is no new device.
The practical consequences:
- Device Manager shows nothing new. There is no volume in "Disk drives".
- Drive properties say "Network Drive". That string is not decoration; it is the answer to "do I have a disk or a redirector".
- Disk quota, BitLocker, and most volume-level tools are absent. Their right-click entries simply do not appear.
- Installers, imaging tools, and backup agents often refuse. Plenty of them require a volume they can query with the IOCTL surface, not a path the network provider resolves for them.
-
Some apps resolve the path themselves. They see
Z:\...and treat it as a local path, then fail in confusing ways.
What a mounted drive letter creates
Mount a WebDAV or HTTPS endpoint with a file system driver (WinFsp is the common one on Windows) and you get a real volume: a device node, a file system, ACLs, and a place in the volume list. Programs that query the disk stack now find it.
Note the difference in direction. A mount does not copy your data onto the PC. It exposes the remote share as a file system, with a local write cache in front of it. That is the opposite of a sync client, which keeps a full local mirror and reconciles changes. If your goal is "free up local disk space but keep the files reachable from every program", a mount is the right shape; a sync client is the wrong one, because the local copy is exactly the space you were trying to reclaim.
Four checks that settle it
- Device Manager -> Disk drives. Is your letter listed there? If not, it is a network mapping.
- Right-click the letter -> Properties. Read the drive type. "Network Drive" means mapping; "Local Disk"/"Hard disk" means a mounted volume.
- Right-click the letter. Do you get Disk Quota / BitLocker / "Initialize Disk" entries? Volume-only features mean volume.
- Install something real. Copy a 100 MB+ installer locally and run it with the drive present. If it fails with an I/O or path error that a local file would not, the mount is not surfacing what the installer needs.
Protocol notes that bite on the mount path
- Non-ASCII names need correct URL encoding. A Chinese or accented folder name that lists fine in the browser can 404 on mount if the path is not percent-encoded per RFC 3986.
-
Windows' built-in WebDAV client requires HTTPS for Basic auth. Over plain
http://, credential handling is unreliable - usehttps://endpoints. - File locking is where "the file is in use by another process" comes from. Word, Excel, and installers take a byte-range lock (LOCK/UNLOCK) before writing. If the server ignores or mishandles LOCK, the client reports a spurious sharing violation. A driver that backs off and retries on lock contention turns a hard failure into a delay.
- Resume matters more than throughput on flaky links. Large writes that fail at 90% are the ones that make people give up; a local cache that can resume after a disconnect is worth more than a higher number on a speed test.
Where this leaves the tooling
I work on ScsDriver, which mounts WebDAV/HTTPS endpoints as real Windows drive letters over WinFsp, with a local cache, credential caching, resumable transfers, and backoff-and-retry on remote file locks. It currently costs $5.50 as a one-time purchase - a lifetime license, not a subscription, and there is a 7-day full-feature trial. Website: drive.scsoi.com
Whatever you use, run the four checks above before you trust the letter in Explorer. It takes about two minutes, and it tells you whether the problem you are chasing is a mount problem or a protocol problem.
