File Content Not Downloading After Moving Local Project to Different Disk/Path (Windows 11)

[tormyvancool]

Bug Report

When the local project folder is moved from the default Windows user application data directory (e.g., %AppData% or a standard user location) to a path on a different disk or deeper folder structure (e.g., K:\DEVELOPMENT\WebSites), the "on-demand" file content download function is completely disabled.
ㅤ
ㅤ

Environment

• OS: Windows 11 Pro (Fully Updated)
• VS Code Version:
• Version: 1.105.1 (user setup)
  Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
  Date: 2025-10-14T22:33:36.618Z
  Electron: 37.6.0
  ElectronBuildId: 12502201
  Chromium: 138.0.7204.251
  Node.js: 22.19.0
  V8: 13.8.258.32-electron.0
  OS: Windows_NT x64 10.0.26100
• Extension Name: FTP-Simple / humy2833.ftp-simple
• Extension Version: 0.7.6
  ㅤ
  ㅤ

Steps to Reproduce

Initial State (Working):

1. Open a project folder located in a default user location (e.g., %AppData%\Code\User\GlobalStorage\hymy2833.ftp-simple\remote-workspace-temp\CODE_CREATED_BY_FTP-SIMPLE\ProjectA.
2. Connect to the remote server using FTP-Simple.
3. The file/folder placeholders are visible.
4. Action: Double-click a file placeholder.
5. Result (Correct): The file content is downloaded and the file opens for editing.
   ㅤ
   ㅤ

Move & Failure State:

Close VS Code.

1. Move the local project folder (ProjectA) to a new, non-standard location, specifically on a different disk: K:\DEVELOPMENT\WebSites\CODE_CREATED_BY_FTP-SIMPLE\ProjectA.
2. Open VS Code and open the folder from the new location (K:\DEVELOPMENT\WebSites\ProjectA).
3. Connect to the remote server.
4. The file/folder placeholders are correctly downloaded/refreshed and visible in the explorer.
5. Action: Double-click the same file placeholder as in step 1.
6. Result (Incorrect): Nothing happens. The file does not download, the editor does not open, and no error message is displayed in the VS Code window or Output panel.
   ㅤ
   ㅤ

Expected Behavior

Double-clicking a file placeholder in the remote explorer should trigger the file content download and open the editor, regardless of the local project's path or disk location, as long as the local folder is accessible by VS Code.
ㅤ
ㅤ

Possible Root Cause

This behaviour suggests the extension might be relying on a hardcoded path structure or failing to correctly resolve the absolute path on the non-default disk, potentially due to:

Issues with path length limits on Windows (unlikely for K:\DEVELOPMENT\WebSites).

Improper handling of paths beginning with a drive letter (K:) instead of a simple relative path or C:... path.

This is a pity, as the extension becomes useless once projects are moved out of the default user directory.

Thank you for looking into this!