I had installed nodejs on Windows 10 Pro PC. The drive it was installed in failed and is no longer accessible. I sent it away for data recovery attempt, but it's now gone, not even connected.
I created a restore point and went to NodeJS site, downloaded the installer anew, and tried to re-install it.
The installer looks for that original installation and immediately responds: "Invalid Drive: O:" (the old location). It then immediately quits.
What can I do to re-install it? I can't uninstall it or do anything else (change, or repair). They all give the same message and quit.
Can I uninstall it from the command prompt? Or do a new installation that way?
You can try by editing the following registry value
HKEY_LOCAL_MACHINE\SOFTWARE\Node.js
There you will find an InstallPath property. Rename the drive to a valid one and then try to install node again.
Also remove Node from your PATH variable
Related
I installed the latest nvm Windows cli tool; and when I try to run nvm install lts it shows "Downloading..." then "Extracting..." and freezes there. Never errors, but never moves on, either. If I kill the process and do nvm list, it lists 16.15.0. But if I say nvm use 16.15.0, or nvm uninstall 16.15.0, it says it isn't installed.
I've tried uninstalling nvm and starting over from scratch; same result every time. How do I get past 'Extracting'?
Ok this was a bizarre problem and solution.
Looks like my (work) laptop had previously had win-zip or 7-zip installed, but when it was uninstalled, it didn't re-associate zip files with Windows Explorer.
That meant that the option to click Extract All on a zip file, even manually, was grayed out/disabled. I followed the instructions here: to re-associate .zip files with Windows Explorer:
START menu > Settings (the cog) > Apps > Default Apps. Scroll to the bottom
of that list and look for "Choose default apps by file type". Then
scroll down that until you find ".ZIP" make sure the default is
selected to "Windows Explorer".
I installed node.js to work on a discord bot with VSCode but it didn't work.
I reinstalled it but ticked the 'install chocolatey' box this time, halfway through the installation I got 3 trojan alerts from my AV, and cancelled the installation.
Since then, I have been unable to uninstall, repair or reinstall Node.JS, through the Windows 10 uninstall function or from the Node.JS .msi file.
Each time I try, I get the same error message:
"The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed."
I've removed all instances of Node.JS from my program files and %appdata%, I've ensure the Installer Service is running, and yet the Node.JS application still shows in the Uninstall Tool and when I try to uninstall / modify / reinstall, it shows the same error, and seems to think it's still installed on my system! Not even Node.JS commands work in my CMD!
I've got no idea how to fix this, and I don't want to use glitch anymore to write my bot, so please help- or it seem's I'll have to factory reset my PC and hope that resolves the issue.
Thanks in advance, guys.
Godspeed.
EDIT: I tried installing a newer version hoping it would overwrite old Node.JS files. Didn't work. Issue still occurring.
Do these:
Open command prompt as Administrator and run /sfc scannow. It will scan and replace corrupted files.
Restart your PC when the scan is done.
I need help reinstalling node.js but I keep this error when I uninstall the previous node
The Windows Installer Service could not be accessed.
This can occur if you are running Windows in Safe mode or if the Windows Installer is not correctly installed
I then try reinstalling msiexec.exe to see if I can fix the error in the windows installer but this popped up
ren msi.dll msi.old
ren msiexec.exe msiexec.old
bash: cd: %windir%system32: No such file or directory
The window installer service is running I check and I try using other packages like chocolatey but I still get the error (Generic MSI error).
As a last resort, I deleted the node folder from the program file but that didn't work. please I need help saving this
I got the error too
This is how i solved it
1-) I ran your command line as administrator then
2-) I typed sfc /scannow in cmd and entered
I fixed this by downloading the latest nodejs zip file and then edit the environment variable by adding C:\Programs Files\nodejs.Note: add the content of the zip file to C:\Programs Files\nodejs Thanks
Try running the installer as an admin.
Run command prompt as administrator and type in this code sfc /scannow the wait for it to finish repairs and try again
would anybody happen to know the latest versions that work together on Windows Vista? I've been back and forth trying to get the right combination together but ng new never works for some reason or another.
(this is the older post showing what I already tried)
I'm having a bit of a problem here. I attempted to update angular/cli and I got errors telling me I need to update my version of node. I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
I tried uninstalling angular and clearing the cache and installing angular-cli#1.0.0-beta.14 and it installs. I can create a new project with it though it takes a long time to create it, and it also throws an error with node-pre-gyp. I came across an article on Github that said it's meant to be installed locally in the project and not globally. So I tried uninstalling, clearing cache and installing without -g to make it local within my project folder and it still has errors installing and I still can't serve my project.
How can I clear this all up and just start back with a clean slate of Angular2? I've looked around and everything I find leads me to the docs which are now updated to something beyond what my computer can handle.
I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
Have you considered running Linux? There are many versions with a lightweight GUI that runs well on older hardware. Ubuntu Mate is an example. It's harder to run node on Windows because of symlinks.
When I open a cygwin console I get the following message:
hostname: : Bad address
Furthermore when I try to ssh into a server I get this message:
gethostname: Bad address
Does anyone know what this might be about? I tried reinstalling ssh and reinstalling cygwin to no avail.
I believe this is a known problem affecting some 64-bit users with the latest version of Cygwin (1.7.29-2).
See the thread here: http://cygwin.com/ml/cygwin/2014-04/msg00132.html
I believe the only solution at this point is to download a recent snapshot, which has a patch for this.
You can get snapshots here: http://cygwin.com/snapshots
But read the directions first here: http://cygwin.com/faq.html#faq.setup.snapshots
The only way I could fix this was by installing the 32bit version of Cygwin, it's worked perfectly on my 64bit system.
Chris's method worked. I'm just going to put it in my words here.
This happened to me with Cygwin 64bit. I unplugged my laptop and at some point it crashed and restarted, it had a network issue wlan. I'm not sure the cause but suddenly I got that message "hostname: : Bad address" when going into cygwin. cygwin.bat runs .\bin\bash --login i and then I got that message
Judging by the solution that worked (replacing cygwin1.dll)
My guess is cygwin1.dll got corrupted, perhaps from an unexpected shutdown (as I just had one of those and was fine before).
Solution was, to replace cygwin1.dll with the latest one from the cygwin snapshots link.
I went here
https://cygwin.com/snapshots/
Got the latest cygwin1.dll
by clicking this link
Downloading cygwin1....dll.xz
http://cygwin.com/snapshots/x86_64/cygwin1-20141120.dll.xz
Extracting cygwin1.dll from it with 7zip (though some may use tar within cygwin but I closed cygwin particularly as i'll be replacing that file of cygwins)
made a copy of my existing cygwin1.dll and Copied cygwin1.dll over my existing cygwin1.dll
(I dragged the cygwin1.dll icon onto the command prompt to get the path to expand)
C:\cygwin\bin>move cygwin1.dll cygwinold1.dll
1 file(s) moved.
C:\cygwin\bin>move C:\Users\harvey\Downloads\cygwin1-20141120.dll\cygwin1.dll .
1 file(s) moved.
Then cygwin started fine no problems.