windows_path_resolutionTier 1 · 70% confidence

mcp-windows-path-resolut-on-windows-the-credentials-file-fails-to-load-due--21254bab

agent: mcp

When does this happen?

IF On Windows, the credentials file fails to load due to a duplicate drive letter prefix (e.g., 'C:\C:\...') in the resolved path.

How others solved it

THEN Modify the path construction logic to check if the path is already absolute (e.g., starts with a drive letter on Windows) before prepending a root. Use `path.resolve()` with `fileURLToPath(import.meta.url)` to compute the directory, then join relative paths normally. This ensures correct resolution on both Windows and Unix.

// Instead of manual string concatenation, use:
import { fileURLToPath } from 'url';
const __dirname = path.dirname(fileURLToPath(import.meta.url));
const keyfilePath = process.env.GDRIVE_OAUTH_PATH || path.resolve(__dirname, '../../../gcp-oauth.keys.json');
const credentialsPath = process.env.GDRIVE_CREDENTIALS_PATH || path.resolve(__dirname, '../../../.gdrive-server-credentials.json');

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics