`process.title` on Windows returns different value in v24.16.0 vs 24.15.0

[jfeingold35]

Version

v24.16.0

Platform

Microsoft Windows NT 10.0.26200.0 x64

Subsystem

No response

What steps will reproduce the bug?

STR:

1. On Windows, install node v24.15.0 either directly or through nvm-windows.
2. Open Powershell and run node
3. process.title, and observe that the result is something like "Windows Powershell".
4. Install node v24.16.0.
5. Repeat steps 2-3

How often does it reproduce? Is there a required condition?

It happens every time.

What is the expected behavior? Why is that the expected behavior?

EXPECTED: The output should be "Windows Powershell" as it was in every version prior to this. Otherwise, I'm unsure of how Node running on a Windows machine can know whether it was instantiated in Powershell or CMD.

What do you see instead?

ACTUAL: The output will be the path to 'node.exe'.

Additional information

No response

[MikeMcC399]

I can reproduce. I used the msi packages to avoid any interaction with nvm-windows

Execute: node -p "process.title"

Windows 11 25H2

Terminal	Node.js 24.15.0	Node.js 24.16.0
Git Bash	MINGW64:/c/Users/mikem	C:\Program Files\nodejs\node.exe
Windows PowerShell	Windows PowerShell	C:\Program Files\nodejs\node.exe
PowerShell	PowerShell	C:\Program Files\nodejs\node.exe
cmd	Command Prompt - node -p "process.title"	C:\Program Files\nodejs\node.exe

and just for comparison:

Ubuntu 24.04 LTS

Terminal	Node.js 24.15.0	Node.js 24.16.0
bash	node	node

[richardlau]

Suspect this is libuv/libuv#5023 included in the libuv update.

cc @StefanStojanovic

[MikeMcC399]

Confirmed with bisect to 493ac40e12 from #61829 (which was also landed into Node.js 26.0.0)