Description:
After successfully installing Node.js version 24.1.0 using nvm (Node Version Manager) on a Windows system, attempting to execute node.exe results in an "Entry Point Not Found" error. The error message specifically indicates that "The procedure entry point GetThreadDescription could not be located in the dynamic link library C:\Users\administrator\AppData\Local\Programs\nvm\v24.1.0\node.exe." This suggests a potential compatibility issue or missing dependency between the Node.js executable and the Windows operating system, or a corrupted installation specifically affecting this entry point.
Steps to Reproduce:
Install NVM for Windows: Ensure nvm is installed and configured correctly on a Windows machine.
Install Node.js v24.1.0: Open a command prompt or PowerShell and execute the command:
nvm install 24.1.0
Use Node.js v24.1.0: Switch to the newly installed version:
nvm use 24.1.0
Attempt to Run Node.js: Try to execute node.exe, for example, by checking its version:
node -v
Expected Behavior:
The node -v command should execute successfully and display the installed Node.js version (v24.1.0), indicating that Node.js is running correctly.
Actual Behavior:
An "Entry Point Not Found" error dialog appears with the following message:
node.exe - Entry Point Not Found
The procedure entry point GetThreadDescription could not be located
in the dynamic link library
C:\Users\administrator\AppData\Local\Programs\nvm\current\nodejs\node.exe.
(Note: The path in the error message might dynamically show ...\nvm\v24.1.0\node.exe or ...\nvm\current\nodejs\node.exe depending on NVM's symlinking.)
Environment:
Node.js Version: 24.1.0
NVM for Windows Version: (Please provide your specific NVM version if known, e.g., 1.1.11)
Operating System: Windows Server 2019
Command Line Tool: Command Prompt or PowerShell
Additional Context:
This issue prevents Node.js applications from running and seems to be related to a low-level API call (GetThreadDescription) that might be unavailable or incorrectly linked on certain Windows configurations or specific Node.js builds.
Description:
After successfully installing Node.js version 24.1.0 using nvm (Node Version Manager) on a Windows system, attempting to execute node.exe results in an "Entry Point Not Found" error. The error message specifically indicates that "The procedure entry point GetThreadDescription could not be located in the dynamic link library C:\Users\administrator\AppData\Local\Programs\nvm\v24.1.0\node.exe." This suggests a potential compatibility issue or missing dependency between the Node.js executable and the Windows operating system, or a corrupted installation specifically affecting this entry point.
Steps to Reproduce:
Install NVM for Windows: Ensure nvm is installed and configured correctly on a Windows machine.
Install Node.js v24.1.0: Open a command prompt or PowerShell and execute the command:
nvm install 24.1.0
Use Node.js v24.1.0: Switch to the newly installed version:
nvm use 24.1.0
Attempt to Run Node.js: Try to execute node.exe, for example, by checking its version:
node -v
Expected Behavior:
The node -v command should execute successfully and display the installed Node.js version (v24.1.0), indicating that Node.js is running correctly.
Actual Behavior:
An "Entry Point Not Found" error dialog appears with the following message:
node.exe - Entry Point Not Found
The procedure entry point GetThreadDescription could not be located
in the dynamic link library
C:\Users\administrator\AppData\Local\Programs\nvm\current\nodejs\node.exe.
(Note: The path in the error message might dynamically show ...\nvm\v24.1.0\node.exe or ...\nvm\current\nodejs\node.exe depending on NVM's symlinking.)
Environment:
Node.js Version: 24.1.0
NVM for Windows Version: (Please provide your specific NVM version if known, e.g., 1.1.11)
Operating System: Windows Server 2019
Command Line Tool: Command Prompt or PowerShell
Additional Context:
This issue prevents Node.js applications from running and seems to be related to a low-level API call (GetThreadDescription) that might be unavailable or incorrectly linked on certain Windows configurations or specific Node.js builds.