Hello, I'm having an issue with Kolide launcher:

{"caller":"launcher.go:133","err":"launching osquery instance: starting instance: could not calculate osquery file paths: extension path does not exist: C:\\Program Files\\Kolide\\Launcher-launcher\\bin\\osquery-extension.exe: CreateFile C:\\Program Files\\Kolide\\Launcher-launcher\\bin\\osquery-extension.exe: El sistema no puede encontrar el archivo especificado.","level":"info","msg":"interrupted","ts":"2022-08-02T16:42:40.1333351Z"}

Here's my build command

.\build\package-builder.exe make --hostname <http://osquery.dpsit.gba.gob.ar:443|osquery.dpsit.gba.gob.ar:443> --enroll_secret ******** --targets windows-service-msi --insecure --output_dir .

What version are you building?

Osquery or Kolide Launcher?

Launcher

branch: master revision: 36ff746fa38221c6d9ac938aff3aeea6d2fb4fa1 build date: 2022-08-02 go version: go1.18.5

Is that package builder or launcher?

i'm sorry, package-builder

On windows, what does

launcher debug

do?

I don't understand, i've cloned the repo and ran make deps make build make package-builder

Right, so you now have a

build/launcher.exe

from

36ff746fa38221c6d9ac938aff3aeea6d2fb4fa1

. But that’s not what package-builder uses. Instead, package-builder downloads the current stable launcher. (which is not that) On the host you installed that MSI, launcher will be somewhere in

C:\Program Files\Kolide\

Yes, I have that folder in Program Files

But I suspect this is skew between the stable luncher (0.11.26) and the head version of package-builder (0.12.1)

So launcher is behind package-builder?

No. Stable releases are behind the git head.

Right

Okay! I have now declared 0.12.1 stable. Would you try a new MSI and seeing if you still have that issue?

It works now, thanks!

Nice. Almost certainly that skew that. Glad it’s working