How to Fix Google Drive Desktop App Stuck on “Loading Files” After Windows Sign-In?

You power on your Windows PC, sign in to your account, and wait for your cloud folders to appear in File Explorer. Minutes tick by, yet the Google Drive icon in your system tray just keeps spinning with the same frustrating status: “Loading files…” Your virtual drive never mounts, your spreadsheets stay out of reach, and restarting your computer only brings you right back to the exact same loop.

When Google Drive for Desktop freezes right after Windows sign-in, your files in the cloud are almost never damaged or missing. Instead, the desktop client is hitting a local roadblock—usually a corrupted cache database, a Windows folder permission glitch, a blocked network handshake, or a virtual drive letter conflict. Because the app starts automatically in the background, it can get trapped retrying the same broken startup step indefinitely.

Rather than wasting hours waiting for a progress bar that is not moving, work through the practical fixes below in order. Most Windows users resolve the issue within the first two steps.

1. Force-Quit Google Drive and Restart It Properly

Clicking the close button on a Google Drive window does not actually stop the application; it simply minimizes the app to your Windows system tray while its background sync engines keep running. If one of those background processes hung during Windows boot, a normal relaunch will not clear it.

Start with a clean process termination:

  1. Press Ctrl + Shift + Esc on your keyboard to open Task Manager.

  2. Stay on the Processes tab and scroll down until you find Google Drive (you may see more than one instance running).

  3. Select each Google Drive entry and click End task in the bottom-right corner.

  4. Close Task Manager, press the Windows key, type Google Drive, right-click the app, and choose Run as administrator.

Running the app with administrator privileges gives it immediate access to Windows file system hooks that sometimes stall right after login. If your virtual drive pops up in File Explorer within a minute, a temporary boot-time hiccup was the culprit. If it stays frozen on “Loading files,” move straight to the cache reset below.

2. Reset the Local DriveFS Cache Folder

The single most frequent cause of an endless “Loading files” screen on Windows is a corrupted local cache database. Google Drive for Desktop stores its operational database and temporary content cache inside a hidden system directory called DriveFS. If Windows shuts down unexpectedly or updates mid-sync, that database can lock up and prevent the app from ever finishing its startup check.

Clearing or renaming this folder forces Google Drive to build a fresh, healthy index without touching anything stored in your online Google Drive.

  1. Make sure Google Drive is completely closed using Task Manager (as shown in Step 1). If any background process is still active, Windows will refuse to let you modify the folder.

  2. Press Windows + R to open the Run dialog box.

  3. Type %LOCALAPPDATA%\Google\ and press Enter.

  4. Locate the folder named DriveFS.

  5. Instead of permanently deleting it right away, right-click DriveFS and rename it to DriveFS_old. (Once everything is working again, you can safely delete DriveFS_old to reclaim disk space.)

  6. Reopen Google Drive from the Start menu and sign back in to your Google account.

When you sign back in, Drive for Desktop will generate a brand-new DriveFS folder and re-index your cloud directory. Depending on how many files you store, the initial scan may take a few minutes, but you should see active progress rather than a frozen status message.

3. Check Windows Folder Permissions and Available Drive Letters

Google Drive for Desktop needs two specific things from Windows before it can mount your files: full read-and-write permissions to its local app directory and an available drive letter (typically G:) for its virtual file system. After a major Windows update or a corporate group policy change, either of those can quietly break.

First, verify your folder permissions:

  1. Open File Explorer and navigate to C:\Users\[YourUsername]\AppData\Local\Google\.

  2. Right-click the Google folder (and the DriveFS folder inside it, if present) and select Properties.

  3. Switch to the Security tab and select your Windows username under Group or user names.

  4. Confirm that Allow is checked for all permissions and that there are no checkmarks under Deny. If anything is missing, click Edit, grant full permissions, and click OK.

Second, check your drive letters. If you have multiple external hard drives, SD cards, or mapped network drives connected to your PC, Windows may have no free drive letters left—or a USB device may be conflicting with the letter Google Drive expects. Safely eject unnecessary external drives, open This PC in File Explorer to confirm plenty of letters are free, and restart Google Drive.

4. Fix Proxy, Firewall, and Antivirus Interference

If Google Drive launches cleanly but stalls while fetching your file list, something on your network or PC is likely blocking its connection to Google’s servers. VPNs, Windows Defender Firewall, and aggressive third-party antivirus suites are common offenders immediately after sign-in.

Try these quick network checks:

  • Switch Google Drive to a Direct Connection: Click the Google Drive icon in your system tray, click the gear icon, and open Preferences. Click the gear icon again in the top-right corner, scroll down to Proxy Settings, change the option from Auto-detect to Direct connection, and click Save.

  • Temporarily pause your VPN or antivirus: Disconnect any active VPN and briefly pause third-party antivirus protection. If your files load right away, add Google Drive to your antivirus exclusion list and ensure Windows Firewall allows Drive for Desktop on both private and public networks.

  • Verify your disk space: Check that your primary C: drive is not completely full. Drive for Desktop requires local breathing room to cache metadata and load your account; freeing up a few gigabytes of space and restarting the app often clears a stalled launch.

5. Disconnect, Reset Preferences, or Perform a Clean Reinstall

If the app is still stubbornly stuck on “Loading files,” your saved account token or the installation files themselves may be damaged.

First, try reconnecting your account:

  1. Click the Google Drive system tray icon, click the gear icon, and select Preferences.

  2. Click the gear icon in the top-right corner of the Preferences window and choose Disconnect account.

  3. Important: Before disconnecting, check whether you have any unsynced files in your local Lost & Found folder and copy them somewhere safe, because disconnecting removes that folder.

  4. If the sign-in screen itself misbehaves, hold down the Shift key while clicking the menu icon inside the pop-up window and select Reset User Preferences.

  5. Sign back in to your Google account and let the app re-establish its sync connection.

If disconnecting fails, perform a clean reinstall. Open Windows Settings, go to Apps, find Google Drive, and click Uninstall. Restart your PC, verify that the old %LOCALAPPDATA%\Google\DriveFS folder has been renamed or removed, and install the latest version directly from Google’s official download page.

Frequently Asked Questions

Will deleting or renaming the DriveFS folder erase my cloud files?

No. Everything inside the DriveFS folder is local application cache and operational data. Your actual files remain safely stored in Google Drive on the web. Just make sure you do not have brand-new, unsynced local files sitting inside a mirrored folder before you reset the cache.

Why does Google Drive get stuck right after I sign in to Windows?

During Windows startup, multiple services—network adapters, VPN clients, antivirus scanners, and Drive’s virtual file system driver—all launch at the same time. If Drive tries to authenticate before your internet connection stabilizes or while an antivirus scan locks its local database, it can hang on “Loading files” until manually restarted.

How long should “Loading files” normally take?

On a healthy setup, loading takes anywhere from a few seconds to a couple of minutes. However, if you just cleared your cache or signed into a massive Google Workspace account with tens of thousands of files, the initial index rebuild can take noticeably longer. If the status has not changed after 15 to 20 minutes on a fast connection, it is genuinely stuck.

Should I use Stream files or Mirror files to prevent loading freezes?

For most Windows users, Stream files is lighter on your hard drive because it keeps files in the cloud and only downloads them on demand. However, if you frequently work offline or have a large local SSD, Mirror files stores copies directly on your PC so you can still access your folders even if the desktop app momentarily struggles to connect.

A frozen “Loading files” screen feels alarming when you need your documents immediately, yet the fix almost always comes down to clearing a jammed local state. Force-quitting the hung background process, renaming the DriveFS cache folder, and double-checking your folder permissions or proxy settings will get Google Drive for Desktop back online quickly—without risking a single file in your cloud storage.

Leave a Comment