diff --git a/Downloads-and-Importing.md b/Downloads-and-Importing.md
index 0060523..facf4f0 100644
--- a/Downloads-and-Importing.md
+++ b/Downloads-and-Importing.md
@@ -19,4 +19,7 @@ Incorrect path issues are possible too, though less common in normal setups. The
 # Common Problems
 
 ## Can't see share on Windows
-The default user for a Windows service is **SYSTEM** which typically doesn't have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [why can't Sonarr see my files on a remote server](https://github.com/Sonarr/Sonarr/wiki/FAQ#why-cant-sonarr-see-my-files-on-a-remote-server) for details.
\ No newline at end of file
+The default user for a Windows service is **SYSTEM** which typically doesn't have access to your shares. Edit the service and set it up to run as your own user, see the FAQ entry [why can't Sonarr see my files on a remote server](https://github.com/Sonarr/Sonarr/wiki/FAQ#why-cant-sonarr-see-my-files-on-a-remote-server) for details.
+
+## Mapped network drives are not reliable
+While mapped network drives like `X:\` are convenient, they aren't as reliable as UNC paths like `\\server\share`. Setup Sonarr and your download client(s) so that they user UNC paths as needed. If your library is on a share, you'd make sure your root folders are using UNC paths. If your download client sends to a share, that is where you'll need to configure UNC paths since Sonarr gets the download path from the download client. It is fine to keep your mapped network drives to use yourself, just don't use them for automation.
\ No newline at end of file