Incorrect display when using -CLI in a Admin/non-Admin Command Prompt

[click-click]

When running net session in an admin command prompt, no output is displayed other than 2 command prompts. A non-admin session also shows 2 prompts with the output on the 2nd prompt.
`Admin Session
U:\SwApps\Tools4Maint\CmdElevation\CmdT>cmdt_x64.exe -cli net session

U:\SwApps\Tools4Maint\CmdElevation\CmdT>
U:\SwApps\Tools4Maint\CmdElevation\CmdT>

Non-Admin Session
U:\SwApps\Tools4Maint\CmdElevation\CmdT>cmdt_x64.exe -cli net session

U:\SwApps\Tools4Maint\CmdElevation\CmdT>
U:\SwApps\Tools4Maint\CmdElevation\CmdT>There are no entries in the list.`

[wesmar]

cmdt_x64.zip

As I mentioned on the MDL forum, I found a little time and changed the way CLI/GUI is prioritized. I was able to reproduce the bad prompt/output ordering with:

cmdt_x64.exe -cli net session

The root cause was the hybrid GUI/CLI behavior of the x64 build. The executable was being used as a GUI-subsystem binary while trying to behave like a blocking console tool for -cli. In that mode, cmd.exe does not wait for the process the same way it waits for a real console executable, so the prompt could be printed before the elevated command finished writing its output. The previous prompt “nudge” workaround could also create the extra blank prompt/Enter behavior you saw.

I reworked the x64 CLI path so that:

• cmdt_x64.exe -cli <command> is now handled as a real console-mode invocation.
• CLI output is routed through the relay/capture path for both admin and non-admin callers.
• The relay path is guarded so the internal -cli -outfile ... child does not recurse.
• The old artificial prompt/Enter workaround is no longer used for the x64 CLI path.
• Running cmdt_x64.exe with no arguments still opens the GUI. Since the x64 binary now needs to be console-subsystem for proper CLI behavior, the no-argument GUI launch starts a detached internal -gui child and the parent exits immediately.

Expected behavior after this build:

cmdt_x64.exe -cli net session

should print the command output before returning to a single prompt, in both elevated and non-elevated command prompts.

Please also test redirection/piping:

cmdt_x64.exe -cli net session > out.txt
cmdt_x64.exe -cli net session | findstr /i entries

One visible side effect: when launching the GUI with no arguments, a console window may flash briefly because the x64 binary is now a console-subsystem executable. The GUI still opens normally; the flash is the tradeoff for making the same single EXE behave correctly as a blocking CLI tool.

I am attaching a test ZIP build for validation before committing the full set of changes.

[click-click]

I will mainly be using this for my batch files. Seems to be working now testing from the 2 differnt command prompts types. No extensive testing yet. I will let you know if anything else breaks. Thanks for updating