-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boxstarter Not Cleaned Up After Installation #24637
Comments
@nodejs/platform-windows |
Seems tied to this PR: #22645 |
It has been reverted in #24344, so this can be closed. |
Thanks! Will a repair tool be released to address the damaged systems from this feature? I have no clue what else has been changed beyond disabled Windows Updates, a few custom powershell modules and the enrollment of my account in a newly created Group Policy. Boxstarter does not have a clean uninstall process: chocolatey/boxstarter#336 and I have no idea how to manage/remove a Group Policy cleanly and safely. How can we recover our systems from this tool short of a clean install? |
IMHO a cleanup solution should come via @chocolatey, as they are much more proficient in the internals of the tool. |
Closing per @seishun's comment. |
It takes quite a bit to clear out the taste of rancid chocolate from my computational pallette. Chocolatey's hijacking of the UAC system as well as prompt- and timer-free reboots feel very much like using a sledgehammer to drive a staple into a kimwipe. |
@MPagel fixed that for you. To be clear, Chocolatey does nothing of the sort. Boxstarter is what does all the restart and UAC behaviors. |
After installing Node.JS Boxstarter is installed on the PC and permanent changes are made to the PC. This includes a permanent installation of the Boxstarter powershell module and the creation of a group policy for the current computer.
Enrolling in Group Policy is not an expected behavior of installing Node.JS and should not happen. Disabling Windows Update is an even larger red flag.
Please either remove Boxstarter or address these side effects during installation.
The text was updated successfully, but these errors were encountered: