[Issue]: Unexpected EOF on all Node JS downloads
brunbimmer opened this issue · 12 comments
What happened?
When I am running npm install x.y.z? I encounter the following error:
Downloading node.js version 20.6.1 (64-bit)...
Error while downloading https://nodejs.org/dist/v20.6.1/node-v20.6.1-win-x64.zip - unexpected EOF
Extracting node and npm...
Error extracting from Node archive: zip: not a valid zip file
Could not download node.js v20.6.1 64-bit executable.
What did you expect to happen?
I expect to see a successful installation. Was able to install 14.18.1 without a problem and then 20.7.0, but then nothing since then. I am geting unexpected EOF errors.
Whichever version I try to install fails and then shows up in the nvm list, but I am neither able to use the said version nor even uninstall it as it says, it is not installed.
Version
1.1.11 or newer (Default)
Which version of Windows?
Windows 10 (Default)
Which locale?
English (Default)
Which shell are you running NVM4W in?
PowerShell
User Permissions?
Administrative Privileges, Elevated
Is Developer Mode enabled?
Yes
Relevant log/console output
No response
Debug Output
PS C:\Users\U1167100> nvm debug
Running NVM for Windows with administrator privileges.
Administrator: Windows PowerShell
NVM4W Version: 1.1.11
NVM4W Path: C:\Users\U1167100\AppData\Roaming\nvm\nvm.exe
NVM4W Settings: C:\Users\U1167100\AppData\Roaming\nvm\settings.txt
NVM_HOME: C:\Users\U1167100\AppData\Roaming\nvm
NVM_SYMLINK: C:\Program Files\nodejs
Node Installations: C:\Users\U1167100\AppData\Roaming\nvm
Active Node.js Version: v20.7.0
No problems detected.
Find help at https://github.com/coreybutler/nvm-windows/wiki/Common-IssuesAnything else?
No response
Do you have fairly strict antivirus settings? I have encountered people whose environments start quarantining/deleting Node zip files as they're being downloaded (ML virus definitions), which would explain EOF's on newer versions of Node.
Proxies can also impact the download process. So can a mirror server.
You can remove the old versions by deleting their folders from C:\Users\U1167100\AppData\Roaming\nvm.
Aside from checking these aspects of your environment, my recommendation would be to just wait and reinstall. It's possible there's a problem with the source server. That's rare, but it has happened in the past.
This keeps happening, but after some attempts it is succesfull.
@coreybutler No, I don't have any specific strict settings which would cause this to happen.
@freddi301 Interesting and odd at the same time.
@brunbimmer have you tried again today? Every once in a while, the Node source site becomes unavailable. It's possible you just hit one of these maintenance windows. This also happens for brand new releases. It takes some time for the download site to sync with the actual release. That said, Node 20.6.1 has been released long enough that there shouldn't be a problem with it... unless the Node team replaced the file recently.
Had the same issue. Excluding :C/Users/{user}/AppData/Roaming/nvm from antivirus scanning helped the installation to succeed.
I was having this issue when running nvm over a VPN. I disabled the VPN and it ran successfully.
I'm closing this since it doesn't appear to be an issue with NVM4W. @brunbimmer - if you're still struggling with this, let me know and I'll re-open the issue.
Error while downloading https://nodejs.org/dist/v18.17.0/node-v18.17.0-win-x64.zip - unexpected EOF
Extracting node and npm...
Error extracting from Node archive: zip: not a valid zip file
Could not download node.js v18.17.0 64-bit executable.
@Ramdoijad did you found a solution? im still getting the same error
@Ramdoijad did you found a solution? im still getting the same error
did you ever found a solution? I'm going through the same now