Command Prompt closes

[dezorianguy]

When I excecute stadiacontroller.exe a short command prompt window appears (accompanied by a windows connecting jiggle sound), and the windows closes immediately after than. Earlier today it worked fine (the cmd window stayed opened), but after a fresh Windows 10 Pro installation, it just closes and my controller isn't working in games anymore.
Any ideas?

[71]

Is ViGEm installed on your fresh installation?

[dezorianguy]

Is ViGEm installed on your fresh installation?

ViGEmBusSetup_x64.msi is installed. I did it before and it worked with the old Windows 10 installation.
It almost feels like Windows 10 is closing the cmd window due to some setting? Like a pesky pop-up that's being prevented.
It is like a .bat file from old old games that would be closed the same way by Windows. Like with some compatibilty issue?
I disabled Windows 10 antivirus, etc. but maybe there is another setting that is prventing from closing...hmm..

[71]

Got it. You could try starting your own cmd.exe prompt and executing stadiacontroller.exe from there; if there is an error, it should be displayed and the prompt won't close on its own before you can read it.

[dezorianguy]

Got it. You could try starting your own cmd.exe prompt and executing stadiacontroller.exe from there; if there is an error, it should be displayed and the prompt won't close on its own before you can read it.

Yeah, good idea. I got an error indeed.

"Overlapping E/A-process in progress/the working."

[71]

I'm not sure about this. I remember having a bug about "overlapping" a while ago, but can't remember exactly what it was or how it was fixed. If I had to guess, I'd say some other process is taking exclusive control of the emulated X360 controller. Perhaps Steam?

Edit: ah, looks like #4.

[dezorianguy]

Nevermind, it works now. Maybe one of that Windows Updates I did yesterday did the trick. Who knows.