Why not run the exe file of the game?

Good time of day. Trying to write a launcher for the game on Electron. Here is the code:
const child = exec('C:/Games/папка games/something.lnk', callback);

And it works, the game runs, all is well. But if I try instead of the shortcut (.lnk) to run through the executable (.exe):
const child = exec('C:/Games/папка games/something Tamaha', callback)
the game tries to start, but after a few seconds the window closes. A listener to the exit event on the child after departure writes
child process exited with code 3221225477 and signal null

In the following error
Error: Command failed: C:\Games\папка games\something timehe

 at ChildProcess.exithandler (child_process.js:308)
 at ChildProcess.emit (events.js:203)
 at maybeClose (internal/child_process.js:1021)
 at Process.ChildProcess._handle.onexit (internal/child_process.js:283)
and nothing else interesting. execFile, spawn instead of exec do not work. Simple programs (excel, calc, cmd) launched through the exe and work, and game in any.
Win 10 system. Node 12.14.
April 4th 20 at 00:35
1 answer
April 4th 20 at 00:37
the problem in setting the cwd (working directory)
When you create a shortcut to windows Explorer (and many other file managers) this parameter is prescribed in the label default to the folder containing the specified .exe
The nod by default, this parameter is taken from the process.cwd()
which corresponds to the working directory of Your node process

I don't fully understand what it is in principle
it sets the "working directory of process", all relative paths used in the startup program will be calculated relative to this

Find more questions by tags Node.js