Repository navigation
node.exe 8.7.0 and above does not work in Windows NanoServer container #16603
Description
Activity
cc @nodejs/platform-windows
Just tested the binaries in Windows Server 1709 images (microsoft/windowsservercore:1709 and microsoft/nanoserver:1709) and all versions 8.7.0, 8.8.0 and 8.8.1 work there.
I have to check my older Windows Server 2016 setup again why it didn't work multiple times.OK, I ran another test on a fresh Window Server 2016 in Azure, tested with several microsoft/nanoserver:10.0.14393.1066 .. microsoft/nanoserver:10.0.14393.1770 (latest) and I can reproduce the problem. Node.exe 8.7.0 ... 8.8.1 don't work in nanoserver images for the LTS channel of Windows Server 2016.
It seems that the newer images for the Semi-annual channel of Windows Server 1709 don't have this problem.
Ohh boy. This is not going to be fun to debug 🤦♂️
@StefanScherer thank you for the detailed information though 👍 Do you by any chance know where we can find something changelog like between 1770 and 1790?@refack Oh the diff between 10.0.14393.1770 and 10.0.16299.19 = current release of Windows Server 1709 could be a little longer :-) It's not just 20 releases I guess.
@StefanScherer so it might be easier to figure this out from node's side (although I already have an obvious suspect, the bump in libuv from 1.14.1 to 1.15.0 https://github.com/libuv/libuv/blob/v1.x/ChangeLog)
P.S. node exits with 0xC0000139 {Entry Point Not Found} so it seems like we started using a new API that doesn't exists in 10.0.14393.1770
API diff:
newAcquireSRWLockExclusive,-,-,-,kernel32.dll DebugBreak,x,-,-,kernel32.dll DispatchMessageA,x,-,-,user32.dll GetMessageA,-,-,-,user32.dll InitializeConditionVariable,-,-,-,kernel32.dll ReleaseSRWLockExclusive,-,-,-,kernel32.dll SetWinEventHook,x,-,-,user32.dll SleepConditionVariableSRW,-,-,-,kernel32.dll TranslateMessage,-,-,-,user32.dll WakeAllConditionVariable,-,-,-,kernel32.dll WakeConditionVariable,-,-,-,kernel32.dlldropped:
VirtualProtect,x,-,-,kernel32.dllMost probably
SetWinEventHook@refack I also tried older nanoserver:10.0.14393.x images and it's the same there.
But with that list of API changes in Node.js maybe @PatrickLang can have a short look ^^ and give us a hint which might cause problems?
Hm, I remember the NanoServer API scan tool. Oh I still have a Docker image of that.
FROM stefanscherer/nanoserverapiscan:onbuild ADD https://nodejs.org/dist/v8.6.0/win-x64/node.exe node-8.6.0.exe ADD https://nodejs.org/dist/v8.8.1/win-x64/node.exe node-8.8.1.exe
docker build -t scan . docker run scanBut it doesn't show any errors.
If @refack's assessment is correct, it's likely from libuv/libuv#1408 (since 8.7 upgraded libuv to 1.15.0)- @bzoz can you take a look, we likely need to GetProcAddress of SetWinEventHook rather than statically linking against it if the API is not present Windows NanoServer
16 remaining items
Reopening because the issue isn't fixed till this patch lands in v8.x and v6.x.
libuv 1.15.0 is slated to land on v6.x on tuesday. Should we back it out or float this patch?
sorry for my ignorance but that is not yet landed (to be backed out) right?
@MylesBorins meant either back out libuv 1.15.0, or float this patch
Not sure if possible, but if libuv could include that patch in a 1.15.1, that would be better than than floating a patch.
I'd rather we float the patch than revert libuv 1.15.0 if possible.
Reacted by Gireesh Punathil and Stefan Scherer- added a commit that references this issue
on Nov 3, 2017 cherry-pick in #16724
Good job everyone 🥇 7 days from report to fix, including a roundtrip through libuv.
Reacted by Gireesh PunathilReacted by Hitesh KanwathirthaI want to thank you all involved resolving this so quickly. Can‘t wait for the next release.
Reacted by Gireesh Punathil- added a commit that references this issue
on Apr 11, 2026 - added a commit that references this issue
on Jul 27, 2026
I have problems running the newer versions of Node 8 in a Windows Nanoserver Container:
Version:
8.7.0, 8.8.0, 8.8.1
Platform:
Windows
Subsystem:
Windows Nanoserver Container running in Windows 10 / Windows Server 2016
To reproduce the problem, just download the node.exe of specific versions in a Windows NanoServer container:
Then inside the container:
Beginning with Node 8.7.0 this stops working: