Google Drive for desktop signs in through a browser and then connects the desktop application. If that handoff fails, check the selected identity, app state, and organizational policy before reinstalling or disconnecting an account that may contain unsynced work.
Confirm the intended sign-in flow
Launch the official Drive desktop app and use its sign-in action. In the browser, select the exact authorized account. A browser already signed into several identities can make it easy to choose a personal account instead of work or school.
Complete the legitimate sign-in and any required organization verification through the normal Google or managed identity flow. Never send a password or verification code to someone offering to complete the handoff for you.
Check the app and environment
Return to the desktop app and inspect the displayed account and error. Check the network and supported operating system. Google lists unavailable Windows drive letters, proxy settings, and administrator device restrictions among reasons an account may not load.
On a managed device, ask whether Drive for desktop is permitted for that account and computer. Do not bypass a company proxy or install an unrelated sync client to avoid a policy restriction.
Escalate without losing local work
Record where the flow stops, the exact message, account type, app version, operating system, and time. A controlled app restart may help, but preserve pending edits before more disruptive steps. Disconnection can remove offline and Lost and Found files, so it is not a harmless first diagnostic. If browser authentication succeeds but the application remains unconnected, report that distinction clearly to the administrator or official support rather than repeatedly generating sign-in attempts.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.