Updates jitters in Windows 10 Home!

Topic

New Reply

I just got a new laptop. It has Win 10 Home, the manufacture date is June, 2020, and I have not started it as yet because I am very concerned about the way updates come and how to “properly” handle them. The questions I have are:
1. When I start, will I be deluged by updates (i.e. from July to October)?
2. Can I select (will I have the options) which update(s) to accept/deny, and how to?
3. I’ve heard that the updates can be delayed by up to 35 days. How do I do that?
4. Are the updates still a monthly thing?
5. Are the updates sectioned, meaning security, recommended and optional?
Any and all advice would be greatly appreciated. My last computer (that died recently) was a Win XP machine! Yeah…I am an old guy! Have mercy (LoL).
Thanks in advance,
Gunny

Reply | Quote

Replies

Win10 Security Updates are issued monthly on the second Tues of the month (Patch Tues). Preview updates are released on other weeks. We do not encourage installing Preview updates.

There are two types of IDs on Win10: a LOCAL ID with which you log directly into your computer, and a Microsoft ID which logs you into Microsoft every time you use your PC.
If you want a LOCAL ID, your initial setup (first time boot up) must be done OFFLINE (not connected to your network or the Internet). If you connect to your network during first time boot, it will force you to create a Microsoft ID.

Your settings for Windows Update, to have any control over it at all, will depend on whether you have the Home Edition or the Pro Edition. Windows Update settings should be set up before the first time you connect to the Internet or it will automatically upgrade you to the latest version. You can read through AKB2000016 Guide for Windows Update Settings for Win10 for an explanation of the WU settings and suggestions on how to set it up. There are screenshots at the bottom of the AKB with examples. It is quite different than XP.

Read through some of the topics on Win10 that mention setup. Look over AKB2000016. Then come back and we can help you with the initial setup and answer any questions you have.

5 users thanked author for this post.

tjm1963, RTEsysadmin, Gunny, Microfix, Coldheart9020

Reply | Quote

OP is using Windows 10 Home edition as clearly stated in his 1st post

Reply | Quote

The AKB2000016 covers both home and pro editions of windows 10.

thank you PKCano, you are a star!

1 user thanked author for this post.

RTEsysadmin

Reply | Quote

OP…first post???
Afraid I don’t get it.
Help!

 

Gunny

1 user thanked author for this post.

RTEsysadmin

Reply | Quote

Gunny, welcome to the lounge!

As I see it, you have three choices in managing your computer.

Use the computer, don’t worry, be happy – For most home users with relatively new, main brand computers, this will be problem free.

Use the pause function (Start > settings > update & security > pause updates for 7 days or advanced options select date)  to delay updates each month until you are ready – This allows you to control the timing of update download, installation, and restart.  It also allows you to follow Woody’s update advice (MS-DEFCON) and avoid potential update problems.

Follow PKCano’s AKB2000016 guide to control updates – This provides the most control over monthly and feature updates – If you want this level of control, you should upgrade to a Pro license.  This involves the most work but gives you the best chance of avoiding update problems.

Win 10 home - 22H2
Attitude is a choice...Choose wisely

1 user thanked author for this post.

Gunny

Reply | Quote

Many Thanks PKCano!
It looks like I have a lot of catching up to do. I won’t first boot until I have at least a minor grip on things. I know I’ll have more questions, like:
Quality Update = Security cumulative, yet Other Update may include “Defender”. Is not Defender a Security?
wushowhide.diagcab implies, to me, that updates are still “listed” and as a “KB” number. Is this correct?

I do hope you stay “tuned in” because it appears I’m going to have to be tuned up!

Gunny

Reply | Quote

Updates have KB numbers like they did in XP. But instead of having individual updates for the Operating System, they are all rolled into ONE update called a Cumulative Update. Each month builds on (contains) the last months’ updates for a given version. These monthly CUs are called Quality Updates.

Version Updates occur approximately every 6 months and are called Feature Updates. Versions 1903, 1909, 2004 and 20H2 are examples (and, yes, Microsoft keeps changing the nomenclature to confuse everyone but themselves).

Wushoehide.diagcab is a MS program used to hide updates from Windows Update so they don’t get installed. In earlier versions of Windows (7 and 8.1) the hide function was built-in to Windows Update and easier to use. Now it’s separate – thank you MS for making things more difficult.

So yes, do some reading and keep asking questions.
OP = original poster (you). First post was your original entry (post).

1 user thanked author for this post.

Gunny

Reply | Quote

PKCano,

Told you I’d have to be tuned up! Questions? I’m neither proud nor shy!!
So, regardless of when my PC was built, the current month’s Quality Update would be the cumulative of all the updates from the time of build. Did I get one right!?
I am appreciative.

Gunny

Reply | Quote

Gunny wrote:

he current month’s Quality Update would be the cumulative of all the updates from the time of build

No quite. From the time the version was released. Updates are cumulative within a given version.
When you get a Feature Update, it starts all over and updates are cumulative within that version.

1 user thanked author for this post.

Gunny

Reply | Quote

It has been said elsewhere but always bears repeating: make an image to an external drive before mucking around. Just in case…. Play it safe!

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

1 user thanked author for this post.

Gunny

Reply | Quote

Wavy,

Right on! Totally agree. Plus, I do plan on going slow at first as I am a very new Win 10 user., yet I do know that an Image prior to mucking around is the safest and best way to go.

Many thanks,
Gunny

Reply | Quote

PKCano,

I’ve delved into all of it and think I have a method that should work. I would greatly appreciate your critique.
For CU’s:
Local account, not Microsoft account. Image right away. Set Metered connection ON.
Pay close attention to AskWoody’s Defcon setting, comments, and the Master Patch List.
When all/most appears to be known, Use “How To Clear Windows Update Queue”.
(Questions: After running wushowhide to verify the updates are hidden, and before restarting, do I again insure Metered is still ON? After verifying the updates are hidden and after restarting, must the PC be left On for up to 36 hours to wait for Windows Update to search for updates?)

For Feature Updates:
First find out what version I have! Then find out when the next semi-annual will occur.
Use the “Setting Target Release Version” method to stay with current version or go to next version.
(Questions: Having not used PowerShell, when I enter the two lines, do I Save or just Close PowerShell? If I select the current version, then decide to up to new version, do I edit the two lines in PowerShell or re-enter them with the new version number? If I select to have the next version, will it automatically update when it is available or simply appear in the Update Queue? If I can keep a current version for up to 365 days and new versions are offered semi-annually, can I skip a version?)

Are Servicing Stack updates handled in a similar manner, or are they special?
Same question for Other Updates (I noticed that within this update is “Defender” which I assumed was in Security Updates).

I hope I got some things right! Again, I do appreciate your input and your time.

Be well and stay safe,
Gunny

Reply | Quote

+ Local account.
+ Image right away, and before you make any big change. I like to image before I install major software or right before a monthly update.
+ If you have Metered connections ON, you can see the updates that are pending (available), but they are not supposed to download through the Metered connections. If you can see them, you can hide them.
+ If you use Pause, it stops the Update Service from scanning, so you won’t see any updates being offered in Windows Update. In addition, wushowhide won’t be able to see them either so you can’t hide them.
+ The trick, for Home Edition, is to a conbination of Pause and Metered connections. Set Pause right before Patch Tuesday for the max number of days (you can always reduce it later). When it’s time to install updates, set Metered connections ON to keep the updates from downloading. Resume updates so the updates appear in the Update queue, but Metered connections kepps them from downloading. Immediately run wushowhide and hide the ones you don’t want (but they will still be showing in the queue). Then you need to clear the queue. Use AKB2000013 and @Matador’s method starting at #2286979 – be sure you understand both before you start. Check wushowhide again and be sure only what you want is showing in the queue. Then when you turn Metered connections OFF, the updates will download/install.

+ To find out what version you have, in the searchbox type winver and hit enter. Use the TargetReleaseVersion settings to control Feature releases. You can skip versions, but if your current version gets close to EOL, MS may force upgrade you.

2 users thanked author for this post.

Linda2019, Gunny

Reply | Quote

PKCano,

Let me please be specific, regarding your comments, to insure I got the message:
Of course do an Image, use Local Account.
Set Pause to max before Patch Tuesday.
When update facts/issues are known, Set Metered to ON, then turn Pause OFF.
Run wushowhide and hide unwanted update(s).
Clear Update Queue with wushowhide. Use your steps exactly or modify them with Matador’s. (With your method, does the PC stay ON?)
When Update Queue verified to what I wanted hidden, and I am ready to update, turn Metered OFF to download updates.

Would you, please, respond to my questions within my “For Features Updates”, regarding proper “editing” (i.e. if I choose to keep same version, then change to newer version) the two lines entered into PowerShell?

Question next: If Security CU’s contain 3 parts, can I hide the IE ones or must I take the total Security CU?

Again, Many thanks, stay safe,

Gunny

Reply | Quote

Gunny wrote:

Clear Update Queue with wushowhide. Use your steps exactly or modify them with Matador’s. (With your method, does the PC stay ON?)

My method has a reboot. Matador’s method circumvents the reboot. Either will work. Otherwise, you’ve got the idea. It’s probably going to take a couple of Patch Tuesdays for you to feel comfortable.

Gunny wrote:

Would you, please, respond to my questions within my “For Features Updates”, regarding proper “editing” (i.e. if I choose to keep same version, then change to newer version) the two lines entered into PowerShell?

I have done a direct edit of the Registry instead of the Powershell commands. BUt the gist of it is, the number you use is the version you want to stay on (if you don’t want to change) or the version you want to move to (if you do want to upgrade). Right now, those numbers would be 1909 or 2004. Soon there will be 20H2 added.

Gunny wrote:

Question next: If Security CU’s contain 3 parts, can I hide the IE ones or must I take the total Security CU?

CUs in Win10 are ONE update with all patches included. There is NO picking them apart. You either install the update or you don’t.

Reply | Quote

PKCano,

OK, to be sure, as you say, your method has a “reboot”, meaning to me that I can shut down the PC and come back whenever, though within your method it says “Restart” which has a different meaning to me and implies I leave the PC ON! Please “un-confuse me”!

In Matador’s alternative, there is no mention regarding Metered ON or OFF which is also confusing to me. If I think hard, I believe Metered to be still ON, then Pause On then Pause OFF!
Again, please “un-confuse: me!

If you were close, I’d buy the beers!!!

Gunny

Reply | Quote

Restart is a warm boot. If you turn off fast start (in Control Panel\Power Options) the computer doesn’t save anything. That’s what you wnat.

Shutdown/turn on is a cold boot. The computer may save settings and state on the way down, so in never resets everything. It’s like a mini sleep. That’s what you don’t want.

Read what @Matador says here. You need to go through the whole discussion until you see what he is doing. Wouldn’t hurt to read what the others add in also. At first, I didn’t think it would work, but the discussion convinced me it does.

1 user thanked author for this post.

Gunny

Reply | Quote

Restart is like a cold boot. It is a complete shutdown without saving anything with an immediate re-boot. See Shutting Down Doesn’t Fully Shut Down Windows 10 (But Restarting Does).

Shutdown saves the state of the Windows kernel but closes all programs when fast boot is on. Again, see the article above.

--Joe

1 user thanked author for this post.

Gunny

Reply | Quote

Metered connection must be on when you start your pc

Just follow Da Boss’s method and you will be good to go.

But your computer will have to remain on, possibly overnight.

My step bypasses the * Restart the computer. This should allow Windows Update to search………..  section.

This will allow the PC to be updated in one sitting without the wait period.

My alternative method will suit those that don’t like to keep their pc’s on indefinitely

and turn off when not in use.

Hope that helps.

2 users thanked author for this post.

flyingdutchgirl, Gunny

Reply | Quote

PKCano,

I hope this is still in line with this post:

I have Win 10 Home version 1909. I took Woody’s suggestion and downloaded (not installed) version 2004.
Seeing that version 20H2 is in the immediate future, I ask, should I go to 2004 now and hold off 20H2, or should I stay with 1909 and hold off for 20H2 until it is “better known” or “safer”?

The main reason I ask is that I have set up my laptop and am waiting to do your reg edits regarding keeping the present version or setting it for another version!

Also, I do not have an option for fast start. Any suggestions there?

And again, your perspective is appreciated.

Gunny

Reply | Quote

Check again for Fast Start.
Control Panel\Power Option\Choose what the Power button does
You may have to click on something about accessing options that are not available. It may be under the settings.

Woody recommends staying on 1909, at least for another month until we see what’s in Oct Patch Tues updates. You DO NOT want any version right after it comes out (unless you like being a Guinea pig) so 20H2 is a no-no for now. 20H2 will be released sometime in the near future, it’s not out yet. If you downloaded the 2004 ISO, just store it somewhere for later.

1 user thanked author for this post.

Gunny

Reply | Quote

PKCano,

I understand and will look as you said.

Why an ISO? I thought to a USB drive was sufficient.
I haven’t dealt with ISO, but can learn!

Gunny

Reply | Quote

Look on your USB. Do you have a file that ends in .ISO, or do you see a file setup.exe?

Reply | Quote

Setup.exe

Reply | Quote

An ISO is an image file, ie. everything packed into one file.
What you have is Install Media, which is the expanded ISO.
Hang on to it.

1 user thanked author for this post.

Gunny

Reply | Quote

Got it! I plan to take the advice and keep 1909 and wait a while to see about 20H2.

Still cannot find any indication of “fast start”!?! I keep checking when I turn on the PC to insure I have Pause setup and metered ON just to be sure. So far, so good. Hoorah!

Gunny

 

Reply | Quote

PKCano,

I took care of the fast start item! I quit for the day and came back the next.
I saved the Target Release Version for last.
I am in my Administrator Account.
I made an Image first.
I went to Start>PowerShell, got the window and command line, and entered the first line as in your directions. I got “Access Denied”. (I did make sure I typed the line exactly).
I backed out and stopped.
To be literal; when I went to Start>PowerShell, there were 4 items listed:
PowerShell
PowerShell ISE
PowerShell (x86)
PowerShell ISE (x86)
There was no item called “PowerShell (Admin)” as is in your directions, exactly.
What did I do wrong this time!?

Thanks in advance,
Gunny

Reply | Quote

In the menu, right click on PowerShell and choose “Run as Adminisrator”
In the second command, be sure you have the right version number at the end of the line before you press Enter.

1 user thanked author for this post.

Gunny

Reply | Quote

PKCano

After pulling my head out and following your input, all is well.
The 2 lines were entered correctly and shows my version (1909) as the Target Version.

Your earlier comment regarding saving my USB which contains version 2004 leads me to 2 questions:
Am I to use that for version 2004 or wait for the status of 20H2 and load that (thereby skipping 2004)?
If I read the Master Patch List correctly, I would (for the October patches) block all items except those which are pointed to with Orange arrows.  Am I on the right path or have I missed out again?

Gunny

Reply | Quote

You are on v1909 currently.
But the current version of Win10 is v2004. And that is the version you would get if you used the MCT to update or make an ISO at this point.

Once 20H2 is released, v2004 will no longer be available using the MCT or downloading the ISO from MS. The MCT will create v20H2.

Now, you never want to upgrade to a version that has just been released. So you are saving the USB with v2004 in case you want/need to upgrade before 20H2 is stable. v1909 is EOL in May 2021, and who’s to say 20H2 will be ready by that time, but v2004 may be good then. So you will have it to fall back on.

Susan’s Master Patch List is aimed at businesses, which are usually under a fixed timetable for updating. They usually have an IT department with know-how and extra test machines to check for problems with updates. If an update crashes the test machine, at least the production machines are safe. So Susan “blesses” the updates before Woody does.

Woody’s DEFCON system is aimed at the consumer, who usually doesn’t have a spare machine or two to sacrifice to bad parches. So Woody tends to hold off longer with the patching.

Both Susan and Woody (and all of us here) work together to ferret out the problems and publish them for the good of all. You, as a consumer, probably can’t afford to be on the front line for testing patches. So I would recommend you use both systems to to make yourself aware of where things stand, and wait for Woody to give the go-ahead for safe patching.

1 user thanked author for this post.

Gunny

Reply | Quote

PKCano,

PKCano,

Then I want to pay close attention to Woody’s Defcon status and comments on bad/questionable patches.
As I now understand, ignore the patches that Woody comments on (paying attention to daily comments) and only patch when “cleared” (i.e. Defcon 4).

As 1909 is not EOL until May 2021, I don’t have too much to worry about now. If 20H2 isn’t “cleared” by 1909 EOL, it would be OK to then up my version to 2004 and wait.

I think I’ve got it now.

Again, many thanks for tuning me up! Want you to know it is not being wasted on me.

Gunny

Reply | Quote

PKCano,

I have seen Woody’s instructions for the October updates (Defcon 3). He indicated that merely going to the Updates and checking “Resume Updates” would essentially be all that is needed to get the updates. Also, I have not seen any “KB” noted to be ignored.

This will be my first update session (no September update) and Woody’s instructions seem oversimplified from what I was prepared to do, meaning the use of wushowhide, etc.

I would appreciate your guidance, this time around, to ensure I do not mess things up on my first outing!

Yes, I plan to Image and provide a Restore Point first, and I am set on version 1909 in the Registry and have Metered set to ON.

Thank you in  advance,
Gunny

 

Reply | Quote

If you have metered connections set to ON, the updates should not download, but when you Resume updates, they should appear in the Windows Update queue. Resume updates, look at them, hide any you don’t want using wushowhide. If they are OK, turn off Metered connections and let ‘er rip.

If the ones you hide haven’t disappeared from the queue, wait till they do before you turn off metered connections. Or if you are in a hurry use AKB2000013 and @Matador‘s method starting at #2286979 – be sure you understand both before you start. Check wushowhide again and be sure only what you want is showing in the queue. If they are OK, turn off Metered connections and let ‘er rip.

1 user thanked author for this post.

Gunny

Reply | Quote

PKCano,

I understand the procedure. My last thought is that I have not seen any indication of updates that should be hidden. I hope I am correct on this point.

Thank you,
Gunny

 

Reply | Quote

If you don’t anything in the list in the WU queue that you don’t want, you are good to go

Reply | Quote

PKCano,

I have not seen anything other than the HP one noted as KB4577586 which does not apply to me!
I do not use Office 365, so I would not want those.
I’ve noted nothing else!

Thanks,
Gunny

Reply | Quote

PKCano,

I went through the procedures and only have one dilemma.

I hid the NET Cumulative Preview and the one regarding Flash.

After the downloads were done, I checked the Update History and found that they were both present! I uninstalled both of them. When I re-checked the History, the Flash one was gone yet the NET Cumulative Preview was still there. Did I mess something up? Can I/should I correct? What concern(s) should I have if it is there and I cannot correct??

I have gone through all my settings and found nothing changed. All my programs/files are present and as yet I have found nothing “added in” though I am still looking.

Gunny

Reply | Quote

You need the Flash updates. Flash is built in to IE11 and Edge and you need to install the security fixes. It will be gone in Dec or Jan, and MS will issue a patch to remove it. But in the meantime, install Flash patches.

And for now, don’t worry about the .NET Previews. MS will fix the optional/required problem with them eventually. If they get installed, just let it be (but not the CU Previews, hide them if they show up).

1 user thanked author for this post.

Gunny

Reply | Quote

OK and thanks!
I gather that I will need the Flash updates for security reasons, but is this true even though I do not use either IE or Edge?

Gunny

Reply | Quote

MS built Flash into IE11 and Edge. That is why you get the update through WU instead of from Adobe.
If you use Flash addons with other browsers, then the dealings are directly with Adobe, and you have to get the updates and the uninstaller from them..

Reply | Quote

Yes, as some parts of IE are “baked into” Windows until MS removes or deactivates them in December or January. Same goes with Edge, as noted by @PKCano in the post above yours.

Reply | Quote

I noticed they are pushing McAfee again on the d/l page , haven’t seen that for a while..

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

Following all the great and timely advice, I managed through October updates with no apparent problems, even though I had one hiccup which was successfully corrected.

I am learning and retaining thanks to all of you. I do not feel so “XP” old now…but wait until November’s Updates!

Gunny

Reply | Quote

PKCano

Regarding the November Updates:
I ran through the process but noticed two “problems”.
(1) I hid the Cumulative Review and Edge updates and proceeded to run the services step but before I could get to that, I saw that the normal Cumulative Update was already “installing”!
(2) I completed setting Services to Manual. When I restarted, the update process started! After the restart had finally completed, I was then greeted with a new Edge screen. I then knew something was amiss and “stopped” the Edge thing through Task Manager. I then completed the remainder of the update process (i.e. running wushowhide) but did not set Metered to OFF. I went to Update History and found that the Cumulative Update (not the Review one) and Edge update had already installed. After setting Metered back to ON, the Malicious Software update installed. I returned to Update History and verified that the Malicious Software update was present.
So, my questions would be:
(1) Why did the Cumulative Update begin so fast before I could get to Services?
(2) Why did the Edge Update install even though I checked it after running wushowhide and verified it was not present with the second running of wushowhide?
I again note that I followed your procedure exactly, except for Matador’s one change.
My confidence is not shaken…I just wish to know what I might be doing wrong and/or learn how to control things a bit better!

Gunny

Reply | Quote

Ensure the metered connection is ON from the moment your computer starts up.

And then only turn OFF when you see the updates that you want are in the queue after following ALL the steps in AKB2000013.

It appears that the update queue was not cleared.

Gunny wrote:

I again note that I followed your procedure exactly, except for Matador’s one change.

What change was that?

1 user thanked author for this post.

Gunny

Reply | Quote

I never turn metered off. I use the download / install buttons instead.
Lately if been using WUmgr and find it a nicer way to manage/install the updates.

cheers, Paul

1 user thanked author for this post.

Gunny

Reply | Quote

The Windows Update queue and the wushowhide list are two different things.
That’s the part you may be missing.

Windows Update queue contains the patches that were available the last time Windows Update scanned for updates on it’s own. When WU scans, the available updates are put in a cache, and that list doesn’t get changed/refreshed until the next time WU scans on its own. That list can be as much as three days old. But what’s in that list is what gets downloaded and intalled.

wushowhide, on the other hand, is dynamic (real time). When you scan with wushowhide, you see the list of what is currently available. If you hide patches, then scan again, what you see is the actual current list with the unwanted patches removed. But that doesn’t change the WU cache/queue and that’s what gets installed. What’s in the WU queue doesn’t reflect what you have hidden until WU scans again on it’s own.

So the purpose of clearing the WU queue is to make its list current so that it reflects the changes you made with wushowhide.

Metered connections prevent WU from downloading the patches currently in the queue.
By turning ON metered connections BEFORE you start the process of clearing the queue and forcing WU to scan again, you prevent the patches from downloading until the queue matches what you see in wushowhide. Once they match, you turn metered connections OFF and allow the update.

2 users thanked author for this post.

Gunny, Matador

Reply | Quote

Better option would be to upgrade to Pro and get better Windows Update management.
There are some special prices from time to time.

1 user thanked author for this post.

Gunny

Reply | Quote

No need to spend money on Pro when you can use metered and Wumgr IMO.
Spend the money on a USB backup disk, and if you already have one, get a new game or 3. 🙂

cheers, Paul

1 user thanked author for this post.

Gunny

Reply | Quote

Paul T

My new laptop was a birthday present…and my grand daughter got me 6 Flash Drives!!! I think that will help for a while!

Back at Ya!
Gunny

Reply | Quote

The change I mentioned regards Matador’s method of no restart,

“An alternate step is NOT to restart the computer, just open Settings/Update & Security and Pause updates again. Then immediately Resume Updates, this allows WU to check for any updates and in the process resets the update queue. There is no need to wait days for it. Metered is still ON.
Just follow on with the remaining instructions and you will be good to go.”

I used wushowhide and hid 2 updates. The WU queue window was visible. I closed wushowhide and went to do the Services step but noticed that in the WU queue window the Cumulative Update was already installing. The next step was to restart and that’s when the update process was noticed.
When I returned (after the restart was completed), I did the Services step and re-ran wushowhide. It showed me that the two updates I hid were not present. that is when I did Matador’s step (quoted above) then completed the process, seeing the WU queue and the 2 updates I hid were not there. That is then when I set Metered to OFF and the updates began. When done, I reset Metered to ON and did a restart. Again, I got the updating process prior to the restart completing.

When I checked the Update History, I got the security ones, the Cumulative and the Edge one. I did not get the Cumulative Review one that I hid.

So, the mysteries to me are the immediate install of the Cumulative (which I wanted) and getting the Edge one that I had hidden.

I am sure that I must have botched the process somehow and some way. Any clues?

I know Pro is a better choice, however, in my current “condition” I have to calculate and save prior to any movement!!!

I am still not deterred and appreciate all the input which is keeping me on the learning, and correct, path.

Thanks to all for the replies, which I value.

Gunny

Reply | Quote

If you have Pause ON, you will not see any updates in the queue OR in wushowhide.
If metered connections were ON BEFORE you “Resumed updates” (ended Pause), the CU would NOT have downloaded.
Metered connections have to be ON when you use wushowhide to hide the updates.
When you flip the Pause ON/OFF metered connections have to be ON.
You have to wait until the hidden updates are no longer showing in the queue before you turn metered connections OFF, because when you turn it off, whatever is left in the queue is going to download/install.
Somewhere you missed something.

Reply | Quote

PKCano

I’ll be literal:
Metered ON. Pause set to Resume, ran wushowhide with auto fix unchecked.
In wushowhide, I selected 2 updates to hide (Cumulative Review and Edge), I closed wushowhide.
Went to Services and set to Stop (it was prior to getting to Services that I noticed in the WU queue window that the Cumulative was installing). Restarted (that’s when the restart showed update(s) were being processed), restart finally completed. Went to Services and set to Manual, ran wushowhide (auto fix unchecked) and saw the updates I hid were not available to be hidden, closed wushowhide. Set to Pause, waited a moment and set to Resume, went to Security & Update and saw the updates I hid were not present, turned metered to OFF, updates installed, turned Metered back to ON, restarted and saw the updating process until it completed and then the restart completed. Went to Update History and saw the Security updates and Edge were there (but I had hid Edge update!?).
That’s as brief, but as exact, as I can get. The only thing I see that is not literally in the procedure is my turning wushowhide off (both instances).
Your thoughts?

Gunny

Reply | Quote

What is the KB number of “Cumulative Review”?

Reply | Quote

Oh Wow!
I do not remember and did not write it down.
It was one of the two I hid.

Gunny

Reply | Quote

PKCano

I re-checked and that Cumulative Review is KB4586878.

Gunny

Reply | Quote

OK, That is not a “Cumulative Review”
KB4586878 is a Cumulative Update Preview for .NET Framework.
Because of the way Microsoft has the metadata in that .NET Preview, for the last three or four months people have not been able to hide it and it installs whether they like it or not. So you go bit by that one along with everyone else, until MS decides to fix how it installs. If you search for that KB number on this site you will see how many complaints there are!

The Edge – I suspect MS is forcing that one also.

Here is what I think happened:
When you turned on metered connections and clicked Resume updates, those two unstoppable ones downloaded and installed (even you thought you hid them).
After the reboot and going through the other part of the procedure, the Cumulative Update for Windows installed like it should have. You should have KB4586786 CU for WIndows in the Windows Update History.

Reply | Quote

PKCano

Sorry, Preview is what I meant. Fingers are faster than the mind.
I have the KB4526786 CU.
And thanks for the sanity check. I can now blame MS instead of kicking my butt!!!
And by the way, I was sure I had followed procedure exactly!
Awaiting next month’s new adventure.

Many thanks,
Gunny

Reply | Quote

You may get a .NET Preview again in Dec, if MS hasn’t changed the way it installs.

Reply | Quote

PKCano,

Long time no problem…until now!

I followed the advice when Defcon went to 3. With wushowhide I blocked all updates.
I then went to the Catalog and got KB5001649 (also as advised) and updated.

When I checked Update History, I saw that besides KB5001649, I got;
KB2267602 Security Update for Defender Antivirus
KB4052623 Security Update for Defender Antivirus Antimalware platform
KB890830 Malicious Software Removal Tool, and,
Servicing Stack V10.0.19041.860

I do not understand given that I blocked ALL updates in wushowhide.
I could use a sanity check now!

Thanks,
Gunny

 

Reply | Quote

The SSU is now included in the Cumulative Updates, including KB5001649 that you installed, so that’s OK.
Defender is the built-in Windows A/V, will usually update independently, even it shows up in the WU queue. So that’s OK.
And MSRT is the Windows once-quarterly A/V scan. So that’s OK.

Best not to hide the Defender updates and the MSRT.

Reply | Quote

The AV, MSRT and SSU are required updates and should be installed.

Wushowhide won’t prevent them downloading. You need to have metered set to on for your network connection, then you can hide updates using wushowhide – or WuMgr if you prefer.

Warning: yesterday I had an error in Windows Update with a Retry button. Clicking Retry ignores the metered setting and downloads and installs everything.
The solution is to use WuMgr to install the updates, leaving WU to catch up later.

cheers, Paul

Reply | Quote

Total sanity restored!

Many thanks to PKCano and Paul T.
Again I have learned more from your info and insights.
Stay safe and well.

Gunny

Reply | Quote

PKCano,

Another anomaly for me to get advice on…

In the update process this month I Hid the Cumulative Preview for version 2004. Continued the process then verified the updates through History. History showed that the Cumulative Preview was installed?!?! I went to uninstall the update and it appeared to be accomplished. After I rebooted, I re-checked History and that Preview still appeared as installed (listed as installed this date)!!! When I went, again, to uninstall the Preview, it was NOT present!?!?

Which do I believe…History Screen or the Uninstall screen?

Thanks,
Gunny

Reply | Quote

OK, History is history. When something happens, it happens. It doesn’t just “un-happen.

The update installs – that happens. that’s history.
You uninstall the update – but that doesn’t mean the history of the installation unhappens. The update was installed. You can’t erase history. It happened.
But the update is no longer installed, you uninstalled it, so it doesn’t show up in the Installed Updates anymore.
But the installation is still in history because it DID happen.

You actually knew that, if you thought about it. Right? 🙂

History is what’s happened in the past.
Installed Updates is what’s currently installed on your machine.

Reply | Quote

Geez!

I really feel like a dunce now!!!
My only excuse is being Microsoft paranoid.

I’ll try to pull my head out next time, or watch SOAP to clear my brain.

Thank you.

Gunny

Reply | Quote