possibility of running the app from cmd no gui.

[RESDXChgfore9hing]

Describe the bug in windows when you open a cmd and run explorer.exe it will keep the cmd open and lock the input*. i suspect it is due to some main thread waiting or something. In contrast if you try some other app like notepad.exe it will not wait for the gui to fully close and you can just exit the cmd or type a new command

Is there a way we can make it not locking? can we as users give some flag or do something in setting?

To Reproduce Steps to reproduce the behavior:

1. open cmd.exe
2. run explorer.exe
3. see the cmd locked
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Crashes Please attach the associated crash dump. This file should be created in %temp% and be named something like Explorer++1.4.0.0-11102020-194414.dmp. Not attaching a crash dump may make it significantly more difficult to diagnose the cause of a crash.

Screenshots If applicable, add screenshots to help explain your problem.

Version (please complete the following information):

• Explorer++ version: [e.g. 1.4.0.1616 dev (64-bit build)]
• OS: [e.g. Windows 10]

Additional context Add any other context about the problem here.

[derceg]

I can't reproduce this. Starting Explorer++ from a cmd instance results in the next prompt being immediately shown.

What version of Explorer++ are you using and which version of Windows?