New install of Workbench on new Win 11 PC won't local compile simple sketch

Unable to compile anything.


/bin/bash: C:/Users/Mark: No such file or directory
…/build/ *** "ARM gcc version 10.2.1 or later required, but found ". Stop.
make: *** [C:\Users\Mark Kiehl.particle\toolchains\buildscripts\1.11.0\Makefile:74: compile-all] Error 2

  • The terminal process “C:\Users\Mark Kiehl.particle\toolchains\buildtools\1.1.1\bin\bash.exe ‘-c’, ‘make -f ‘C:\Users\Mark Kiehl.particle\toolchains\buildscripts\1.11.0\Makefile’ compile-all -s’” terminated with exit code: 2.
  • Press any key to close the terminal.

This is a new Win 11 laptop with a new installation of Visual Studio Code v1.72.2. Initially I had a sketch folder ‘Particle’ under my ‘Documents’ folder, but then suspected that was the problem, so I moved it to C:\Particle. I completely uninstalled Visual Studio Code and deleted the following folders:
C:\Users\Mark Kiehl.vscode
C:\Users\Mark Kiehl.particle
C:\Users\Mark Kiehl\AppData\Local\particle

Reinstalled Visual Studio Code and then Particle Workbench. Created a new Particle project in ‘C:\Particle\boron_a\junk_b’. Logged in to Particle. Configured for device. Installed deviceOS@5.1.0 toolchain for boron. Then when I local compile, I experience the error:

/bin/bash: C:/Users/Mark: No such file or directory

(My user folder is C:/Users/Mark Kiehl/…)

I tried all other suggestions I could find, and everything else works fine until a local compile.

“username”: “”,
“workspace”: {
“name”: “junk_b”,
“isWorkspace”: false,
“folders”: [
“location”: “c:\Particle\boron_a\junk_b”,
“hasValidPath”: true,
“settings”: {
“firmwareName”: “deviceOS”,
“firmwareVersion”: “5.1.0”,
“targetDevice”: “boron_a”,
“targetPlatform”: “boron”,
“compileButtonAction”: “localAppDeviceOS”,
“flashButtonAction”: “localAppDeviceOS”,
“disableWelcomeScreen”: false,
“disableDeviceOSOutdatedCheck”: false,
“disableLocalCompilerDirtyCheck”: false,
“enableVerboseLocalCompilerLogging”: false,
“compileDefines”: ,
“customDeviceOSLocation”: “”,
“maxAllowedToolchains”: 4
“files”: [
“cli”: {
“binpath”: “c:\Users\Mark Kiehl\.vscode\extensions\particle.particle-vscode-core-1.15.5\src\cli\bin\windows\amd64\particle.exe”,
“ok”: true,
“version”: “3.5.0”,
“installed”: 1666636582888
“localCompiler”: {
“ok”: true,
“dependencies”: [
“id”: “deviceOS@5.1.0”,
“ok”: true
“id”: “gcc-arm@10.2.1”,
“ok”: true
“id”: “buildtools@1.1.1”,
“ok”: true
“id”: “buildscripts@1.11.0”,
“ok”: true
“id”: “openocd@0.11.0-particle.4”,
“ok”: true
“id”: “deviceOS@4.0.0”,
“ok”: true
“platform”: {
“os”: “windows”,
“type”: “Windows_NT”,
“release”: “10.0.22000”,
“arch”: “x64”,
“path”: {
“key”: “Path”,
“value”: “C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Users\Mark Kiehl\AppData\Local\Microsoft\WindowsApps;C:\Users\Mark Kiehl\AppData\Local\Programs\Microsoft VS Code\bin”,
“entries”: [
“C:\Users\Mark Kiehl\AppData\Local\Microsoft\WindowsApps”,
“C:\Users\Mark Kiehl\AppData\Local\Programs\Microsoft VS Code\bin”
“homeDir”: “C:\Users\Mark Kiehl”,
“particleDir”: “C:\Users\Mark Kiehl\.particle”,
“particleToolchainDir”: “C:\Users\Mark Kiehl\.particle\toolchains”
“env”: {
“ALLUSERSPROFILE”: “C:\ProgramData”,
“APPDATA”: “C:\Users\Mark Kiehl\AppData\Roaming”,
“CommonProgramFiles”: “C:\Program Files\Common Files”,
“CommonProgramFiles(x86)”: “C:\Program Files (x86)\Common Files”,
“CommonProgramW6432”: “C:\Program Files\Common Files”,
“ComSpec”: “C:\Windows\system32\cmd.exe”,
“DriverData”: “C:\Windows\System32\Drivers\DriverData”,
“HOMEPATH”: “\Users\Mark Kiehl”,
“LOCALAPPDATA”: “C:\Users\Mark Kiehl\AppData\Local”,
“NIEXTCCOMPILERSUPP”: “C:\Program Files (x86)\National Instruments\Shared\ExternalCompilerSupport\C\”,
“OneDrive”: “C:\Users\Mark Kiehl\OneDrive”,
“OS”: “Windows_NT”,
“Path”: “C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Users\Mark Kiehl\AppData\Local\Microsoft\WindowsApps;C:\Users\Mark Kiehl\AppData\Local\Programs\Microsoft VS Code\bin”,
“PROCESSOR_IDENTIFIER”: “AMD64 Family 23 Model 104 Stepping 1, AuthenticAMD”,
“ProgramData”: “C:\ProgramData”,
“ProgramFiles”: “C:\Program Files”,
“ProgramFiles(x86)”: “C:\Program Files (x86)”,
“ProgramW6432”: “C:\Program Files”,
“PSModulePath”: “C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules”,
“PUBLIC”: “C:\Users\Public”,
“SESSIONNAME”: “Console”,
“SystemDrive”: “C:”,
“SystemRoot”: “C:\Windows”,
“TEMP”: “C:\Users\MARKKI~1\AppData\Local\Temp”,
“TMP”: “C:\Users\MARKKI~1\AppData\Local\Temp”,
“USERNAME”: “Mark Kiehl”,
“USERPROFILE”: “C:\Users\Mark Kiehl”,
“VBOX_MSI_INSTALL_PATH”: “C:\Program Files\Oracle\VirtualBox\”,
“VSCODE_AMD_ENTRYPOINT”: “vs/workbench/api/node/extensionHostProcess”,
“VSCODE_CODE_CACHE_PATH”: “C:\Users\Mark Kiehl\AppData\Roaming\Code\CachedData\d045a5eda657f4d7b676dedbfa7aab8207f8a075”,
“VSCODE_CWD”: “C:\Users\Mark Kiehl\AppData\Local\Programs\Microsoft VS Code”,
“VSCODE_IPC_HOOK”: “\\.\pipe\012e7699d56f966f1f9787c8374d18fd-1.72.2-main-sock”,
“VSCODE_NLS_CONFIG”: “{"locale":"en-us","availableLanguages":{},"_languagePackSupport":true}”,
“VSCODE_PID”: “15552”,
“windir”: “C:\Windows”
“versions”: {
“node”: “16.14.2”,
“v8”: “”,
“uv”: “1.43.0”,
“zlib”: “1.2.11”,
“brotli”: “1.0.9”,
“ares”: “1.18.1”,
“modules”: “106”,
“nghttp2”: “1.45.1”,
“napi”: “8”,
“llhttp”: “6.0.4”,
“openssl”: “1.1.1”,
“cldr”: “40.0”,
“icu”: “70.1”,
“tz”: “2022b”,
“unicode”: “14.0”,
“electron”: “19.0.17”,
“microsoft-build”: “15825693”
“vscode”: {
“appName”: “Visual Studio Code”,
“appRoot”: “c:\Users\Mark Kiehl\AppData\Local\Programs\Microsoft VS Code\resources\app”,
“machineId”: “2bc38df7f31b6d9d142320908140ec5d144363045063fcdb8f5f416aaa4e477d”,
“sessionId”: “3f0c2789-c165-4049-9c22-a423cae303df1666638225327”,
“version”: “1.72.2”
“extensions”: [
“id”: “ms-vscode-remote.remote-wsl-recommender”,
“version”: “0.0.17”
“id”: “ms-vscode.js-debug”,
“version”: “1.72.1”
“id”: “ms-vscode.js-debug-companion”,
“version”: “1.0.18”
“id”: “ms-vscode.vscode-js-profile-table”,
“version”: “1.0.3”
“id”: “marus25.cortex-debug”,
“version”: “1.6.6”
“id”: “ms-vscode.cmake-tools”,
“version”: “1.12.27”
“id”: “ms-vscode.cpptools”,
“version”: “1.12.4”
“id”: “ms-vscode.cpptools-extension-pack”,
“version”: “1.3.0”
“id”: “ms-vscode.cpptools-themes”,
“version”: “1.0.0”
“id”: “particle.particle-vscode-core”,
“version”: “1.15.5”
“id”: “particle.particle-vscode-pack”,
“version”: “1.15.5”
“id”: “particle.particle-vscode-snippets”,
“version”: “1.15.5”
“id”: “particle.particle-vscode-theme”,
“version”: “1.15.5”
“id”: “twxs.cmake”,
“version”: “0.0.17”

Windows 11 Home v 21H23

My user folder is C:/Users/Mark Kiehl/

sadly, spaces within file paths are not supported due to limitations in the underlying make build system:

No, my project path is now: C:\Particle\

Turning on logging, the problem seems to be related to the toolchain:

Executing task: make -f ‘C:\Users\Mark Kiehl.particle\toolchains\buildscripts\1.11.0\Makefile’ compile-all


cd “C:/Users/Mark Kiehl/.particle/toolchains/deviceOS/5.1.0/modules” && make all
make[1]: Entering directory ‘/cygdrive/c/Users/Mark Kiehl/.particle/toolchains/deviceOS/5.1.0/modules’
/bin/bash: C:/Users/Mark: No such file or directory

I don’t know how to change the Particle Workbench installation so it doesn’t install anything into my user folder.

I looked over all of the similar posts and tried everything, but I still have the same problem. Changing my login name to remove the space is NOT an acceptable solution because it would require me to re-install nearly every other app (I spent two days configuring my new laptop). What I need is a way to install Particle Workbench into a different folder than under \Users[my name].

I have a project to work on for a client and no way to move forward.

My prior laptop had Windows 10, VSC 1.67.2, and Workbench v1.14.11 and worked without an issue.

ash-4.4$ make -f $PARTICLE_MAKEFILE help
make: C:/Users/Mark: No such file or directory
make: *** No rule to make target ‘C:/Users/Mark’. Stop.

bash-4.4$ echo $PARTICLE_MAKEFILE
C:/Users/Mark Kiehl/.particle/toolchains/buildscripts/1.11.0/Makefile
bash-4.4$ echo $PATH
/cygdrive/c/Users/Mark Kiehl/.vscode/extensions/particle.particle-vscode-core-1.15.5/src/cli/bin/windows/amd64:/cygdrive/c/Users/Mark Kiehl/.particle/toolchains/gcc-arm/10.2.1/bin:/usr/bin:/cygdrive/c/Users/Mark Kiehl/.particle/toolchains/openocd/0.11.0-particle.4/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Users/Mark Kiehl/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Users/Mark Kiehl/AppData/Local/Programs/Microsoft VS Code/bin

bash-4.4$ which particle
/cygdrive/c/Users/Mark Kiehl/.vscode/extensions/particle.particle-vscode-core-1.15.5/src/cli/bin/windows/amd64/particle

bash-4.4$ which arm-none-eabi-gdb
/cygdrive/c/Users/Mark Kiehl/.particle/toolchains/gcc-arm/10.2.1/bin/arm-none-eabi-gdb

bash-4.4$ arm-none-eabi-gdb --version
GNU gdb (GNU Arm Embedded Toolchain 10-2020-q4-major)
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

SUGGESTION: Add something to Particle Benchmark install that checks to see if Windows user profile path has a space in it. If found, warn the user. That is the minimum that should be implemented.

I tried changing my Windows 11 user profile folder name to remove the space. It is an involved process that requires me to create a separate administrator user. In the end, I WAS UNABLE TO DO THE CHANGE, and then I could not get access to my Windows account.

Fortunately, I created a system restore point prior to this disaster, and used that to recover my account. I guess the only option is to create another user account with a name that doesn’t have a space in it and use that account solely for working with Particle Workbench.

Seriously disappointing.

1 Like

Hey, sorry about your issues.
I wonder if a symlink can help here. Not sure yet how, and not even sure if Windows today supports them in a proper way.

Maybe if you create a symlink of c:\Users\Mark Kieh that points to c:\Users\Mark this could work?
I guess you will need to move around/modify particle workbench config files.


acknowledging this isn’t an ideal situation, the best, most-reliable option is to create a new local user profile without a space:

again, i understand that isn’t always possible or easy.

i can’t commit to a timeline for (hopefully) obvious reasons but know that we are aware of the issue and intend to address it ASAP.

thanks for the report and apologies for the bumps :pray: