Citrix client drive mapping not working: a troubleshooting checklist
Local drives missing in a Citrix session? Check the Workspace app's file access, the File Redirection policies that apply, browser access, and a test file.
Read the video transcript
0:00 — No local drives in the Citrix session
In the Citrix session, File Explorer shows only the VDA's own disk. The PC's drives C: and E: are missing.
0:08 — Check what the Workspace app may share
Workspace app asks before a session can use local files. If the store is set to No access, no drives appear. Change it, then reconnect.
0:17 — Check the File Redirection settings that apply
Client drive redirection must be allowed, or no drive maps at all. Drive-type, auto-connect and read-only settings refine it. Several policies can apply.
0:28 — Browser sessions don’t map drives on their own
The installed Workspace app maps drives automatically when allowed. In a browser, users map a folder from the toolbar in desktop Chrome or Edge, or use upload and download.
0:36 — Reconnect, then prove it with a test file
In a fresh session, the PC's drives appear with its name. Save a harmless test file to the mapped drive and find it on the PC.
0:47 — Need the PC’s folders inside published apps?
TwinPane, on its own connection outside ICA, can map the PC's own folders into a published app's dialogs. Pilot it on one VDA and one PC.
When a user's local drives don't appear in a Citrix Virtual Apps and Desktops session, three layers have to agree: the Citrix Workspace app on the endpoint, the Citrix policies that apply to the session, and the way the user connects. Find the layer that says no before changing anything.
This checklist is for an administrator investigating one affected user. The video is an illustrated walkthrough: its Windows, Workspace app and policy screens are mock-ups, not recordings of Citrix Studio or a live session. Citrix references were checked on 27 September 2026.
1. Record the connection before you change anything
Write down the endpoint OS, the Workspace app platform and version, whether the user opens a published desktop or a published app, and whether they connect through the installed app or a web browser. Add one affected user, one VDA, and one drive. A precise starting point makes the before-and-after result easy to compare.
Know what "working" looks like. In a session, a mapped client drive usually appears with the endpoint's name, such as Local Disk (C: on DESK-9M53Q04), and Citrix documents that client drives appear as network mappings, lettered from V: backwards by default. A drive named Local Disk (C:) without a client name is the VDA's own disk. Users who save there are saving to the server.
2. Check what the Workspace app was allowed to share
Citrix Workspace app asks the user, or follows its stored preference, before it gives a session access to local files. The options are Read and write, Read only, No access, and Ask me each time. A user who once chose No access, or dismissed the prompt, can end up with no drives while every server-side setting is correct. On Windows, Citrix documents this preference under Connection Center › Preferences › File Access; administrators can set the default centrally (CTX133565).
If you change the preference, disconnect and reconnect the session, then look again.
3. Check the Citrix policies that actually apply
Client drive mapping is controlled by the ICA › File Redirection policy settings (Citrix reference):
- Client drive redirection must be allowed. If it is prohibited, no client drives map, whatever the drive-type settings say.
- Client fixed drives, Client removable drives, Client network drives, and Client optical drives allow or prevent each type of drive. A USB stick is a removable drive.
- Auto connect client drives decides whether drives connect automatically at logon.
- Read-only client drive access lets users open files from mapped drives but not save to them. This explains "I can see the drive but can't save".
These are allowed by default, so a missing drive usually means a policy somewhere prohibits it. Several policies can apply to one session; use policy modeling in Citrix Studio to see the resulting settings for the affected user and VDA, rather than reading a single policy in isolation. Citrix's client drive mapping article covers the requirements.
If a restriction is intentional, document what the user needs and ask the policy owner which transfer workflow is approved. A different tool would need that approval, too.
4. Browser access works differently
With Citrix Workspace app for HTML5, drives don't map on their own. On desktop Google Chrome and Microsoft Edge, users can choose Map a drive from the session toolbar, pick an access level and a local folder, then reconnect for it to appear. Otherwise, browser sessions use upload and download, governed by the File transfer, Upload file and Download file policies for Workspace app for ChromeOS/HTML5 (Citrix: file handling). Don't expect a browser session to behave like the installed Windows app.
5. Reconnect and prove it with a test file
After an approved change, start a fresh session rather than reusing a disconnected one. Then:
- Open File Explorer (or the published app's Save As dialog) in the session.
- Find the mapped drive with the endpoint's name and browse to the intended folder.
- Save a harmless file with a distinctive name, such as
ctx-drive-test-0927.txt. - Open File Explorer on the endpoint and confirm the file is in the same folder.
Record what you changed, the VDA you tested on, and the result. If the drive appears but saving fails, check Read-only client drive access and the Workspace app's file access level before looking elsewhere.
6. Decide whether drive mapping is the right workflow
If the user can now reach the drive and complete the approved task, keep that working solution. Some requirements are different: opening a file from the session in a local Windows application, or presenting the PC's own Desktop, Documents and Downloads inside a published app's dialogs. Drive access alone doesn't solve those.
TwinPane is built for those workflows. It uses its own connection outside ICA, with TwinPane Server on the Windows VDA and TwinPane Client on the user's Windows PC, and it needs a deployment your organization approves. Read how TwinPane works with Citrix and the comparison with drive redirection. A pilot should cover one VDA, one Windows PC, the real published app, and a harmless file; confirm the Client and Server connection first.
Keep a useful escalation record
Note the endpoint and Workspace app version, connection type, VDA, drive, the Workspace app file access setting, the resulting File Redirection policy values, the application, the expected folder, and the observed result. Include whether a fresh session changed anything. Keep credentials and customer files out of screenshots.
Similar problems on other platforms: AVD local drives not showing and RemoteApp saves to the server instead of my PC. To evaluate TwinPane, start a 30-day trial for up to five devices and review pricing, which starts at 20 paid devices.