You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run any node command, a simple node -v is enough to reproduce
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
Node command should execute and not throw dll error.
What do you see instead?
Windows error dialog:
Title: node.exe - Entry Point Not Found
Body: The procedure entry point GetHostNameW could not be located in the dynamic link library WS2_32.dll.
Button options: OK
Additional information
I have read the docs and I am aware Node.js 14 drops platform support for Windows 7 meaning it is no longer tested and may be broken. However I have a requirement to use Windows 7 so I have tried, successfully, to use 14 .x until I upgraded to 14.18.0 which broke for me. Multiple previously releases of 14.x have worked without issue. Filing this issue for awareness and to see if this was an intentional / known break or something that might be addressed in a future 14 release.
Version
14.18.0
Platform
Microsoft Windows NT 6.1.7601 Service Pack 1 x64
Subsystem
No response
What steps will reproduce the bug?
Run any node command, a simple
node -vis enough to reproduceHow often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
Node command should execute and not throw dll error.
What do you see instead?
Windows error dialog:
Title:
node.exe - Entry Point Not FoundBody:
The procedure entry point GetHostNameW could not be located in the dynamic link library WS2_32.dll.Button options:
OKAdditional information
I have read the docs and I am aware Node.js 14 drops platform support for Windows 7 meaning it is no longer tested and may be broken. However I have a requirement to use Windows 7 so I have tried, successfully, to use 14 .x until I upgraded to 14.18.0 which broke for me. Multiple previously releases of 14.x have worked without issue. Filing this issue for awareness and to see if this was an intentional / known break or something that might be addressed in a future 14 release.