wslpath | wslpath - Converts Unix and Windows format paths in WSL

Check if this configuration might work in your case:

I managed to get it working using the built-in wslpath command which comes with new WSL versions!

My git config on WSL linux side:

It looks like I didn't install the package "numactl" for some reason.

Just double check if you have those packages installed with (On Archbased)

"Desktop/" doesn't actually resolve to a folder. Try the following:

Since you have only one path you don't need arrays. Spaces inside paths are handled correctly as long as you quote your variables.

_{Actually, splitting the path into an array of words would cause information loss. You would not know if the array (a b) was originally a b (one space) or a b (two spaces). Also, you don't need eval to split a variable into words. array=($var) is the way to go.}

The problem here is that Windows pastes paths with spaces by surrounding it in double quotes. That is, if you drag'n'drop C:\a you get the string C:\a, but if you drag'n'drop C:\a b you get "C:\a b". These quotes are not interpreted by bash as they are only input and not part of your script. wslpath does not interpret these quotes either. Instead wslpath '"C:\a b"' looks for a file named literally a b" residing on drive "C:. We have to manually remove the quotes that Windows' drag'n'drop inserted.

I think you have to do some additional escaping on the backslashes that are produced by wslpath. The code below works for me, meaning it opens the correct directory in Windows Explorer.

Note: it does still throw the error you mentioned, which I think is due to the way node exits rather than anything wrong w/the execution of explorer.exe; I'm not a node expert by any stretch.

You might need to set up your WSL again or upgrade to WSL2. Here is a helpful link: https://docs.microsoft.com/en-us/windows/wsl/install-win10

Or try this link: https://code.visualstudio.com/docs/remote/wsl-tutorial#:~:text=Run%20Terminal%20%3E%20New%20Terminal%20(Ctrl,VS%20Code%20running%20on%20Windows. It's mostly for running Python on vscode, but it might work if you follow the 'Intergrated Terminal' steps.

The problem was because of the default terminal in VSCode. So I had to change that to Command Prompt. To do that, just press F1 in VSCode and type “Terminal: Select Default Shell”, and then select Command Prompt.

Hope this helps.

Try this:

The Windows Task Scheduler allows you to specify a user to run as (for privilege reasons), but does not give you the environment (PATH and other environment variables) that are configured for that user.

So, when running programs from the Windows Task Scheduler, it's important to not make any assumptions about what's in the environment (particularly the PATH). If my program depends on certain things in the environment, I will sometimes change my Task to be a .BAT file that first sets up the environment as needed and then launch my program from there.

Among other things, the simplest way to not rely on the path is to specify the full path to the executable you are running rather than assuming it will be found in the path somewhere. But, you also need to make sure that your executable can find any other resources it might need without any environment variables or you need to configure those environment variables for it before running.