Repository navigation
Installation of Chocolatey fails with several errors on a clean Windows 10 Home machine #35124
Description
Activity
Make sure you have an active internet connection and retry running the script. It will be in the Start menu, under
Install additional Tools for Node.js. Choco will pick up where it left and will install all remaining dependencies.You can also install those apps by hand. You need:
- Python 3 - you can find it in the Microsoft Store
- Visual Studio 2019 and pick
Desktop development with C++while installing.
To get what was installed by Chocolately, run
choco list -lin the command prompt.Hi @dmauas, I wanted to look into this issue but wasn't able to reproduce it (I tried Node 18.20.2, 20.12.2, and 22.0.0). Do you think this can be closed now?
Since this is no longer reproducible, and there has been no answer since the last comment, I'll close this. If you still experience the same issue, please reopen this issue or open a new one.
v12.18.3
Windows 10 Home
Version: 1909
Installed on: 08/09/2020
OS Build: 18363.1016
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Simply downloaded Node installer MSI, ran it using all default options,
when the checkbox for "install additional stuff for visual studio" appeared,
I checked it.
Installation ran...
And failed horribly.
What is the expected behavior?
Installation should run without errors.
What do you see instead?
When a windows powershell window opened, wherein the installation of Chocolately began...
in steps.
then I noticed, after a while the errors started appearing, the first being:
Python not installed. An error occurred during installation: Unable to read package from path 'python3.3.8.5.20200721.nupkg'.
Followed by multiple errors...
Eventually the powershell window got stuck, and stopped responding.
I force-closed it, and rebooted.
Additional information
Now... I have absolutely ZERO idea what was installed... where, and how in the world to uninstall it.
I honestly regret ever having touched it.
I believe a "full-uninstall-and-clean.exe" file should be provided. I can't think of any better idea, for this type of case.
I have no idea what to fix, where to look for the fix even.