Google Drive Not Showing Up in Windows File Explorer

When Google Drive for Desktop is installed and running but does not appear under This PC or the sidebar in Windows File Explorer, the operating system has failed to attach the virtual file system mount point. This issue prevents direct local access to your cloud files, streaming folders, and Shared Drives.

Fast Fix

Restart the Google Drive process. Right-click the Google Drive icon in the system tray (notification area), click the Settings gear > Quit, then relaunch Google Drive from the Windows Start menu. If it still does not appear, check Disk Management to verify whether the assigned drive letter conflicts with an existing network or local drive.

Diagnostic Snapshot

Parameter	Specification
Affected Scope	Windows 10, Windows 11 (Google Drive for Desktop client)
Observable Symptom	System tray icon may be running, but no virtual drive (default G:) appears in File Explorer under “Devices and drives” or the navigation pane
Underlying Subsystems	Virtual filesystem driver (WinFsp), Windows Shell Namespace integration, local drive letter assignment
Admin Access Required	No for client-level restarts or drive letter reassignment; Yes if repairing virtual filesystem drivers or modifying group policy drive maps

Forensic Decision Path

Use the following checks to isolate why the virtual drive is not mounting in Windows:

[Google Drive Missing in Explorer]
  │
  ├─► Is the Google Drive icon present in the Windows System Tray?
  │     ├─► No  ──► Process is not running or crashed on boot. Check Windows Task Manager.
  │     └─► Yes ──► Process is active. Check account sync and mount status.
  │
  ├─► Is there an error banner in the Drive desktop utility?
  │     ├─► "Mount point already in use" ──► Drive letter collision. Reassign drive letter.
  │     ├─► "Account disconnected" ────────► Re-authenticate OAuth session.
  │     └─► "Drive has stopped" ───────────► Virtual driver crash or corrupted local cache.
  │
  └─► Is the drive letter visible in Disk Management / Command Prompt (`diskpart`), but missing in File Explorer?
        ├─► Yes ──► Windows Explorer shell cache issue or policy hiding drive letters.
        └─► No  ──► WinFsp / Virtual File System driver failed to initialize.

What This Means: System Mechanics

Google Drive for Desktop does not store a complete duplicate of your cloud files on your local hard drive by default. Instead, it creates a virtual filesystem mount point using a driver (WinFsp) to present cloud files dynamically inside Windows File Explorer as a local drive letter (typically G:).

For the drive to appear in File Explorer, three distinct layers must complete successfully:

1. The Core Engine: GoogleDriveFS.exe runs in user space and authenticates against Google Workspace identity services.
2. The Virtual Driver: The kernel-level driver mounts a virtual disk partition and binds it to an available Windows logical drive letter.
3. The Shell Extension: Windows Explorer registers the mount point in the left-hand navigation tree and under “Devices and drives.”

If an assigned drive letter is already reserved, if the WinFsp driver fails to start, or if the process crashes silently, the client remains disconnected from Windows File Explorer. If your setup involves virtualized desktops or terminal environments, profile persistence issues can also prevent the drive from loading; see Drive for Desktop vs. Virtual Desktop Infrastructure (VDI).

Common Causes

• Drive Letter Collisions: Drive for Desktop defaults to mounting on letter G:. If a USB drive, local partition, or mapped network share (SMB) already occupies that letter, Drive for Desktop cannot mount without an explicit configuration change. If a collision is causing explicit mount errors, refer to Error: “Mount point already in use” (Drive Letter Conflicts).
• Virtual Filesystem Driver Failure: The underlying driver (WinFsp) may fail to initialize if an antivirus tool blocks its service or if a Windows Update corrupts the driver registration.
• Hung Background Processes: A previous instance of GoogleDriveFS.exe may remain stuck in a suspended state in the background, preventing newly launched instances from claiming the mount point.
• Corrupted Local Application State: Stale metadata or damaged cache databases in %LOCALAPPDATA%\Google\DriveFS can cause the initialization routine to abort before the mount command executes.
• Account Disconnection or Auth Loops: If Google Workspace requires re-authentication, the client will withhold the virtual drive until the user signs in again. For recurring sign-in loops, see Resolving “Account disconnected: Please sign in again” Loops.

Common Misdiagnoses

• Misdiagnosis: “The files were deleted from the cloud.”
  • Distinction: Missing drives in File Explorer are local mounting or process failures. Log in to drive.google.com in a web browser to confirm that your cloud files and Shared Drives are intact.
• Misdiagnosis: “The local hard drive is full.”
  • Distinction: Drive for Desktop streams files on demand and does not require local disk space equal to the size of your cloud storage. While low disk space can trigger caching warnings, it does not hide the drive letter itself. For related disk space anomalies, see How to Resolve “Disk Full” Errors with Plenty of Space.
• Misdiagnosis: “Firewall or proxy is completely blocking the app.”
  • Distinction: Network blocks usually cause a “Disconnected” or “Offline” sync status inside the tray menu, but the virtual drive letter itself still mounts and shows existing cached files. If network rules are actively blocking traffic, review How to Whitelist Google Drive for Desktop in Windows Firewall.

Resolution Steps

Step 1: Force-Terminate and Relaunch Google Drive

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Select the Details tab.
3. Locate any processes named GoogleDriveFS.exe.
4. Right-click each process and select End task.
5. Open the Windows Start menu, search for Google Drive, and launch the application.
6. Open File Explorer (Win + E) and verify if the drive appears under This PC.

Step 2: Assign an Unused Drive Letter

If another volume has taken the default letter:

1. Click the Google Drive icon in the system tray.
2. Click the Settings gear > Preferences.
3. Click the Settings gear in the top right corner of the Preferences window.
4. Scroll down to Google Drive streaming location.
5. Under Drive letter, change the selection from G: (or current) to a letter near the end of the alphabet (such as M:, S:, or X:).
6. Click Save and confirm the prompt to Restart now.

Step 3: Restart the Windows Explorer Shell

If the drive is mounted in the background but the Windows desktop shell has not refreshed its UI:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. On the Processes tab, scroll down to Windows Explorer.
3. Right-click Windows Explorer and select Restart.
4. Check if the Google Drive entry populates in the navigation sidebar.

Step 4: Clear Corrupted Local State

If a damaged local database is preventing initialization:

1. Exit Google Drive completely from the system tray (Gear icon > Quit).
2. Press Win + R, type %LOCALAPPDATA%\Google, and press Enter.
3. Locate the DriveFS folder.
4. Rename DriveFS to DriveFS_Old (this preserves your configuration as a backup).
5. Relaunch Google Drive from the Start menu and sign in to re-initialize the local database.
6. If you need detailed guidance on managing cached files safely, see How to Clear Google Drive Local Cached Files Safely.

Step 5: Repair or Reinstall the Application

If the virtual driver files were corrupted:

1. Press Win + R, type appwiz.cpl, and press Enter.
2. Locate Google Drive, right-click it, and select Uninstall.
3. Reboot your computer.
4. Download the latest installer from the official Google Workspace distribution page and run the installer with administrative privileges.

Admin & Advanced Checks

• Verify Service Status via Command Line: Run sc query winfsp in an elevated Command Prompt to confirm that the virtual filesystem service driver is registered and in a RUNNING or STOPPED (demand-start) state.
• Google Workspace Admin Console Policies: Ensure that Google Drive for Desktop access has not been restricted for the user’s Organizational Unit (OU). Navigate to Apps > Google Workspace > Drive and Docs > Features and Applications > Google Drive for Desktop to verify permission status. If the admin has disabled access, see Error: “Your administrator has disabled Google Drive for Desktop”.
• Group Policy Drive Hiding Checks: Verify whether the domain policy Hide these specified drives in My Computer (located in User Configuration\Administrative Templates\Windows Components\File Explorer) is active and masking the assigned drive letter.

Hard Stops

Stop local troubleshooting and escalate to your IT administrator or security team under these conditions:

• Endpoint Security System Blocks: If your organization’s Endpoint Detection and Response (EDR) software flags or quarantines GoogleDriveFS.exe or its driver extensions, do not attempt to bypass local security controls.
• Repeated Driver Installation Failures: If reinstalling consistently produces error codes during driver registration, inspect system event logs for storage controller conflicts. For broader error code diagnostics, consult The Master List of Google Drive for Desktop Error Codes.