Constant ENOENTs

[ilyadreamix]

Extension version: 0.8.1
Buf version: 1.63.0
OS: Windows

Autocomplete and semantic highlighting are not working. Whenever I try to execute any command from the Command Palette (e.g., "Buf: List modules in workspace"), the following error appears in the logs:

2026-01-16 22:26:42.544 [error] Error executing args config,ls-modules in /c:/Users/IlyaDreamix/project: Error: spawn c:\Users\IlyaDreamix\AppData\Roaming\Code\User\globalStorage\bufbuild.vscode-buf\v1.63.0\buf.exe ENOENT

The error persists regardless of the Buf installation method. It seems the extension cannot find or access the binary at the specified path.

[stefanvanburen]

hey @ilyadreamix — just to check, does the binary exist at that directory (c:\Users\IlyaDreamix\AppData\Roaming\Code\User\globalStorage\bufbuild.vscode-buf\v1.63.0\buf.exe)?

[ilyadreamix]

It does. Also, as I've mentioned, this errors persists even after changing the installation method (for example to WinGet)

[stefanvanburen]

@ilyadreamix I unfortunately don't have a Windows machine to test, but just to check: can you run e.g. c:\Users\IlyaDreamix\AppData\Roaming\Code\User\globalStorage\bufbuild.vscode-buf\v1.63.0\buf.exe --version?

[ilyadreamix]

Yeah, I can

[stefanvanburen]

@ilyadreamix thanks for confirming! we'll look into this. (It surprises me to see /c:/Users/IlyaDreamix/project path with forward-slashes on windows, so maybe we're missing a path conversion somewhere?)

[stefanvanburen]

hey @ilyadreamix — as of the latest 0.8.11 version (available in the VS Code Marketplace) we should no longer be calling ls-modules as a part of the extension; can you try upgrading to that version and confirm that you don't see any other issues?

Going to close this out assuming the issue is fixed with the upgrade, but please let us know if you're seeing any other issues.

[ilyadreamix]

Still getting ENOENTs.

[ilyadreamix]

Also, errors/warnings highlighting doesn't work

[stefanvanburen]

@ilyadreamix can you upgrade to the latest buf (1.64.0) and make sure you're running the latest version of the extension?

[ilyadreamix]

Tried that, doesn't seem to work

[ilyadreamix]

Maybe something is wrong with my setup?

buf.gen.yaml:

version: v2
managed:
  enabled: true

plugins:
  - remote: buf.build/protocolbuffers/go
    out: generated/proto
    opt: paths=source_relative
  - remote: buf.build/connectrpc/go
    out: generated/proto
    opt: paths=source_relative

buf.work.yaml:

version: v1
directories:
  - proto

buf.yaml:

version: v1
name: buf.build/organization/project
deps:
  - buf.build/bufbuild/protovalidate
lint:
  use:
    - STANDARD
breaking:
  use:
    - FILE

[stefanvanburen]

@ilyadreamix I'd probably try to upgrade to a v2 buf.yaml, which should be completely automated if you just run buf config migrate. Let me know if that helps.

[ilyadreamix]

Didn't help 🥲

[stefanvanburen]

@ilyadreamix did that at least upgrade you to a new version: v2 buf.yaml (and remove your buf.work.yaml)?