How to remove Windows 10 upgrade updates in Windows 7 and 8

[jhexp67]

It would recommend using GWX Control Panel. It removed about 3Gb of Windows 10
hidden program files from my PC.

 

[UsernameIssues]

It would recommend using GWX Control Panel. It removed about 3Gb of Windows 10
hidden program files from my PC.

The native Disk Cleanup tool will remove those same files and more. (Run the tool as admin.)

 

[jhexp67]

Thanks for that useful tip.
I think GWX Control Panel is good if you are not interested in Windows 10 updates or reserved it and decided not to upgrade and want to remove any hidden files.

 

[thelma]

Well, thanks for that info UI, I did that only last week so I won't bother. Anyway, at the moment I don't do anything on this PC without Anak's consent as he is helping me clean my PC.

 

[thelma]

thanks for this new list Lee,

Will take notes.

Cheers

 

[Bertison]

Thanks Lee, very useful in keeping 7 safe from contamination!

 

[UsernameIssues]

~~~
Computers that have this Group Policy object enabled will never detect, download, or install an upgrade to the latest version of Windows.

You can configure this Group Policy object by using Group Policy Editor (gpedit.msc). You can do this by going to Computer Configuration > Administrative Templates > Windows Components > Windows Update, double-clicking "Turn off the upgrade to the latest version of Windows through Windows Update", and then clicking Enabled.

Or to suppress this offer through the registry, set the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
DWORD: DisableOSUpgrade = 1

It looks like you suggesting that people should uninstall or avoid installing KB3050265. Do you have evidence that the GPO or registry change quoted above will work without KB3050265 (or newer WUC) installed?

 

[Brds7t7]

All I know is all the systems I have set the Group Policy on have never downloaded any Windows 10 files or offered the upgrade to 10 on any of my systems.
From what I've seen some people have said the registry change sometimes doesn't stick after a new upgrade client install. I have never encountered this with the GP set in place.
I have all the WU client updates installed though.

Not sure what evidence I can provide, I'm just going on my own usage and testing in various different VM's.
If none of those Windows Update Client updates are installed, then the GP object doesn't exist on the system anyway, as it was first introduced with KB3050265. So it can't be set without that update installed.

As for the Registry setting, I don't know as I've always preferred to use the GP workaround.
I just used the wording from the KB article on the MS site.

 

[UsernameIssues]

Brds7t7,
This thread seems to be for people wishing to avoid:
1) changing the OS to W10
2) telemetry
You provided a list of "Windows 10/telemetry related" updates (presumably for people to avoid or uninstall*). I was hoping that you had computers where you had set the GPO, removed the updates that you listed and had empirical evidence that "Computers that have this Group Policy object enabled will never detect, download, or install an upgrade to the latest version of Windows".

As I understand them, GPO settings are not magic. They require some app to read and obey them. As you noted, the GPO setting in question is not originally a part of Windows 7. It was added by KB3050265. The Windows Update client that came with KB3050265 will read that new GPO setting and act accordingly. However, if you uninstall every Windows Update Client until you are at the version prior to KB3050265, then what app is going to read and act on the GPO setting that you mentioned?

I vaguely recall testing in a VM that only had SP1 installed. I installed KB3050265, set that GPO and then uninstalled KB3050265. I think that the GPO setting remained; but I could not leave that VM in that state to test the statement: "Computers that have this Group Policy object enabled will never detect, download, or install an upgrade to the latest version of Windows".

Since you stated that you have been installing each new Windows Update Client, then you might not be able to test this for those in this thread.


*If your list of updates is for people to uninstall, then you might be doing them a disservice by telling them that "Computers that have this Group Policy object enabled will never detect, download, or install an upgrade to the latest version of Windows" after they uninstall all of the Windows Update Clients on your list.

 

[Brds7t7]

Problem solved. List removed.
I'll keep them for my own personal use.

 

[UsernameIssues]

Brds7t7,
It is fine if you wish to add your list to this thread. I was simply attempting to highlight the potential problem with removing all of those Windows Update Clients AND depending on that GPO setting. As you mentioned, there have been posts where people had various registry settings* and yet they had W10 ready to install. I'm wondering if that was caused by removing the very Windows Update Clients that were designed to read those registry settings.

*that GPO is just another registry setting.

 

[Brds7t7]

Point taken. People just mentioned they wanted updated lists that's all.
I'm not an I.T tech, so I can't really explain all the workings of group policy objects, etc.
Just wanted to help with an updated list which has worked so far for me and any other friends, relatives systems that I've used the GP workaround on.
I can't say 100% whether it will work in future with the way MS is trying to push 10.
I'm just going by my own list which has worked for me.
I've removed it now anyway, so won't cause anyone any issues.

 

[jelson]

Problem solved. List removed.
I'll keep them for my own personal use.

Personally, I really liked how your list was organized and contained both the function and reference link for the updates. I for one will miss it.

 

[jelson]

Brds7t7,
It is fine if you wish to add your list to this thread. I was simply attempting to highlight the potential problem with removing all of those Windows Update Clients AND depending on that GPO setting. As you mentioned, there have been posts where people had various registry settings* and yet they had W10 ready to install. I'm wondering if that was caused by removing the very Windows Update Clients that were designed to read those registry settings.

*that GPO is just another registry setting.

I concur... the "DisableOSUpgrade = 1" registry setting is only functional if the Window Update Client KB3050265 (Aug '15) or newer has been installed. As I understand it, the primary reason for suggesting people setting that registry key is because their editions of W7 (Home eds.) lack the Group Policy Editor.

In my case, that registry setting would do no good at all since I haven't installed any of the recent WUC updates --- starting with KB2990214 (Apr '15). And that means, I don't have the "Turn off the upgrade to the latest version of Windows through Windows Update" showing up in pertinent "Windows Update" section of the GPE on my machine.

The underlying issue with the W10 being "ready to install" is KB3035583 which installs the "Get Windows 10" app. And that's the whole point of suggesting people take a look at GWX Control Panel -- it does address the results of installating of the GWX app and the WUC updates.

And that brings up the central issue upon which Microsoft's aggressive push the W10 upgrade relies: the technical comfort level and expertise of W7/W8 users. Most of them have WU set to "Automatic" with the "Recommended" updates set to installed along with "Important."

That's why I recently alerted all my friends and family to uncheck the box under "Recommended updates" in WU settings. It's the first thing they need to do given MS plans to offer the Install W10 patch in 2016 as a recommended update. Second thing is to make use of GWX Control Panel.

OTOH, there's those who're more tech savy... comfortable with registry settings... and being selective with the updates they install or uninstall. (And some of us really dislike the telemetry updates.)

And I believe that Brds7t7's posts and list were meant for the latter group instead of the former for whose sake you raised your well-considered concerns.

BTW, "DisableOSUpgrade = 1" registry setting (for those who have any of the WUC updates installed) does have the added advantage of restoring the "Windows Update" notifications in the system tray. There's a good thread on this issue and GWX Control Panel in another forum: link

 

[thelma]

Good explication

Jelson thanks for you're thoughts

You are explaining things here in a very simple way that I understand.

If it's true what you state here, then it underlines my idea that all updates, that are offered in a general way to the big public on certain dates, ( usually patch Tuesday), are not the same for each PC, and should therefore always be treated as a personal matter. Install, hide or (delete is not offered).

Now as far as I know, you can really only uninstall one completely from the list if you first would install it and that is wrong and dangerous.

It can simply not be true that we all need the same updates as our interests in things offered are different and what is important or even crucial for one is of no use to the other.

The words force feed, in general, come to my mind.

Does everybody, what works with a Windows 7 program ( no matter what state your PC is in at that moment ) gets the same updates on their plate every Tuesday, I wonder or is it somehow individually monitored?
Perhaps I have it completely wrong, I am only learning at the moment

 

[Brds7t7]

Problem solved. List removed.
I'll keep them for my own personal use.

Personally, I really liked how your list was organized and contained both the function and reference link for the updates. I for one will miss it.

Thanks Jelson, appreciated. I put a fair amount of time into those lists. Gathering the info, testing wherever I could in VM's. But I'll no longer be posting in any Windows 10 Upgrade related threads.
They were never intended as a "fix all" for everyone, just a collated reference for anyone wanting an updated list with some extra info/links thrown in. But I can't fix Microsoft's BS, I don't have that expertise.

I'll keep testing and keep my list updated every month for my own personal use. If anybody wants it, they can send me a message. I can't speak of the reliability of the lists for everyone, but they've certainly worked for my own usage so far.

Who knows what MS will do in the future though, they're trying everything they can to get people to install Windows 10. Unfortunately, they can't take "NO" for an answer!

 

[IAmNoMan6591]

I'll show you mine ...

Thanks for the link
Yep it's been a fun month or two but a couple of those updates have morphed at least for me Now showing a couple as Important instead of optional as originally did,
A couple even disappeared from the hide list and reappeared as Important is how I spotted them :/
Namely KB2990214 the other morphed to Recommended KB2952664

Originally the only recommended I ever showed was KB3035583 and I suppose ....1917 ?

These are my "Hidden Updates" attached:

 

[jadinolf]

Thanks for the link
Yep it's been a fun month or two but a couple of those updates have morphed at least for me Now showing a couple as Important instead of optional as originally did,
A couple even disappeared from the hide list and reappeared as Important is how I spotted them :/
Namely KB2990214 the other morphed to Recommended KB2952664

Originally the only recommended I ever showed was KB3035583 and I suppose ....1917 ?

These are my "Hidden Updates" attached:

But wait- 5583 is recommended.

 

[groze]

Here is some of what I have hidden.
KB3087039,KB2952664, KB2999226, KB3013531, KB3021917, KB3035583, KB3068708, KB3075249, KB3080079, KB3080149, KB3102810, KB3107998

I don't know if these are all of them.

You can use windows powershell to see if you have anyone of those updates installed.

Get-HotFix -id KB3087039, KB2952664, KB2999226, KB3013531, KB3021917, KB3035583, KB3068708, KB3075249, KB3080079, KB3080149, KB3102810, KB3107998

If you need to add more just add a coma, space and KB article number. If you want to make sure you are doing it correctly you can add KB article that already been installed on your system.

 

[jelson]

Jelson thanks for you're thoughts

You are explaining things here in a very simple way that I understand.

If it's true what you state here, then it underlines my idea that all updates, that are offered in a general way to the big public on certain dates, ( usually patch Tuesday), are not the same for each PC, and should therefore always be treated as a personal matter. Install, hide or (delete is not offered).

Now as far as I know, you can really only uninstall one completely from the list if you first would install it and that is wrong and dangerous.

It can simply not be true that we all need the same updates as our interests in things offered are different and what is important or even crucial for one is of no use to the other.

The words force feed, in general, come to my mind.

Does everybody, what works with a Windows 7 program ( no matter what state your PC is in at that moment ) gets the same updates on their plate every Tuesday, I wonder or is it somehow individually monitored?
Perhaps I have it completely wrong, I am only learning at the moment

We're all learning... I don't think it ever stops. And you're welcome thelma. Glad I helped.

My understanding is that everyone gets the pertinent updates for their version/edition of Windows and their machine as determined by the Windows Update mechanisms.

For instance, since I've been paying closer and closer attention over the last 6 months and scrutinizing the updates I've being offered... I've found I'm getting the pretty much same updates as everyone else. But at times, I've noticed one or two not showing up. (Some updates have prerequisites.) And of course, I get offered drivers that are specific for my hardware.

Someone else will have to address what the actual processes are and how WU determines which updates to offer.

I don't fully understand why you say uninstalling an update "is wrong and dangerous"... But, I do considering installing them "hazardous" enough to take the precaution of taking a system image before installing MS Updates and then afterwards. (Much easier to restore the system partition than trying to fix things if anything goes wrong.) And I also wait a bit and check to see if any updates are causing people problems beforehand.