[BUG]: Activating extension failed

[mbomb007]

Describe the bug
After updating VS Code to 1.222.0, I noticed another extension failed to load, and while checking the error output for extensions, noticed this one did too.

To Reproduce
Steps to reproduce the behavior:

1. Start VS Code
2. Click on Output
3. Set dropdown to Extension Host or Extension Host (Remote) if using WSL
4. See error

2026-05-28 08:52:09.122 [error] Activating extension ycodetech.automatic-comment-blocks failed due to an error:
2026-05-28 08:52:09.122 [error] Error: ENOENT: no such file or directory, scandir '/mnt/c/Users/REDACTED/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions'
at Object.readdirSync (node:fs:1590:26)
at Configuration.readExtensionsFromDirectory (/home/REDACTED/.vscode-server/extensions/ycodetech.automatic-comment-blocks-1.1.15/out/src/configuration.js:424:12)
at Configuration.findAllLanguageConfigFilePaths (/home/REDACTED/.vscode-server/extensions/ycodetech.automatic-comment-blocks-1.1.15/out/src/configuration.js:276:51)
at new Configuration (/home/REDACTED/.vscode-server/extensions/ycodetech.automatic-comment-blocks-1.1.15/out/src/configuration.js:70:14)
at activate (/home/REDACTED/.vscode-server/extensions/ycodetech.automatic-comment-blocks-1.1.15/out/src/extension.js:19:27)
at Ld._callActivateOptional (file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:506:18591)
at Ld._callActivate (file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:506:18301)
at file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:506:16275
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async _b._activate (file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:502:16021)
at async _b._waitForDepsThenActivate (file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:502:15963)
at async _b._initialize (file:///home/REDACTED/.vscode-server/bin/6a49527b96e326fe62fbdb56f60e16877c9aa724/out/vs/workbench/api/node/extensionHostProcess.js:502:15330)

Expected behavior
Extension should load and work

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

Perhaps the issue for the other extension is similar: Gruntfuggly/todo-tree#925

Please attach the Auto Comment Blocks Output channel debug text file.

debug.txt

[yCodeTech]

With vscode changing the paths willynilly as seen in the todo-tree extension, I suspect your error is also caused by a problematic path change.

Interestingly, I've not had any issues with this extension on my work's laptop on Windows 11. I'll have to do some digging and test on WSL.

[yCodeTech]

As this comment on the todo-tree extension states, vscode changed it's installed directory to include the commit hash which obvs changes every update.

What this extension does is extracts the install directory from the VSCODE_CWD environment variable and then appends resources/app/extensions to it.

The line in question:

auto-comment-blocks/src/extensionData.ts

Line 120 in 60c6b65

this.extensionDiscoveryPaths.set("WindowsBuiltInExtensionsPathFromWsl", path.join(process.env.VSCODE_CWD!, "resources/app/extensions"));

But this variable points to the root directory ie. c/Users/REDACTED/AppData/Local/Programs/Microsoft VS Code/, so then when the extension adds the last part of the path, which used to be the correct path, now errors because the path is no longer valid. It's worth noting that this only happens on WSL. For Windows the extension uses a different variable.

I will have to find a way to reliably extract the commit hash so the path is valid.