Skip to content
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

Successfully uninstalled Boxstarter via Chocolatey -- update policies still in place #383

Closed
Newbytee opened this issue Jan 1, 2019 · 6 comments
Labels
Duplicate Issue Issues that are duplicates of other issues

Comments

@Newbytee
Copy link

Newbytee commented Jan 1, 2019

What You Are Seeing?

The update policies Boxstarter put on my PC during the Node.js install persist even though Boxstarter was uninstalled and my PC promptly was rebooted (by me).

What is Expected?

I never expected these update policies in the first place, and I expected uninstalling Boxstarter to remove them.

How Did You Get This To Happen? (Steps to Reproduce)

  1. Install Node.js 10.13.0 via the MSI.
  2. Choose to install Chocolatey and Boxstarter.
  3. Remove the Boxstarter packages using choco uninstall <pkg names>.
@pauby
Copy link
Member

pauby commented Jan 1, 2019

When you say 'update policies' are you referring to Windows Update?

@Newbytee
Copy link
Author

Newbytee commented Jan 1, 2019

Here is what I am seeing.

image
image

@pauby
Copy link
Member

pauby commented Jan 1, 2019

This is a duplicate of #371

@pauby pauby closed this as completed Jan 1, 2019
@pauby pauby added the Duplicate Issue Issues that are duplicates of other issues label Jan 1, 2019
@Newbytee
Copy link
Author

Newbytee commented Jan 1, 2019

Yes, indeed, I have read through that thread but I failed to find a solution! I had the same experience as runewake2, where the commands didn't seem to help much (this was prior to me uninstalling Boxstarter) and gpedit.msc, well, I attempted that method as my initial instinct when this happened, but I will attach a screenshot showing you exactly what I'm seeing in case I am missing something.

image

Oh, and by the way, the same state applies to every entry in the "Windows Update for Business" folder.

@pauby
Copy link
Member

pauby commented Jan 1, 2019

Not finding a solution in the other issue doesn't warrant opening a new one. This is not a new issue. It's the same issue.

Please use the other issue so we can keep all related issues in the one place.

@Newbytee
Copy link
Author

Newbytee commented Jan 1, 2019

You do have a very good point there. My apologies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Issue Issues that are duplicates of other issues
Projects
None yet
Development

No branches or pull requests

2 participants