By default, the Xackup Service runs under the LocalSystem account, which typically can't access network resources like mapped drives. This is due to the security context that Windows services run in.
Why This Happens
- Security context – LocalSystem has extensive system privileges, but not the same network access as a logged-in user account.
- Session isolation – Services run in a separate session from user sessions, with limited access to desktop and user-specific resources.
- Drive mapping scope – Drive mappings are created within a specific user session, so they aren't visible to the LocalSystem account.
How to Fix It
- Run the service under a dedicated user account with the necessary network permissions. Grant only the minimum privileges required for backups to run securely.
- Use UNC paths instead of mapped drives (e.g.,
\\server\share\). UNC paths aren't tied to a user session, so they're generally accessible to services running as LocalSystem. As a general rule, follow the principle of least privilege — give the Xackup service only the access it needs to perform its backup tasks.