MS-DEFCON 2: Make sure Windows Update is de-fanged. Patch Tuesday’s tomorrow.

Topic

New Reply

It’s been an interesting month in Patch City. First the WinXP/Vista/Win7 emergency patch (yes, you need to install the latest patches for all of them)
[See the full post at: MS-DEFCON 2: Make sure Windows Update is de-fanged. Patch Tuesday’s tomorrow.]

4 users thanked author for this post.

PhotM, Elly, abbodi86, geekdom

Reply | Quote

Replies

Woody – your article suggests that those on 1903 Pro set Feature Update deferral to 365 days. However, as documented by Martin Brinkmann on ghacks and Gunter Born on borncity, doing so will cause both deferral settings to disappear. They will then only reappear by going into the registry, resetting them, and rebooting.

In 1903, just change the deferral for Quality Updates. The Feature Update deferral can stay at zero since MS won’t force those anymore (maybe).

1 user thanked author for this post.

woody

Reply | Quote

Both Martin and Günter describe the unholy mess that is Windows 1903 Update. We’re only beginning to see how the settings work in the real world.

I can replicate the “go to 365 and lose all settings” bug.  Wotta mess.

Microsoft will have to fix it at some point, but for now, it’s all the more reason to delay feature updates for as long as you possibly can!

2 users thanked author for this post.

PhotM, Geoff King

Reply | Quote

woody wrote:

I can replicate the “go to 365 and lose all settings” bug

What if you enter some number less than 365 days?

Also since the 1903 update change is included in the June CU that comes out for versions 1803 and 1809 tomorrow, does the same concern/advice apply?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Short answer: I don’t know.

Longer answer: I don’t know what happens now., what was intended, or what will happen after the next round of updates.

Waiting for some stability and insight.

Reply | Quote

@Woody:  I’m assuming that a lot of what is being discussed is for Windows 10 only, as I don’t recognize a lot of what’s being discussed.  I don’t know what the “update referral” is, so it may be for the Windows 10 as well.  Hope I can understand what these directions are for?  Apologies for my usual “density”, and thank you again for all of your help!

Reply | Quote

Definitely “update deferral” is for Win10. Don’t worry about that one.

Reply | Quote

@PKCano:  Thank you so much for the information about that particular issue.   It helps so much for know that I can ignore some of those references which I have felt were only for the Win 10.  You are a “real” Life Saver!   🙂

Reply | Quote

I updated my 1809 VM today to 1903.
I first updated to Build 17763.529 – there were NO new WU features there.
In 1809, I had my settings at SAC, Feature/365, Quality=0, no pause.
I  changed to SAC (T) and Feature/0 and was not offered 1903 as a “seeker.”
I used Win10 Upg9252 and the Upgrade Assistant to get 1903.
Feature and Quality settings were present in WU/Advanced Options (both set to 0).
Anything less than 365 days Feature deferral – I set 180, did not change quality.
The Feature deferral disappeared from the settings.
And there is NO “download and install now” section in WU.
Something is missing here – it appears we DID NOT get what Microsoft promised.

3 users thanked author for this post.

abbodi86, NetDef, woody

Reply | Quote

There are many, many unanswered questions, and multiple behaviors that appear to be bugs.

We won’t know until MS issues an explanation – or at least cleans up its act.

In the interim, 1903 is NOT ready for prime time.

1 user thanked author for this post.

Geoff King

Reply | Quote

The “Download and install now” section won’t appear until there is a corresponding update. This even happened to me on 1809 when I was offered the 1903 feature update, which I proceeded with. Once the update is applied, the “Download and install now” section will go away until the next time.

3 users thanked author for this post.

abbodi86, NetDef, b

Reply | Quote

Yes, apparently the new feature works as bundle/pair with latest cumulative update

Reply | Quote

I’m watching several machines today with 1903 (Pro) waiting for patch Tuesday to drop.

At this time I can confirm that all deferral settings went AWOL on all my test hardware after setting the Feature delay to either 180 or 365.  I left the Quality deferral at zero on these for now, but will be testing that with an 8 day delay the next month.

Once the patches drop today, will try to post more results tonight here for you.

~ Group "Weekend" ~

Reply | Quote

Hi all.

I have a Win7 x-64 Home Premium SP1 box. Group A.

If I’m fully patched through May (I patched on 5/17 after the Defcon-3 alert for Win7), I don’t visit UK government sites, and my NIC was not one of the ones affected several months ago, and everything seems to be running  smoothly, I don’t need anything else ATM, right?

I’m referring specifically to the pciclearstalecache.exe.

Thanks a lot! 🙂

Reply | Quote

If everything is running OK, you should be good to go.

Reply | Quote

I just ran windows update for the first time in months and finally got around to updating .net for security/other things via that .net rollup that came out a few months back. and I almost completely forgot about that SHA-2 code signing update(KB4474419) that has to be installed before July 2019.

So now for all my currently installed .net versions’s security/quality fixes are up to date and I was surprised that Windows update no longer took forever to show any new updates after being run. I just had to hide a few updates and only allowed the .net security/Roll Up to download and install after I used the windows update catalog for that SHA-2 and Some required DX3D DLL(DX3D compiler extension) dependency for .net 4.7.

I would have Used the windows update catalog for the .net update also but that download package came with 4 updates and 2 of the 4 being .exe files and no instructions on how to properly download all of that to the proper directory and properly install everything correctly. So I instead just used windows Update for the March 2019 .net Security/Rollup and let windows update properly work that out for me with no issues.

The funny thing was that windows update offered me the option of downloading .net 4.7 also but I hid that offer and instead only installed the march 2019 .net Security/Rollup and afterwards I ran windows update one more time just to be sure and was no longer offered a .net 4.7 update. I’m assuming that its was installed during with that March 2019 .net Security/Rollup that I had installed.

Does anyone have a MS reference as just how many .net versions there are currently as I have not really been keeping up with .net on my systems as they are usually not offered as being required most of the time. I’m trying to keep up with staying current while trying to avoid any nefarious spyware or windows 7 EOL nagging KBs ending up on my windows 7 laptops. I’m only trying to get the needed security and some other non nefarious updates all installed so I can do my final windows 7 system image backups in Jan 2020 so I can have some fairly secure system Images on hand should I need them after Jan 2020.

Reply | Quote

The only other patch you need to be sure you have is the latest Servicing Stack KB4490628. It won’t show up in WU unless there are no other pending updates (checked OR unchecked). Check the “view installed updates” to be sure it’s there, otherwise get it through WU by hiding everything else, or download it from the MS Catalog.

1 user thanked author for this post.

walker

Reply | Quote

I Installed KB4490628 in Feb 2019 so I have that already and I have installed the 2019-02 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4487078), I did that on 6/9. And that’s from February 2019 and not March. But that’s all of the .net that I think is installed on my system and I did run windows update one more time just to see if there were any more .net patching that may be needed and there was none offered by windows update.

So I keep windows update off and just manually check once in a good while but I may have to begin checking once a month after I do my security only patching(Win 7, IE11) via the windows update catalog. I will probably be running Windows Update on a more regular schedule for anything that may be too complicated to install via the Windows Update catalog but I do want to avoid any unnecessary telemetry and nagware(Win 7 EOL nagging) so the update catalog is a good option for most of my security only updating needs.

My newest Laptop makes use of an AMD discrete mobile GPU(Terascale GPU Micro-Architecture based) and AMD’s Catalyst Control Center(CCC) is .net based software but that GPU management software has not been working completely since maybe the past 2 years after some .net patch. But CCC’s switchable graphics functionality appears to be working mostly and that’s good enough. And I’m not wanting just yet to mess around with any Graphics driver updating/rolling back that may make things worse but I do need to be keeping .net patched for security as well as quality issues going forward until Windows 7 goes EOL. My newest laptop came with a windows 8 Pro license that was factory downgraded to Windows 7 Pro, via Windows’ OS Pro edition downgrade rights, at the factory by its OEM. So after January 2020 that laptop is getting a windows 8 install from the provided recovery DVDs and an in place upgrade to Windows 8.1 to last until 2023.

Maybe when is gets closer to Windows 7’s EOL there can be a review article listing all the nefarious KBs to avoid like the Noid on both Windows 7 and 8/8.1 to keep that nonsense to a minimum.

Reply | Quote

One update you will definitely need (before July 2019) if you intend to use Windows Update is the SHA-2 patch KB4474419. Microsoft is changing the download security hashing from SHA-1 to SHA-2. Be sure you have it installed.

3 users thanked author for this post.

Geo, walker, woody

Reply | Quote

Not sure I appreciate beein tagged seeker or sucker. I’ve installed everyone of the feature updates on both my desktop and my laptop – both HP i7 machines. The laptop is 10 years old and the desktop is 5 years old. The only issues are that I need to use the update assistant to get things rolling on the laptop and have to manually install the sound driver on the desktop after installation. Never had any other trouble with either machine after installation.

Question: is my experience more typical of most users or is your fear laden narrative? I think Windows is getting better and better – been using it since we all abandoned dos and have been a member of Windows Secrets/ Ask Woody almost as long.

5 users thanked author for this post.

NetDef, zero2dash, Maincat, b, Barry

Reply | Quote

You are a “seeker” by Microsoft’s definition/terminology, not AskWoody’s. That is what MS calls anyone who clicks on “Check for Updates” (which doesn’t really mean “check,” but instead “download and install”).

I guess you are only a “sucker” if you update early (before the problems are known) and it borks you machine. Guess you haven’t been one (yet).

3 users thanked author for this post.

walker, AlphaCharlie, woody

Reply | Quote

@PKCano:  Question.  I missed the reference to the “Check for updates”.  I have Win 7, Home Premium, no sophisticated programs.  Usually when I “check for updates”, it’s the only option I see and have always used, in addition to the “NEVER CHECK FOR UPDATES”.   Is there something I’ve missed?  Thank you for all of the good advice, and guidance you provide for all of us!!

Reply | Quote

The discussion above (that you probably just read) is about Windows 10, not Windows 7. You haven’t missed anything. Your Win7 looks different than Win10.

Reply | Quote

Your experience is probably more common – most people manually installing 1903 at this point are doing fine.

But that’s always been true. The initial releases of new Windows versions have bugs that only affect some percentage of users – 1%, 25%, or somewhere in between. It depends on a lot of variables. Initially, Win10 1809 was so bad Microsoft yanked it. Twice. Right now, I’m using 1809 on my production machine.

It’s a question of balance: Are the new features worth the disruption? Even Microsoft has to find the balance – thus “Current Branch for Business” or “Semi-Annual Channel” or “broad distribution” – and it takes awhile.

Reply | Quote

woody wrote:

Initially, Win10 1809 was so bad Microsoft yanked it. Twice.

Once.

Reply | Quote

Literally, that’s true, for the RTM version. It was delayed for six weeks, and many customers who got the first release lost data.

Reply | Quote

In Woody’s book he suggest setting the semi-annual channel to 365 days, but in some posts he shows 150 days?

Also, Quality updates in the book he suggests 30 days, but in some places he suggest 15 days?

Comments please.  Thank you.

Reply | Quote

As we gain more experience, my recommendations change.

Microsoft has been pretty consistent in fixing bugs introduced with cumulative updates (“quality” updates) within a couple of weeks. Thus, I now recommend people set the cumulative update deferral to 15 days, more or less.

At the same time, Microsoft has changed the definition of “feature update” (version change) levels so many times you need a scorecard. I try to roll with the punches.

1 user thanked author for this post.

Foothills Dave

Reply | Quote

woody wrote:

I now recommend people set the cumulative update deferral to 15 days, more or less.

You realize this becomes an “automatic Defcon rating action”?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Yep. It’ll continue to be my recommendation until I see some change in Microsoft’s ability to deliver good patches.

1 user thanked author for this post.

Geoff King

Reply | Quote

? says:

yes! only 7 more “patching” months until after no winX-mas. the early june emergency patching feels like a welcome vacation. meet you at the middle fork

Reply | Quote

I’m seeing a .net 4.8 that’s from 4/2019 and most of my laptops are not that much dependent on .net except my Probook with an AMD discrete Mobile GPU and its .net based GPU management software that is so old that its compiled against a legacy version of .net with the newest graphics drivers available from HP dating to late 2012, so I’ll have to see. LibreOffice(2018/later Versions) has some VS 2015 C++ redistributable dependency as well.

My 2 oldest laptops have installed on them 2 different versions of the Visual Studio Express editions for VS 2008 and VS 2010 so maybe I can Update them with all the nesessary .net frameworks. Most of my C++ .net managed code applications are written targeting some legacy .net frameworks anyways but I never actually produced a final build of the C++ applications as I just keep them as VS C++ projects with links to the compiler generated .exe files. So I can just recompile that to target a later .net framework, but that’s only a C++ console application and the same application refactored as a C++ .net managed code Windows Forms application. I never got to the point of actually doing a final distribution build of my C++ managed code .net applications as I was just messing around anyways to learn/experiment. So those 2 C++ .net projects are still installed on 2 of my oldest laptops that have respectively VS2008 and VS2010 Visual Studio express editions installed on them.

MS at the time of VS2010 had not included any working Visual Studio IntelliSense with Visual Studio 2010 so that was a no go for me and any C++ coding targeting some shiploads of .net frameworks/assemblies with millions of lines of code and many thousands of Base Class hierarchies and Objects with their manifold functions/methods to sift through by hand just to make heads or tails of things when writing C++ .net based managed code applications.

I have not done any VS C++ coding in years and have forgotten way more than I can remember about that and I figured that .net was just going to be another thing that MS depreciated and moved on from there to things like Windows RT and UWP, but it looks like RT and UWP are what’s actually getting the boot and legacy is back in vogue to a certain very small degree in Redmond.

Even Silverlight is still being suggested by Windows Update but really I do not want Flash or any Flash equivalent on my systems as HTML5 is mostly what is going to be used going forward.

Reply | Quote

But here we are at DEFCON 2 and Windows update on my system stays locked down and not looking until I manually request that it check for updates. So now I’ll wait for the KB numbers to be published for the Security Only Windows 7 updates and whatever IE11 cumulative security update for June/2019 there is.

Folks, Windows 7 and Windows 8/8.1 have very similar OS kernels so MS is not having to go too far out of its way to offer any extended Windows 7 security updates until 2023 to its enterprise/volume licensing customers. I’m dusting off my HP Probook’s Windows 8 Pro recovery DVDs but that laptop shipped with a Windows 7 Pro Downgrade done at the factory. So that’s a clean Install for Windows 8 and an in-place upgrade to 8.1 for that laptop and if it even can last until 2023 then I got a great deal anyways for 10 good years of use.

Edit for content: Please stay on topic – DEFCON and Windows Update

Reply | Quote

AWDavwein wrote:

Not sure I appreciate beein tagged seeker or sucker. I’ve installed everyone of the feature updates on both my desktop and my laptop – both HP i7 machines. The laptop is 10 years old and the desktop is 5 years old. The only issues are that I need to use the update assistant to get things rolling on the laptop and have to manually install the sound driver on the desktop after installation. Never had any other trouble with either machine after installation.

Question: is my experience more typical of most users or is your fear laden narrative? I think Windows is getting better and better – been using it since we all abandoned dos and have been a member of Windows Secrets/ Ask Woody almost as long.

I’m certain that I don’t like being called a sucker.  1903 is excellent here.

2 users thanked author for this post.

zero2dash, b

Reply | Quote

My elderly Win 7 HP small business desktop had KB3150513 installed, so I removed it per instructions; however, I have never been offered KB4500331, nor does the MS page list an update for Win7… I use MSE and Chrome (duckduckgo)  with only Office pro plus 2010 installed (it’s a long, boring story). I’m urged to install an update I cannot locate and do not have. What’s going on? I only check for updates manually and did again today after installing some May security patches. HELP, please…

Reply | Quote

KB4500331 is the Windows XP patch for the Bluekeep vulnerability. It is not for Win7.
Perhaps your older desktop came with XP and some remnants of it are still on the computer? Or, are you using XP mode on the Win7?

1 user thanked author for this post.

walker

Reply | Quote

I haven’t been a seeker for a long while, now.

I don’t have the time or the inclination, to faff around trying to fix what MS screws up.

I have Win Update Stop set to Disabled, and it will say that way until Woody gives 1903 the thumbs up ! Eventually, I hope !  🙂

Others can be the guinea pigs.

Reply | Quote

Some users are willing to live on the bleeding edge. Microsoft loves the free beta test group.

Byte me!

Reply | Quote

how do I unsubscribe from this topic – i’ve looked up and down the posts  and can’t find the unsubscribe link.

Reply | Quote

Unsubscribe link is at top right just above first post.

Reply | Quote

[Berserker79]

Hello, I’ve got a question regarding “making sure that Windows Update is de-fanged”.

I’m on Windows 10 Home 1803 and I’ve set my Ethernet connection to metered as suggested here for Home users in order to “de-fang” Windows Update. In Settings\Update & Security\Windows Update\Advanced Options I have also set to ‘Disabled’ that ‘automatically download updates over metered data connections (charges may apply)’ option. I have no Wi-Fi connections on this machine.

Last Tuesday first thing I did after booting up was running wushowhide and hid all new updates that showed up as available. Notably, ‘KB4503286 – 2019-06 Cumulative Update for Windows 10 Version 1803’ did not show up wushowhide. Out of curiosity I went to Settings\Update & Security\Windows Update and noticed that Windows Update was in the middle of checking for updates of its own initiative. Am I wrong or this should not happen considering I’ve set my connection to metered?

Probably I should have shut off my machine before Windows Update completed this unsolicited check for updates, but I didn’t. Anyway, a minute later the check was complete and Windows Update showed a message noting the availability of KB4503286 and that because my connection is set to metered the update would not be downloaded until I hook to a non-metered connection or I hit the “Download” button. What bothers me is that when I looked in ‘C:\Windows\SoftwareDistribution\Download’ I found a folder with all the files needed to install KB4503286! So, to add insult to injury, not only Windows Update did an unsolicited check for updates, but also downloaded the update on a connection that is set to metered while claiming that no update has been downloaded because the connection is set to metered. Just more Windows Update crazyness? Good thing I’m not on a “truly” metered connection… Also, at least the update was not automatically installed (I suppose that would happen if I press the ‘Download’ button).

Assuming the above should not happen when setting the connection to metered, did I miss some important step to “de-fang” Windows Update? If so, can anyone please suggest what to do to make sure Windows Update stops this kind of behavior? Alternatively, does Windows Update perform the automatic check regardless that the connection is set to metered and then it’s just my bad luck that KB4503286 did not show up on wushowhide and thus was not hidden?

BTW, after Windows Update reported KB4503286 as available, I re-run wushowhide and sure enough that update (along with the Adobe Flash update) were available to be hidden. That’s annoying that 5 minutes earlier wushowhide had failed to list all of the available updates…

• This reply was modified 4 years, 5 months ago by Berserker79.

Reply | Quote

Berserker79 wrote:

Out of curiosity I went to Settings\Update & Security\Windows Update and noticed that Windows Update was in the middle of checking for updates of its own initiative. Am I wrong or this should not happen considering I’ve set my connection to metered?

Windows Update checks for updates automatically about once per day. It does not (supposedly) download over metered connections. But it does recognize the availability of the updates by listing them in the Windows update queue (as you saw when they showed up in the update queue after it checked.)

If you use whshowhide to then HIDE the updates, they are hidden.
BUT, the availability is not removed from the update queue. Even though you have hidden them, they will still download if you click “Download” b/c they are still in the queue.

You have to clear the update queue for the hiding to be effective. You can try the procedure in AKB2000013 to do this. Once the update queue shows only the updates you want (not hidden), and the others are verified hidden, you can undo metered connections long enough to get the updates you want.

1 user thanked author for this post.

Berserker79

Reply | Quote

Thanks for the explanation PKCano!

So, the bottom line is:
1) it’s normal for Windows Update to automatically check for updates when the connection is set to metered;
2) it’s a good idea to run wushowhide multiple times after updates have been released to ensure that everything I want to hide is set to hidden;
3) it’s (always) necessary to clear the update queue for the hiding to be effective.

The only “mystery” that remains unsolved is why Windows Update actually downloaded (but did not install) the KB4503286 update despite the connection being set to metered. It’s a bit silly for Windows Update to warn me that costs may be incurred if I choose to download the update on a metered connection when it actually already downloaded that update. Well, think I don’t really need to solve this mystery: after all it’s Windows Update we are talking about, so strange things are bound to happen! 🙂

Reply | Quote

Note: If the CU had been downloaded, I think it would have been installed. Consider the possibility that the whole CU has not been downloaded (look at the size of the file that you are referring to), but instead a container of metadata about the CU (would be smaller). This could be the “availability” that keeps showing up in the queue after you have hidden the patch.

What has been downloaded (and not installed) is in the
C:\Windows\SoftwareDistribution\Download folder. Make a copy of the folder in a different location (don’t MOVE it with drag/drop) and delete the contents of the original folder leaving the folder itself. Run the procedure in AKB2000013 again and see what happens.

If everything works, you can delete the copied folder.

Reply | Quote

I’m relatively sure that the CU was downloaded, but not installed. Below is what my Windows Update screen looks like since last Tuesday. Since then the CU is not shown in ‘View installed update history’ and Windows did not prompt to “Update and shut down” or “Update and restart” at any time.

A literal translation of the text between the Windows Update title and the Download button reads as follows:

“Updates available
Last check: 11/06/2019, 19:01

2019-06 Cumulative update for Windows 10 Version 1803 x64 (KB4503286)
Status: Awaiting download

Updates are available. The download will take place when using a non-metered connection or you may download 82.02 MB on the current metered connection (charges may apply). Some updates may require connection to a non-metered Wi-Fi network”

Despite claiming that the update is yet to be downloaded this is what I found in the C:WindowsSoftwareDistributionDownload folder:

The folder that pertains to KB4503286 is about 300 MB in size, so I don’t think this is a container of metadata, but the files that were downloaded (and not installed).

Anyway, I’ll follow your suggestion to copy the Download folder elsewhere, delete the original and re-run the AKB2000013 procedure to see what happens.

Reply | Quote

I’m finding the same thing… despite following all of the instructions available to us Windows 10 Home users (current v 1803 installed manually as per PK’s instructions after successfully blocking it for almost a year) posted on this site.  I check every couple of days for updates to hide (using windows show/hide tool), follow what’s on the patch list as far as allowing to install or not.  When it’s patch Tuesdays, I check a couple of times a day on the Tues and Wed.  This week, I checked and allowed/hid as per patch list recommendations, and rechecked Wed and Thurs.  Didn’t use the laptop at all on Friday.  Yesterday (Sat June 15) as I’m about to check emails etc, the computer was lagging and I couldn’t open any apps… so what do I find?  Feature update to 1809, that wasn’t available to hid any of the previous days I checked!  It was already at 25% of install, so obviously ignored my metered connection and downloaded it (I assume).  I have also seen folders that appear to contain downloaded updates despite the metered connection.

Is it possible that these folders are just place holders and not really the full downloaded update(s)?  And why didn’t that Feature Update appear as a choice to hide?

I was going to shut the computer down, but thought I’d try again to see if that update showed up to hide, and it was there.  Was it being pushed as soon as it’s available to hide?  Or was I just unlucky in not checking show/hide yesterday?

I am going to let it install, just because I’m hoping it will include the M$ promise of providing a way to have more control over WHEN upgrades happen.  What really annoys me is that you think you can use your computer for something quick and critical, only to find M$ is slowing you down/rendering your machine useless at their whim.  I’m sure glad I didn’t have a time-sensitive task to perform, like flight check-in, or correspondence or I’d have been hooped.

Reply | Quote

Hello PKCano, just want to report that I followed your suggestion to copy C:\Windows\SoftwareDistribution\Download folder in a different location, delete the contents of the original folder leaving the folder itself and run the procedure in AKB2000013.

At first nothing seemed to change and the Windows Update screen still showed the CU as available for download. However, on rebooting the system once more, the Windows Update screen changed to “up to date” status and the CU is now listed in the update history as having failed installation with error code 0x8024200d.

On the other hand, Windows Update now shows a message offering to update to 1903 with a “when you are ready you can download and install”. No way I’m going to click on download and install for the time being…

Reply | Quote

Try and reinstall the CU again. Some people have reported it takes two run-throughs of the install for it to be successful.

Reply | Quote

woody wrote:

Short answer: I don’t know.

Microsoft still hasn’t acknowledged lose of ‘update deferrals’ in its documentations for 1809 and 1903 as a know issue, so maybe it is intended ? 🙂

Reply | Quote

I’m running Win10 Home, v 1809, Build: 17763.503. I defanged WU and came here looking to see if it was safe to go back. I see no info on that, but meanwhile . . .

I cannot find any Pause option in my WU. Does that only appear in WinPro?

I also see:

Intel – System – 4/11/2018 12:00:00 AM – 1815.12.0.2021
Status: Pending Install

and

Last checked today at 4:45PM
2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327)
Status: Pending download

Please what to do?

Thank you

Reply | Quote

@Peepers

I manually allowed the KB4503327 update 2 days ago on a metered connection on the same build you have (Win10 Home, v 1809, Build: 17763.503) and rebooted twice (to prevent a shutdown error I have seen w/ previous CU’s). I did not receive any Intel updates as many others have. My security is WD. So far, no problems observed.

Windows 10 Home 64-bit

Reply | Quote

Peepers wrote:

I cannot find any Pause option in my WU. Does that only appear in WinPro?

There are many different “Pause” options. In 1809, there’s one but only in Win10 Pro. In 1903 there’s one in Home and two in Pro.

Confusing? Yeah.

In my opinion the only “Pause” option that’s worthwhile is the one in Win10 1903 Home.

Reply | Quote

Peepers wrote:

I cannot find any Pause option in my WU. Does that only appear in WinPro?

Update deferrals are only in Pro versions.

Reply | Quote

If that’s the case, M$ info is (purposely?) misleading!  I’ve received the notice 1809 is ready to install (despite using all the blocking tools recommended here) on my Win10 1803 Home version.  If you click on the link ‘what’s new in the latest feature’ in Settings>Windows Update, you’d expect it to send you to the feature update it is pushing out to you (1809 in this case). If you’re not up on all the versions and when they were available, you would see the new features and expect to be getting the update pause feature. It’s the interpretation of ‘latest’ that is key, and how many people will twig to that?

Reply | Quote

Peepers wrote:

I cannot find any Pause option in my WU.

Does that only appear in WinPro?

Last checked today at 4:45PM 2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327) Status: Pending download

Doesn’t the 2019-06 CU install the “new” Windows Updater in Settings that gives Home users an ability to Pause updates in the future?

Sportsman wrote:

I manually allowed the KB4503327 update 2 days ago on a metered connection on the same build you have (Win10 Home, v 1809, Build: 17763.503)

What does your new Windows Updater screen(s) in Settings show regarding an ability to now Pause updates?  Screen shot most appreciated.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

Peepers wrote:

I cannot find any Pause option in my WU.

Does that only appear in WinPro?

Last checked today at 4:45PM 2019-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4503327) Status: Pending download

Doesn’t the 2019-06 CU install the “new” Windows Updater in Settings that gives Home users an ability to Pause updates in the future?

Sportsman wrote:

I manually allowed the KB4503327 update 2 days ago on a metered connection on the same build you have (Win10 Home, v 1809, Build: 17763.503)

What does your new Windows Updater screen(s) in Settings show regarding an ability to now Pause updates?  Screen shot most appreciated.

No deferral options offered to me in 1809 w/ June CU.

Windows 10 Home 64-bit

Reply | Quote

Sportsman wrote:

No deferral options offered to me in 1809 w/ June CU

Yo Woody, PK, and Others!

This is NOT what Microsoft touted and promised for versions 1803 and 1809.

The late May update release was suppose to include the promised change, and that release should be included in the June CU.

So what’s up?  Where is the Update Pause?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

[Peepers]

Thank you, Sportsman. I tried following your lead, but nothing will download. I have selected Retry several times without success.

My WU screen has changed, though. Screenshot attached. (I hope 😉)

OK, no. Guess I need help posting the screenshot.

 

 

• This reply was modified 4 years, 5 months ago by Peepers.

Reply | Quote

Peepers wrote:

OK, no. Guess I need help posting the screenshot.

Ath the bottom left of the entry box, choose “Select File.”
Highlight the file in the popup box and choose “Open”
If you want to instert the attachment into the post, place your cursor where you want it to go.
Choose “Insert into content”

Reply | Quote

Thanks. I will try “Insert into Content” as the other didn’t seem to work.

Or perhaps the screenshot doesn’t look the way I expect before it is posted.

Reply | Quote

Check to be sure you don’t have your connections still set to metered.

Reply | Quote

Yes, I am still metered. OK, here’s something else I don’t know how to do. Insert a quote correctly 🙂 But I can Copy/Paste.

Sportsman said:

> I manually allowed the KB4503327 update 2 days ago on a metered connection on the same > build you have (Win10 Home, v 1809, Build: 17763.503)

Reply | Quote

Peepers wrote:

I don’t know how to do. Insert a quote

@peepers

To reply to a post click on REPLY at top of post you want to reply to.

To insert the specific text you are replying to into your post, highlight the text and click on QUOTE at bottom of that post. That will insert the text in blockquote (colored block of text) and say who you are quoting automatically, Like I did in this post.

You must select QUOTE after selecting REPLY. If you don’t highlight text it will quote the complete post. Not always the best choice. 🙂

Please ask these questions in Getting Started Forum, Someone will be happy to help.

HTH (Hope that helps)

Reply | Quote

If you WANT to download the update, you should take your computer OFF metered connections. Metered connections are what you are using to BLOCK the updates from downloading.

Reply | Quote

I have a Windows 10 version 1809 computer that I have typically set to metered connection in order to prevent the OS updates from automatically downloading and installing themselves. So far this has proven effective. However, after last month’s update, I noticed that I now have a panel in the Updates tab saying that 1903 is available for that computer, but I need to click a “Download and install now” prompt in order to do so.

My question is, am I only still safe from having 1903 pushed onto me because I have the metered connection on? Or does having that “Download and install now” option mean I could theoretically remove the metered connection and not worry about 1903 installing itself?

Reply | Quote

Removing the metered connection would involve trusting Microsoft to refrain from downloading 1903 on your until you click on “Download and install now.” That option has not been available long enough to say that MS will honor it (or not).

Are you willing to trust MS?

Reply | Quote

That’s what I suspected, but I wasn’t sure if other people had news or experience that refuted that train of thought. Thanks for the input!

Reply | Quote

I just had an update automatically install over a metered connection. I trust MS, not!
1803, 17134.829.

cheers, Paul

Reply | Quote

you should be using at least build 17134.858 (KB4503288), Paul T, which fixes the event viewer problems.

Reply | Quote

Only if I use EV in any meaningful way, which I don’t on that box. 🙂

I let MS decide what to put on that machine and so far they haven’t offered anything apart from basic updates.

cheers, Paul

Reply | Quote

Read everything in here and still not sure what I should expect to see from the Windows 10 Pro ver 1803 cumulative update KB4503286 that we will probably get the OK to install next week.

1. Will the Windows Updater change to the newer 1903 style?
2. If so, will it have the same Feature and Pause “disappearing” problems as 1903 if delay is set to other than 0 days?
3. Has anything changed with Group Policy settings, particularly as respects Windows Download – ask before downloading?
4. Will item 3 above continue to hold off a forced update to ver 1903?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

forget KB4503286, Tex265 – it is superseded by the KB4503288 and KB4509478 updates

install either KB4503288 or KB4509478 update instead, which include the “event viewer” custom views fix.

Reply | Quote

1. If you mean the separate “download and install now” for feature update, then yes

2. No

3. No change

4. Yes, deferral still works

1 user thanked author for this post.

Tex265

Reply | Quote

Also does MS wushowhide tool still work?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

wushowhide.diagcab tool works with any Win10 version.

though I’m getting KB4503288 instead of KB4503286 on my other PC running Win10 v1803

Reply | Quote

EP thanks for the replies but I’m sticking with the June Security update KB4503286 if I update.  Per Woody, PK, Susan and Others, the later KB’s are “optional” and can wait until next month’s CU unless have a specific problem.

Edit: for duplicated content

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote