Windows 10 clients can test this straightforward technique for obstructing Microsoft's Automatic Update
A standout amongst the most upbraided "elements" in Windows 10 - constrained redesigning - might be helpless against a basic break utilizing Microsoft's own apparatuses. To test that, in any case, timing will be a key segment. On the off chance that you utilize Windows 10 - any adaptation, with or without a corporate overhaul server - my pleasure to go along with me in an investigation in patch blocking. There's no compelling reason to join, run anything abnormal, or even distinguish yourself. Essentially remain back and watch and check whether it works for you.
This examination relies on a Microsoft program called Wushowhide. More or less, Wushowhide (Windows Update appear/conceal) gives you a chance to specify individual fixes and conceal them from Windows. It's like the Windows 7 and 8.1 "conceal overhauls" capacity. Once you've shrouded an upgrade, Windows overlooks it, until you "unhide" it and the Windows updater runs once more. (Microsoft has a method for unhiding particular patches in Win7 and 8.1, yet that is another story for a more unpredictable time.)
There's one catch: so as to conceal a redesign, you need to know particularly which update(s) to stow away. In this screenshot, you perceive how I can shroud a Silverlight upgrade, a Visual C++ redesign, or an IE Flash Player overhaul. There's no real way to tell Windows 10 "Shroud any new redesigns that turn out today," for instance, or "Conceal the following Cumulative Update."
Wushowhide, an odd Windows 10 troubleshooter
I've accepted for just about a year that the best way to conceal an upgrade was to sit tight for the overhaul to be introduced, then physically uninstall it and run Wushowhide to shroud the redesign. Generally, you needed to give your PC a chance to get bit before you could vaccinate it.
Windows veteran Noel Carboni, posting on AskWoody.com, has persuaded me regarding the mistake of my ways. Noel fights that you don't need to sit tight for the patch to strike. You should simply hold up until the patch is discharged and accessible on your framework, then utilize Wushowhide to conceal it, before Windows 10's constrained Automatic Update kicks in.
Hence the investigation.
Today is Patch Tuesday, and it's presumable that Microsoft will discharge another aggregate upgrade for Windows 10 - it appears to happen each Patch Tuesday. The total redesign normally turns out around twelve, Redmond time, or 3 p.m. on the East Coast.
I'd like to check whether Noel's methodology works - and I'd like to test the theory on whatever number frameworks, in the same number of arrangements, as could be expected under the circumstances.
In the event that you'd like to join in, this is what to do:
Step 1: Go to KB 3073930 and download Microsoft's Wushowhide apparatus. (Click the connection stamped "Download the 'Appear or conceal redesigns' troubleshooter bundle now.") Drag the downloaded record, Wushowhide.diagcab, to any advantageous area. I put mine on the desktop.
Step 2: Wait until this evening - after the total redesign is discharged. Watch @gabeaul or @woodyleonhard on Twitter, or check AskWoody.com for the thumbs up.
Step 3: When the patch is out, however before your framework has an opportunity to swallow it (probably on Tuesday evening or night), double tap on Wushowhide.diagcab to run it. Click the connection stamped Advanced. Uncheck the container stamped "Apply repairs naturally." Click Next.
Step 4: Wait for Wushowhide to search for the majority of the pending reports on your framework. When it surfaces for oxygen, click "Shroud Updates." There ought to be a case stamped "Combined Update for Windows 10 Version 1511 for x64-based Systems (KB xxxxxxx)" or something comparable. Watch that container, click Next, and "X" out of Wushowhide.
At that point hold up until tomorrow. We should see whether Wushowhide can defer a Windows 10 constrained upgrade before it happens - and if there are any unanticipated inconveniences. Post your outcomes here or on AskWoody.com, and we should check whether we can crowdsource this mammoth into accommodation.
No comments:
Post a Comment