A command that expects a typed answer may not work as intended when its input channel is closed. With Sudo for Windows, that can be a deliberate configuration choice rather than a broken terminal or keyboard.

First read the command’s own instructions. Determine whether it really needs administrator rights, whether it asks interactive questions and where its output should appear. Do not add elevation simply because an ordinary command returned an unfamiliar error.

Distinguish the three modes

Microsoft supports Sudo for Windows on Windows 11 version 24H2 and later. Its current documentation places the enablement and mode controls under Settings, System, Advanced. Inspect the existing setting before changing it.

In a new window is the default: the elevated command runs in another window. Input closed keeps the process in the current window but closes its console input. Inline keeps the current window and allows the elevated process to receive console input.

Input closed therefore does not suit a task that requires responses from that console. A new-window workflow may meet the requirement without changing every later sudo invocation to Inline.

Treat shared input as a privilege decision

Microsoft recommends the default new-window mode unless the risks of the alternatives are understood. Inline can let an unelevated process send input to the elevated process in the same console; Input closed reduces that particular exposure by closing input. Both shared-window modes have documented security considerations.

The elevation still goes through User Account Control. Read the prompt in the context of the command you deliberately started. A familiar terminal window is not itself approval for an unrelated privileged action.

For a supported administrative task, record the chosen mode alongside the command instructions. Check that prompts appear where expected and that the command reaches its documented completion result. Avoid testing with a destructive command just to see which window opens.

If the workflow cannot operate under the chosen boundary, stop and revisit its requirements. Keep a deliberate configuration that serves a known task instead of making permanent privilege changes while chasing an input symptom.

Sources: Microsoft Sudo for Windows.