Skip to content

Boxstarter Not Cleaned Up After Installation #24637

Description

@runewake2
  • Version: 10.13.0
  • Platform: Windows 10 64bit

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.

image

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.

Activity

  1. Trott commented on Nov 25, 2018

    @Trott
    Member

    @nodejs/platform-windows

  2. added
    windowsIssues and PRs related to the Windows platform.
    on Nov 25, 2018
  3. runewake2 commented on Nov 25, 2018

    @runewake2
    Author

    Seems tied to this PR: #22645

  4. seishun commented on Nov 25, 2018

    @seishun
    Contributor

    It has been reverted in #24344, so this can be closed.

  5. runewake2 commented on Nov 25, 2018

    @runewake2
    Author

    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-community/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?

  6. refack commented on Nov 25, 2018

    @refack
    Contributor

    Thanks! Will a repair tool be released to address the damaged systems from this feature?

    IMHO a cleanup solution should come via @chocolatey, as they are much more proficient in the internals of the tool.

  7. bnoordhuis commented on Nov 27, 2018

    @bnoordhuis
    Member

    Closing per @seishun's comment.

  8. MPagel commented on Nov 28, 2018

    @MPagel

    Thanks! Will a repair tool be released to address the damaged systems from this feature?

    IMHO a cleanup solution should come via @chocolatey, as they are much more proficient in the internals of the tool.

    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.

  9. ferventcoder commented on Dec 1, 2018

    @ferventcoder
    Contributor

    It takes quite a bit to clear out the taste of rancid chocolate from my computational pallette. Chocolatey's Boxstarter'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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions