You cannot hide an update. You can only hide a version of an update. If a new version is issued, it might show up for you. There have been 6 versions of KB3035583
https://support.microsoft.com/en-us/kb/3035583
Article ID: 3035583 - Last Review: 10/05/2015 16:45:00 - Revision: 6.0
Commercially you can't alter anything for sure! But experienced programmers will manage to tweak things? on their own regardless of the EULA on their own machines. MS can't control or actually say anything about that since they do not own the hardwares! Their concern has to remain with the things that do violate the terms of the licensing.
It comes as no surprise actually! The number remains the same while the core element sees a slight change to allow it to simply arrive mixed in with the rest. So far I have only run into the first seeing the 10 app put on back in late June and suspect then and not in July and just this past week.
The second failed upgrade by 10 app was obviously an MS server's recall of the first when I knew the reserved copy would fail here after 10 was already on and I had added in two new larger storage drives to replace the first pair of which one was failing. That was the monkey wrench tossed into the works as far as seeing any automatic replacement of 7!
The page there is a good one however since I will be passing that along for others to see. The one thing I so far have yet to see would be the "Upgrade to Windows 10" item found in the Optional updates list already checked off which has been stirring the 10 controversy a bit from people not wanting but ending up seeing the upgrade take place when not fully understanding how MS is bringing 10 in! Some likely thought it was simply another service pack and clicked to find out otherwise!
I don't want to take this tutorial thread to far into W10, but I think that there should be one or more registry settings that would prevent W10 from being installed while allowing all updates to be applied (e.g not be hidden over and over). Perhaps one of these will work for all versions of Windows 7:
Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GWX] "DisableGWX"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade] "AllowOSUpgrade"=dword:00000000 "ReservationsAllowed"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "DisableOSUpgrade"=dword:00000001
I copied and pasted that into a new NotePad file named "Windows 10 Block" with the "reg" file extension to see that merged with the 7 registry here easy enough. The updates setting to never check as well as having an additional storage drive plugged in however will cause any upgrade install attempt to fail.
The 10 installer gets confused on where to put boot files and temp install folders resulting in a failed upgrade! I wouldn't worry too much about any of this however as even if the upgrade does take place before MS fixes? their goof? it can be reverted back or if caught during the upgrade easily sabotaged even with a hard boot if necessary. Generally to finish the set up that would still require some user interaction or see the upgrade canceled out.
The main goal however for hiding and unhiding updates has always been more about problematic updates where when something goes on the existing Windows installation bugs out on you until the update is later removed. Once a system is corrected the update can then be unhidden for a normal install. That happens when a Windows Defender update interferes with the av program in some cases someone has on when the WD itself failed to go into it's own form of hibernation until no av program is present.
Yes I know what you mean mate but although as Night Hawk says the authorities can tap in any time they like I don't like the idea that Microsoft can do what they like if they so wish to do so - surely my data is MY business no one else's or otherwise I might just as well broadcast to the whole world what I ma doing and hey while I ma at it throw the AV stuff away.
I just think Microsoft have become so greedy and hell bent on a power trip that only they can control and it leaves me no choice to keep my own private matters to myself. I am the very wrong person to tell what to do and when to do it and how to do it.
Windows in my mind is slowly becoming Big Brother No2 and I for one don't like it. If their intentions and only IF are to stop counterfeiting their product then it would be ok but does it or would it stop there??
Ok a bit like the farmer who grows the chicken then wants to know how I cook and eat it and if I don't bend to his rules then I am stopped from doing it my way or prosecuted for it.
I am sorry for ranting but it seems to me that there are loads of people defending what Microsoft is doing either in the futile belief that they can do nothing about it or don't want to or couldn't care less.
Well by the direction MS has been taking you can tell BG is no longer running the show! He had stepped down as the CEO some years back with Steve Balmer taking the reins. Shortly after you saw 8 with Metro arrive and features being stripped out of Windows to the urk of many who obviously provided some negative feedback in addition to the authors who became the critics.
Now the new method for delivery in itself is actually intrusive since 10 has arrived to many as what appears to be just another "Optional" update but arrives already checked off ready to install?!That in itself was going to be a tough and go trial for MS since as suspected it did back fire on them! Now they have to set things straight.
The problem is more with the new marketing strategy over the engineering aspects. "yeah we can find a way to get 10 on more machines alright! Just give us some space to work." was likely some quick brainstorm someone in marketing suggested to the engineering dept. "Under the Table of course" to keep MS from being liable by simply saying when caught "we made a goober we will now have to correct!" while that wasn't any goober?!
For the most part the only updates that would normally be checked off would fall under "Important" and when there's a good number to play catch up on you may find several not even checked off going by date of release since those may need others installed first. You would see typically with NetFramework when some program needed 2.0 and you already had 3.51 or something else newer on. You would have to remove the latest to see the early bird then installed in sequence.
Quote