• MS-DEFCON 4: Install the August updates, but avoid the Optional and non-security patches

    Home » Forums » Newsletter and Homepage topics » MS-DEFCON 4: Install the August updates, but avoid the Optional and non-security patches

    Author
    Topic
    #2293768

    Now that we have the second cumulative update for Win10 version 2004, I feel confident in recommending that you install the August patches. Nope, Win1
    [See the full post at: MS-DEFCON 4: Install the August updates, but avoid the Optional and non-security patches]

    9 users thanked author for this post.
    Viewing 48 reply threads
    Author
    Replies
    • #2293793

      A reminder for those still on Win10 Pro v1903:
      v1909 has been out around 300 days. If you have Feature Deferral set for 365 days, you are getting close to running out of deferral in v1903.

      So you don’t get any surprises:
      If you set Feature Deferral = 200-250 days, you should be offered v1909
      If you set Feature Deferral = 75-100 days, you should be offered v2004
      If you want to stay on v1903 till Dec 8, 2020 EOL, set TargetReleaseVersion to 1903 (but be advised, MS may update you at their whim near EOL)

      5 users thanked author for this post.
    • #2293791

      To be clear, if KB4023057 does get installed, is removing “Microsoft Update Health Tools” from the Apps/Programs list enough to remove it completely? In addition, is this KB something I’ll want when I decide I do want to move to 2004?

      • #2293799

        KB4023057 is not needed to upgrade to the next version.
        Personally, it has never been installed on my machines. I always hide it.

    • #2293796

      On my Toshiba Satellite Windows 10 Version 1909, it took over an hour to install KB4565351, with no known issues after rebooting. It also installed the Cumulative Update Preview for .NET Framework (KB4570723). which was not optional.  Since this is a preview  would it be better to delete it, in the history section, or just let it remain as is?  Thanks

      • #2293798

        If the .NET Preview is not causing any problems, leave it. It will be superseded by the next Patch Tuesday .Net Rollup.

        4 users thanked author for this post.
        • #2293801

          If the .NET Preview is not causing any problems, leave it. It will be superseded by the next Patch Tuesday .Net Rollup.

          Thanks,  PKCano. No issues noted so far.

        • #2293818

          For the first time since using Windows 10 Pro I got a preview – .Net KB4570723
          Installed it. Has some hiccups with a super valuable app that uses .Net, which crashed.
          Re-downloaded the app (portable) and now all is well.

          • This reply was modified 4 years, 6 months ago by Alex5723.
          • This reply was modified 4 years, 6 months ago by Alex5723.
          1 user thanked author for this post.
    • #2293800

      Installed both KB4565351 and KB4569751 without incident on x64 1909; ran sfc /scannow after the restart, with no issues found. Then ran wushowhide and saw KB4570723 in the queue, which I hid. Build number is now 18363.1016 – which must be fully patched since there is nothing else in the queue after hiding .NET Preview update linked above.

      However, geekdom mentioned in #2290114 that he was also offered KB4566116 – I will keep an eye out for it and hide it if/when it’s offered to me, and suggest others do the same as again it is an optional, non-security Preview update.

      1 user thanked author for this post.
      • #2293833

        However, geekdom mentioned in #2290114 that he was also offered KB4566116 – I will keep an eye out for it and hide it if/when it’s offered to me, and suggest others do the same as again it is an optional, non-security Preview update.

        Do you have Feature Update deferral set? If so, you won’t see it since it’s a “Week C” optional cumulative update preview and so is in the same queue as Feature Updates, i.e., not available in the WU queue for wushowhide to find and hide. See @abbodi86 at #2284115

        2 users thanked author for this post.
        • #2294042

          Do you have Feature Update deferral set?

          I do have Feature updates deferred for 365 days, so that would explain it. Thanks for the clarification 🙂

    • #2293806

      Both of my computers (a Lenovo IdeaPad laptop and an i7 home-built system) are on 2004 now.  Didn’t want to be here, but I updated the laptop from Home to Pro and the home-built from Win7 to Win10 Pro, and they jumped to 2004 during the updates.  C’est la vie.

      I’ve now set them up to delay feature updates by 15 days, and I’ve paused them for a few weeks to get past the next Patch Tuesday. I also disabled defrag on both until we see if the optimize bug is well and truly fixed.  I haven’t run into any issues yet, and both machines seem to be humming along fine.

      The last updates before I paused were KB4569745 (Aug .NET cumulative) and KB4566782 (Aug Win10 cumulative).  Are there any other August updates I need before Patch Tuesday?

      Thanks…

    • #2293832

      On my Win 10 1903 Home, when I clicked “Resume Updates” today after “Pausing” last month, it FORCED me to download and install Win 2004. Took about 2 hours and 4 GB of data. Also installed 1903 updates which seemed irrelevant after installing 2004. Fortunately, everything worked ok. I might add while mentioning being FORCED to do something, it seems the new cell phones now FORCE you to do updates by WIFI instead of through cell data. Sounds like a plot by the landline providers to FORCE poor people with only a cell phone to have to buy home landline WIFI to update their phones (or risk hacks through insecure public WIFI’s). Come on corporate America, have you forgotten this country is suppose to represent freedom of choice. How about some honesty for a change?

      • #2293838

        If your cell phone is an Android, at least through the Google Play Store, you can specify under “Settings” for both “App download preference” and “Auto-update Apps” for over any network instead of just Wi-Fi only.  System updates you may not be able to use cell data because of the size of the updates and, therefore, you can ONLY use Wi-Fi  to update. Hope that helps. 🙂

        Win 10 ver. 22H2 x64

        2 users thanked author for this post.
      • #2293842

        Part of the reason I gave up on Home a few years ago and upgraded our machines to Pro.  Much easier to delay updates/upgrades and turn off most of the MS junkware with gpedit.  Home’s an ad server over which users have little control.

        The tipping point was when I was downloading something over our old DSL with the download taking hours and right before it finished (on the third download attempt) Windows 10 Home rebooted to install updates. Win 8.1 never did that.

        Re: Android.  Your phone should have a setting somewhere in System to control how updates are delivered.

        1 user thanked author for this post.
      • #2293847

        Not only poor people, but also those like me who have no interest in using wifi (or indeed apps). Mind you, my Android phone is too old to be able to update the OS anyway, but I don’t use it for any personal or financial information etc so nothing on it is at risk. Then again, my wife’s phone isn’t even smart and doesn’t have internet access, but then when she only uses a phone to make calls or send texts probably once a month what more does she need?!

        Thanks Woody for the recommendation on the August updates, as usual I shall let the dust settle on this topic for a few days before tackling my Win10 version 1909 machine. I installed 0patch Pro on my Win7 machine today and have set Windows Updates to “Never check” so we’ll see how that goes.

        2 users thanked author for this post.
    • #2293840

      Earlier this week I did a clean ISO install of 2004 Pro to a new SSD in my daughter’s laptop.  It had been sitting for three years, so I was pretty sure the Update system would royally hose things; better to start over.

      All is well. Runs office stuff, videos, online games, online whatever-she-does, accesses our Ubuntu file/media server OK, everything is peachy.  Even Calibrated her screen with XRite and DisplayCAL since I’m so nice 🙂   Best part was “WOW!  This is SO much better than that stupid phone, why did I quit using it?”  Yessssssss!!!

      Still a mystery to me why some users have big issues and others don’t; maybe because this was clean install.  Our other computers are all on 1909 Pro, this 2004 install was a “I hope this works…” exercise.

      1 user thanked author for this post.
      • #2293856

        Glad it went well! You may well be partly right with the point about a clean install over an upgrade, although plenty of users including me have had no problems with upgrades. I suspect a bigger cause of problems is either hardware conflicts or prior messing around with the computer generally including the use of registry cleaners. I dare say a large chunk of it is also down to luck!

    • #2293849

      Oops.  I have no idea what happened but update failed.  Should I click RETRY?

      2020-09-04-windows-10-update
      2020-09-04-update-history

      HP Pavilion Desktop TP01-0050 – 64 bit
      Windows 10 Home Version 22H2
      OS build 19045.5487
      Windows Defender and Windows Firewall
      Microsoft Office Home and Business 2019
      -Version 2501(Build 18429.20132 C2R)

      • #2293857

        If it were me, and it was possible, I’d leave it for a couple of days to see if that enables MS to hotfix the broken downloads, assuming the error message is correct  – which is a big assumption to make where MS error messages are concerned! At least it is a clear and concise one and spelt out in words and not just a string of numerical gibberish. That’s just a personal approach, others may see no reason not to retry straightaway.

        1 user thanked author for this post.
        • #2294095

          I tend to agree. Retry sometime before noon, Pacific Time, on Tuesday.

          If it doesn’t work, run the Windows Update Troubleshooter and try again. But don’t knock yourself out. There’s nothing in the August patches that’s pressing.

          1 user thanked author for this post.
          mpw
    • #2293870

      Well, I decided to hit RETRY for KB4565351.  First “Getting things ready” went well.  (I don’t remember it did that before.)  Then “Downloading” went well.  Then “Installing” proceeded to 100% and stopped.  Then it started over.  More slowly.  Long pauses at 11%, 44%, and 74% then proceeded to restart and all OK.  I am up to date.

      Maybe too much going on.  HP/Microsoft snuck in two software components and my Office 2019 click to run had some updates.  Busy, busy.

      All OK now.

      HP Pavilion Desktop TP01-0050 – 64 bit
      Windows 10 Home Version 22H2
      OS build 19045.5487
      Windows Defender and Windows Firewall
      Microsoft Office Home and Business 2019
      -Version 2501(Build 18429.20132 C2R)

      4 users thanked author for this post.
    • #2293883

      Now that we are at MS-DEFCON 4 to install the August patches, I’m still confused if we should install KB4578013. As Woody said in his article, “And you should similarly ignore the manual-install-only second cumulative update, KB 4578013.” which DID show up on Windows Update.

      Win 10 ver. 22H2 x64

      • #2293885

        “And you should similarly ignore the manual-install-only second cumulative update, KB 4578013.”

        Yes, that’s your answer. Nothing to be confused about. Ignore it.

        (It will be included in the Sept patches.)

        2 users thanked author for this post.
        • #2293886

          Thanks PKCano. What is confusing is that KB4578013 wasn’t listed as a Preview on Win 8.1 Windows Update but that’s M$ for you.

          Win 10 ver. 22H2 x64

        • #2294063

          I updated a Win 8.1 x64 Pro machine last night. KB4570508 (.NET Rollup) first, followed by a reboot, then KB4571703 (8.1 Rollup) followed by a reboot.

          All is well.

          I ignored KB4578013 (which parenthetically was offered through Windows Update).

          1 user thanked author for this post.
          JD
        • #2294405

          I’m still confused about KB4578013 for Win 8.1.  Woody says to ignore the update (i.e., don’t install it).  But in the Master Patch List (as of 8/31) Susan marks that same update with an “Install” status (i.e., “Should be installed as of August 31 for business patchers”).  So which is it?  Whose advice should I follow for KB4578013 — Woody’s or Susan’s?

    • #2293896

      Win 10 v. 2004 “broke” iCloud for Windows (an Apple product), which syncs Outlook to an iPhone.  Microsoft messages said problem was an Outlook file error.  Wasted hours.

      It was a problem on the Apple side, as confirmed by three levels of Apple tech support (first two were clueless) over two days.  Apple had already identified this issue.   More hours.

      Apple has a temporary workaround, and says that their engineers will be updating iCloud for Windows in the next few weeks when they release Apple Fall updates.

      Scary to lose sync and thousands of contacts between iCloud and Outlook. (Whether that’s your favorite way to manage contacts, or not.)  Heads up!

      # # #

      • #2293901

        Was it an upgrade to v2004 from another version that caused the problem, or the monthly CU update?

    • #2293902

      Tried 2004.19041.488 today on my systems and everything looked good until I tried remote desktop. The display was so slow that it made the remote computer almost unusable. I discovered that MS is now using a Remote Display Adapter driver from 2006 (XP?). My machines have Quarto video cards for my CAD work. A few non CAD systems have Intel video cards. Under 2004, all computers used the 2006 Remote Display Adapter driver.

      MS can say remote desktop works, is not fit for anything… but they can say it works!

      I restored my computers back to 1809. In remote desktop on 1809 the actual video card driver is used and the display is 90 percent of the speed of a non-remote session, not 30 percent.

      I would like to thank Macrium Reflect. Without their software I couldn’t keep a MS domain running for more than a few weeks at a time.

      2 users thanked author for this post.
      • #2294068

        I’ve had problems with RDP since 1909. Disabling use wddm graphics driver has helped tremendously but it still crops up occasionally that the remote machines present a black window with no way out unless I log in another way and reboot. Real pain

        1 user thanked author for this post.
      • #2294127

        I did some follow up and here is what I found. An 1809 remoting into a 2004 computer works just fine. The opposite is true also.

        But a 2004 remoting into another 2004 is where the slowdown is.

        1 user thanked author for this post.
    • #2293919

      Installed, without incident:

      2020-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4571729)

      2020-08 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, 4.8 for Windows 7 for x64 (KB4570506)

      Rebooted, and was offered, and took:

      2020-08 Servicing Stack Update for Windows 7 for x64-based Systems (KB4570673)

      ====================================

      …and may I say, as an ESU’er, I feel MSFT really doesn’t give a horse’s er, ears about us low-level ESU’ers: a patch that was updated in July had to be reinstalled prior to all this, and I would not have been aware of it if not for our esteemed Patch Lady Susan and her list; MSFT pushed it out on WSUS, and it was in the catalog, but NOT WU. (KB4575903, I think it was.)

      Yo, Redmond: Bananas!

      *****

      BTW, since I am now an ESU’er, should I be reporting the results of monthly updates here, or down in the basement in the Win 7 After-End-Of-Lifers, or where?

      Win7 Pro SP1 64-bit, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Greenhorn
      --
      "The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

      2 users thanked author for this post.
      • #2293946

        Reporting here is great. That way, everyone can see the results.

        3 users thanked author for this post.
      • #2294483

        Can you still print from your Win7 system after installing the rollup (KB4571729)? The following post, #2292943, reports that, after installing either the rollup or the security only update (KB4571719), printing no longer works.

      • #2294889

        Should I have used KB4575903 before installing the Aug patches.  I have 5 ESU machines and 4 of them had no issues with the two recommended patches plus the stack update.  I saw several post about KB4575903 and when or if I needed to run it.  I am in the process of trying what to do to fix the 5th machine that is showing some strange behavior after this Aug patch.  This machine is one of three same spec machines.  Please advise on the the KB4575903 question.  Thank you.

        • #2294891

          If you have the one of the previous License Prep Packs installed, I don’t think you need KB4575903

          See #2287923 for prereqs

          • #2294894

            Yes I have had the ESU since the first of the year and I added an additional ESU patch I think it was in May or June.  No issues with any of the patches until that one machine lost its mind yesterday.  Thanks for the info.

    • #2293934

      I have a question regarding the .NET Framework updates: can anyone please let me know if the current MS-DEFCON 4 includes the Preview Cumulative Update that MS usually releases in the weeks following Patch Tuesday (e.g. KB4571462 for 1809)? I’m asking because the “regular” Cumulative Update for .NET released on Patch Tuesday is no longer offered through Windows Update when the Preview is made available (as noted in earlier posts by woody). Since the rule of thumb is to avoid the preview updates, I’m wondering whether that extends to .NET Framework preview updates or whether they are kind of an exception.

      Other than that, I can report successfully installing the following patches on my Windows 10 1809 Home machine without apparent issue:
      – KB4565349 2020-08 Cumulative update + SSU KB4566424 (both manually installed since not offered through WU);
      – KB4570505 – 2020-08 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 (manually installed since no longer offered through WU after release of the Preview CU);
      – KB4484366 – Security Update for Microsoft Access 2013;
      – KB4484359 – Security Update for Microsoft Office 2013;
      – KB4484449 – Security update for Microsoft Excel 2013;
      – KB4484354 – Security Update for Microsoft Office 2013;
      – KB4484486 – Security update for Microsoft Outlook 2013; and
      – KB4484484 – Security update for Microsoft Word 2013.

      • #2293951

        I also did not get the CU & SSU for v1809 offered via WU. It started with the July updates, until June they were offered via WU. I recall that you mentioned the same issue since July. Like you I installed the updates manually. But it is strange that these updates are not offered via WU anymore.

        • #2294206

          I also did not get the August CU & SSU for v1809 offered via WU and had to manually install those and confirm that I had this issue at least since July when WU started offering the update to 1909 (which I’m regularly hiding in wushowhide so far). From what I understand based on PKCano’s input, the update to 1909 in essence prevents the regular 1809 CUs (and SSUs) from being offered. This means that until we update to 1909 (or later) we will not be offered the CUs/SSUs through WU.

      • #2294096

        You never, ever, ever need a Preview.

        1 user thanked author for this post.
        • #2294121

          but msft installs them anyway- I have last months or maybe Junes? KBxxxxxxx900 installed TWICE! I am using pkcano’s recommended settings.

          Yesterday Opened wushowhide and unticked  2 update I had hidden back in early Aug-don’t know the # of one but the other is KB4565351. So the 2 I unticked should have installed? No they didn’t. Knowing I was only going to see the needed updates and would ignore any optional that appeared, I clicked dreaded CHECK FOR UPDATES. So the above mentioned patch and one other(number unknown) appeared and proceeded to download and install. Well ok. So ONLY the aforementioned kbxxxx351 installed. The other is now no where to be found- I’ve been seeing preview updates for .net so much the last few months maybe it was a preview? Don’t know but its not on my machine. Just the one.

          Only intel driver from a long time ago and also KB4570723 update preview for .net that was offered 11aug and I dutifully hid are in wushowhide hidden area. So according to Belarc, I am only missing 1 update I don’t want anyway(KB4569751). So 1 patch file from aug is all I am supposed to get? And I have to unhide then click Check for updates? That’s NOT how I understood things were supposed to work. NEVER EVER am I supposed to check for updates!!!

          Also noticed msft installed 4569073 on 21 Aug unbeknownst to me. Sneaky so and so’s!

          So why didn’t the algorithm work as advertised? I studiously followed instructions given. Seems wushowhide is buggy?

        • #2294207

          Yeah, I’m always following your advice to avoid the Previews. It’s just that these .NET Preview updates are regularly showing up in place of the “regular” (i.e. Patch Tuesday) .NET update and making my life a little bit harder…

    • #2293935

      current MS-DEFCON 4 includes the Preview Cumulative Update

      The answer is no.
      Defcon doesn’t include previews.

      1 user thanked author for this post.
      • #2293938

        Thanks for the reply Alex. I’m aware that the DEFCON does not include previews as a general rule, which is why I’m wondering how to handle the .NET Framework updates.

        On Patch Tuesday a .NET CU Update is (often) released, but we are on Defcon 2 and so we are not installing it right away. Thereafter, MS releases a Preview .NET CU Update that supersedes the previous “regular” update while we are still on Defonc 2. As a result, by the time we are on Defcon 4 Windows Update only offers the Preview CU and not the “regular” CU.

        If the Defcon 4 does not apply to the .NET Preview CU, this means that every month we either have to manually install the “regular” .NET CU by downloading the package from the MS Update Catalog or we do not install any .NET Framework update at all.

        Both options don’t seem ideal for a majority of users, which is why I’m wondering if – as an exception – the .NET Preview CU is included in the current Defcon 4.

        1 user thanked author for this post.
    • #2293942

      Now that we have the second cumulative update for Win10 version 2004, I feel confident in recommending that you install the August patches. Nope, Win1
      [See the full post at: MS-DEFCON 4: Install the August updates, but avoid the Optional and non-security patches]

      Woody:
      I saw a new Microsoft Microcode Update, August 31 2020 ( I think) :
      “windows10.0-kb4497165-v5-x64_744848f43c1c3e827ccf16eba21cd66aa8817204.msu”
      I did install this one, but cannot figure out the what and how…

      I missed any of the Microsoft announcements, have you seen this one, with some explination what it does?

      * _ ... _ *
    • #2293941

      I lost the plot somewhere and my workstation got updated to 2004 a few months ago.I’m not doing anything weird on the box. Office/Microsoft 365, SQL Server, Visual Studio, Corel After Shot Pro, Firefox, LastPass, etc.

      I installed the August updates and they ran without problems … until I came to log in. My hard-wired USB keyboard was not recognised. The hard-wired USB mouse worked. I moved the keyboard from a 3 rear panel slot to a USB 2 front panel slot and got the magic tones to indicate that it was recognised. It worked. Then I moved it back to the USB 3 rear panel slot and that worked again. I know that I don’t need USB 3 for a keyboard. It’s the only spare slot.

      I got some weird message along the lines of “You can’t use your keyboard because you haven’t used your keyboard to activate your keyboard.”

      Life is full of strange adventures.

    • #2293949

      If the Defcon 4 does not apply to the .NET Preview CU, this means that every month we either have to manually install the “regular” .NET CU by downloading the package from the MS Update Catalog or we do not install any .NET Framework update at all.

      With Defcon 4 you install the latest CU and.NET for that month.
      The .NET preview is for the next month and will be superseded by the patch Tuesday .NET.

      For August Defcon 4 I got CU KB4565351 and .NET KB4569751 for my 1909 pro.
      No manual install needed.

      • This reply was modified 4 years, 6 months ago by Alex5723.
      1 user thanked author for this post.
      • #2293977

        I see… Then it seems my system is behaving differently from yours. I was no longer offered the “regular” August .NET patch, only the preview August .NET patch. Specifically, WU did not offer KB4570505 (i.e. the August 11, 2020 – Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10 Version 1809) and instead I was offered KB4571462 (August 20, 2020 – Cumulative Update Preview for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10 Version 1809).

        If, for the sake of the argument, something similar had happened to you, i.e. rather than getting KB4569751 WU offered you KB4570723, what would you do? Let WU install KB4570723 or manually install KB4569751?

        • #2293984

          Perhaps the Preview patch superseded the Patch Tues patch.
          If you hide the latter patch with wushowhide, does the earlier one show up?

          • #2294017

            I had hidden the Patch Tues patch with wushowhide and then also hid the Preview patch when it showed up. The Patch Tues patch was no longer available for “unhiding” in wushowhide once the Preview patch was on offer. I think it’s exactly like you said, i.e. the Preview patch superseded the Patch Tues patch.

            When this happens would you recommend manually installing the Patch Tues patch or should we let WU install the Preview patch like The Surfing Pensioner reported doing in his post #2293987?

          • #2294104

            When I first ran wushowhide on 9/1/2020, KB4570723 was already listed as an available update, not an optional or preview update.  KB4569751 was already out of the picture and not listed.

            I am leaving well enough alone as I am not having any problems since yesterday afternoon’s download.

            HP Pavilion Desktop TP01-0050 – 64 bit
            Windows 10 Home Version 22H2
            OS build 19045.5487
            Windows Defender and Windows Firewall
            Microsoft Office Home and Business 2019
            -Version 2501(Build 18429.20132 C2R)

        • #2293987

          Mine too. I just let the system install August’s .Net Preview and hoped for the best. We were advised the .Net preview for July – that also carried an ‘important’ rating – was problem-free, so I trust this one will be, as well. But it wasn’t optional and seems to have overridden any regular .Net patch.

        • #2294022

          what would you do? Let WU install KB4570723 or manually install KB4569751?


          @PKCano
          : I have the same question. The later dotNET Preview patch KB4570723 is hidden, but the earlier dotNET Cumulative patch KB4569751 does not show up in wushowhide.

          • #2294143

            Based on PKCano’s reply #2294026 above, it appears that at least for this month either manually installing KB4570723 or letting WU install KB4569751 is fine:

            Either way should work (this time) as there doesn’t seem to be reports of problems with either.

      • #2294493

        Went to Msft catalog and tried to install KB4569751- message say not applicable to my OS which is 1909 bld 18363.1016

        Weell alrighty then! that “explains” everything.   NO it doesn’t

        so, situation normal

        • This reply was modified 4 years, 6 months ago by DriftyDonN.
    • #2293965

      Just downloaded from the Catalog and installed 4569073 SSU, 4565351 Cum Aug and 4569751 .NET 3.5 and 4.8 on my 1909 Pro – now on Version 18363.1016. All seems o.k. but:
      It takes much longer now to startup, login screen to appear, taskbar items to appear and VPN to kick in. I think 4565351 is the culprit. Hopefully it will get better after a few reboots.

      Crazy enough, WU (which is restricted by gpedit.msc) still offers the notorious .NET 3.5 and 4.8 update 4562900. What’s up with that?

      MintDE is my daily driver now. Old friend Win10 keeps spinning in the background
      • #2293969

        Cleared the WU queue and luckily 4562900 is gone now. Startup etc is back to normal as well.

        MintDE is my daily driver now. Old friend Win10 keeps spinning in the background
        1 user thanked author for this post.
    • #2293983

      I currently have Windows 10 Home, ver 1903, build 18362.959.

      I clicked “Resume updates” this morning. After “checking for updates” for a few seconds, several things popped up as “getting ready”, including the update to version 2004.

      That made me nervous, so I quickly clicked “pause updates”, and it seemed to work. (I clicked it five times, so it now says updates will resume on 10/10/2020.)

      So, the August patches did not get installed.

      I’m looking for advice: should I leave it paused for another month, or should I resume and suffer the update to version 2004? (Is it risky to go another month without the August patches?)

      • #2293998

        The way you get around this is to hide the Feature Update (v2004) with wushowhide.diagcab.

        To do this:
        Set Metered connections to ON.
        Resume updates (so you can see the pending updates).
        Hide the Feature Update with wushowhide.
        Pause updates again for as long as necessary.

        When the updates disappear from the Windows Update queue, you can turn Metered connections back OFF.

        • #2294010

          Thanks. This is what I experienced:

          • I set metered connections to ON.
          • I clicked “resume updates”. After “searching for updates”, the “getting ready” and “downloading” processes started immediately for two things: the update to version 2004, and the .NET preview KB4570723. (i.e., it appeared that the metered connections trick didn’t work.)
          • I clicked “pause updates” and restarted the computer.
          • I clicked “resume updates”, and the same thing happened (“getting ready” and “downloading” started immediately.)
          • I started wushowhide and navigated it as quickly as I could, hiding the version 2004 update. As soon as it seemed to be done, I clicked “pause updates”. (At this point, I think the version 2004 update was in the “getting ready” phase. It might have gone from “downloading” back to “getting ready”. I think the .NET preview was in the middle of the “installing” phase.)
          • I ran wushowhide again, but it said there are no hidden updates.

          At this point, I’m planning to leave it alone until October. I’m pretty sure I don’t want either of those updates, and nothing else was getting displayed. (If that’s a bad strategy, please let me know.)

    • #2294007

      Win 10 1909 Pro .NET KB4569751 causing continual crashes and reboots.
      I would put this as a separate thread topic but don’t know how to do that.  Sorry for this being long but want to give details.

       

      Have Win 10 1909 Pro.  Installed KB4565351 and KB4569751.  On 08/28 I installed KB4565351 first (build 18363.1016) then KB4570723 .NET (didn’t catch that KB4569751 had been replaced by KB4570723).  System began crashing and rebooting.  System would stay up for just a few minutes before crashing/rebooting.  Did this multiple times.  Have had issues with .NET patches in the past so I suspected the crashing and rebooting may be due to KB4570723.  I uninstalled KB4570723 and .NET was back to KB4565633 and system was stable again, no more crashes.

       

      I then went to the Catalog and downloaded and installed KB4569751.  System began crashing and rebooting again.  I uninstalled KB4569751 putting .NET back to KB4565633 and system was stable again.

       

      Today, 09/05 Windows Update showed KB4569751 as pending install.  Did not want to install it and wushowhide did not show it to be hidden.  But, I thought since KB4570723 was replaced by KB4569751 that the crashing may have been fixed.  So I installed KB4569751 and the system began crashing and rebooting again, only staying up a few minutes each time.  I uninstalled KB4569751 putting .NET back to KB4565633.  System is stable again.  No issues with July .NET KB4565633.

       

      I cannot find anything in the event logs that indicates the reason for the system crashing.  Is it hardware?  Software?  Wushowhide is empty, nothing to hide.  I’m not sure but I suspect when Windows Update runs again that KB4569751 will again show up as pending download.  Wushowhide will not show it to hide.  So how do I get rid of it when it shows up again in Windows Update.

       

      • #2294084

        Your problem is most likely you are trying to install the Cumulative Update KB4565351 without installing the Servicing Stack KB4569073 first. If you are going to install updates manually, you need to install all the updates, starting with the SSU.

        The SSU doesn’t show up in Windows Update as a separate patch. It is bundled with the CU and gets installed first. If you look at the Support Pages KB4565351 under “How to get this update” you will see it listed.

        1 user thanked author for this post.
      • #2294122

        @redknight

        The following link discusses KB4569751  and why you may NOT want to install it. Ever.

        I do not get why .net framework is constantly being updated and previewed! Why do we need this .net framework at all? I’m sure there is a reason but I have nver seen anyone question it- just install it cause msft says so. Perplexing. mebbe I’ll do a search-(NEVER google it- I had my google removed 😉

        https://support.microsoft.com/en-us/help/4569751/kb4569751-cumulative-update-for-net-framework

    • #2294081

      If, for the sake of the argument, something similar had happened to you, i.e. rather than getting KB4569751 WU offered you KB4570723, what would you do? Let WU install KB4570723 or manually install KB4569751?

      I got .NET preview KB4570723 with ‘download and install’ not installed automatically by WU.
      The .NET preview came on its own days after I updated the AUG. patch Tuesday.
      I have installed the preview and suffered a very important app crashing.
      Re-downloaded and “installed” (portable) app which stopped crashing (probably the app has “cached” some previous .NET DLLs)

      • This reply was modified 4 years, 6 months ago by Alex5723.
      1 user thanked author for this post.
    • #2294115

      August patches (without the Preview KB4578013) installed with no problems to report on Win 8.1 🙂

      Installation Successful: Windows successfully installed the following update: 2020-08 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Server 2012 R2 for x64 (KB4570508)

      Installation Successful: Windows successfully installed the following update: 2020-08 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4571703)

      Win 10 ver. 22H2 x64

      1 user thanked author for this post.
    • #2294126

      Two W10-v2004, two W10-v1909, one W7 using the two scripts, all Aug patches in and no apparent problems.

      1 user thanked author for this post.
    • #2294123

      Win10-1909 Home and I got the cumulative Aug 2020 update  and I also got the .Net Preview update installed and I do not think that Home edition users are able to stop that .Net preview nonsense, but I’m not sure.

      Everything appears to be working and I’ve once again paused updates until 10/10/2020. But I always get the system Image Backup done just in case before letting the DEFCON3 approved w10 monthly updates have their way.

      I’m getting the 10/2004 feature update offered but avoiding that sword of 10/2004 that’s hanging over my head should that decision be made for me against my will.

    • #2294150

      I do not think that Home edition users are able to stop that .Net preview nonsense, but I’m not sure

      Yes, they can using Microsoft’s wushowhide or 3rd party apps like wumgr, wumt…

    • #2294157

      Windows 10 x64 1909

      https://support.microsoft.com/en-us/help/4565351/windows-10-update-kb4565351   says ”If you are using Windows Update, the latest SSU (KB4569073) will be offered to you automatically.”  This was exactly what occurred with the July patches: it was present in the “patches to be installed” list.

      I’ve just let Windows Update do its stuff for the August crop and, contrary to the above, was offered the cumulative Windows update KB4565351 but not KB4569073 (see attachment).  I let it run to see if KB4569073 would show up but there was no sign of it.  So, is the MS description misleading and that it is in fact a component of KB4565351?  If it’s not, should I just grab KB4569073 from the MS catalogue and install it now or should I start again (have a pre-patch image copy), installing the SSU update manually before letting Windows Update run?

      Just one more thing: If the SSU is a component of the monthly cumulative Windows update, is there any way to actually see that it’s installed?  It’s not in the update history – but neither is the SSU for July and I know that was installed.

       

      • #2294162

        The SSU is bundled with the monthly CU, but it never shows up in the queue in Windows Update. However, it IS there and it gets installed first as it should be.
        Sometimes, in the Update History, it may look like the CU gets installed twice. This is actually the SSU posing as the CU for what appears to be a double install.

        To verify that the SSU is installed, on the “View update History” page, at the top left there is a link to “uninstall updates.” This actually takes you to the Installed Updates list, where you will find the SSU listed.

        2 users thanked author for this post.
        • #2294168

          Ah!  KB4569073 isn’t present in the Update History list but it IS in in the Uninstall Updates list. Never thought of looking there. Doesn’t feel logical, but I suppose MS has a reason for it. And I think the MS statement that “You will be OFFERED KB4569073″ is most misleading.
          Anyway,  a big thank you for your prompt help!

    • #2294160

      offered the cumulative Windows update KB4565351 but not KB4569073

      KB4569073 is part of the CU, always have been, not a stand alone update.
      When downloading the CU you will notice multiple downloads.
      Check uninstall updates.

      1 user thanked author for this post.
      • #2294163

        KB4569073 is part of the CU, always have been, not a stand alone update.

        The SSU is NOT a part of the CU, it is “bundled with” the CU. It is a separate update and can be downloaded from the Catalog separately.

        2 users thanked author for this post.
    • #2294208

      Based on PKCano’s reply #2294026 above, it appears that at least for this month either manually installing KB4570723 or letting WU install KB4569751 is fine:

      How about waiting for the Sept 8 Patch Tuesday .dotNET CU, which will incorporate the August 19 Week “C” .dotNET CU Preview KB4570723, which has superceded the Aug 11 Patch Tuesday .dotNET CU?

      • #2294383

        I suppose you could do that… The question is whether your plan is to install the Sept 8 Patch Tuesday .dotNET CU (a) right away once it is available or (b) wait until it is cleared for install the next time MS-DEFCON is raised to a safe level.

        If (a) we would be taking the (small?) risk of installing the Sept 8 Patch Tuesday .dotNET CU without the benefit of waiting to see whether there are any bug reports about it, if (b) there is the risk that by the time MS-DEFCON is raised again to a safe level a new Week C dotNET Preview patch has replaced the Sept 8 Patch Tuesday .dotNET CU and we are kind of back where we started…

        All things considered, given the odd behavior of how these .dotNET updates are released, I prefer to manually install the Patch Tuesday CU after woody raises the MS-DEFCON level.

        1 user thanked author for this post.
      • #2294480

        For Version 1909:

        Berserker79 wrote:

        Based on PKCano’s reply #2294026 above, it appears that at least for this month either manually installing KB4570723 or letting WU install KB4569751 is fine:

        I think this quote has it backwards, b/c KB4569751 is not available any longer in WU (or in wushowhide, if it has been hidden). It was superseded by KB4570723. So, shouldn’t the quote read
        “…. manually installing KB4569751 or letting WU install KB4570723 n.b.(or unhiding it and then installing it, if it is hidden)….”

        Regarding manually installing the Aug 11 Patch Tuesday dotNET KB4569751, I read that it has problems (likely the reason for the later August 19 Week “C” dotNET CU preview KB4570723. See Known issues with KB4569751

        • #2294765

          Oh, you are most correct about that quote, it should read like you suggest.

          Regarding that known issue with KB4569751, the KB articles mentions workarounds to solve it should your system be affected, plus I suppose that since the patch was cleared for installation during the past MS-DEFCON 4 that means the issue is relatively small and the workarounds sufficient to address it.

          Since I’m still on 1809 I don’t have direct experience with KB4569751, but given the general consensus to avoid the Previews I still prefer to manually install the Patch Tuesday dotNET update (i.e. KB4569751 on 1909).

        • #2294766

          I installed KB4569751 via WU and a couple of days latter got notifications for KB4570723 preview which I installed too. After KB4570723 an app using .NET crashed. I fixed it by ‘re-installing’ (portable) the app which is now working ok.

    • #2294215

      Regarding the .NET Framework update 4570508 for Win 8.1.  There is very little discussion about it.  Search reveals only these two posts, both of which are in this topic.

      DrBonzo Sep.5 1:54pm #post-2294063

      JD Sep.5 7:17pm #post-2294115

      The above two members installed the update, which seems to indicate it might be OK for me to do.  However, they do not indicate how they came to that conclusion.

      The computerworld article this month doesn’t offer anything either.

      Not being a plus member I’m not sure what the master patch list says on the matter.

      Sometimes I really struggle with what to do about these .NET updates.  I’ve been known to ignore them temporarily until someone says something substantive or more permanently by skipping them altogether.

      Would someone please be so kind as to show me where the mystery info is or nudge me in the right direction (be it hide or install)?  I’d really appreciate it.

      Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

      • #2294217

        The Security Rollup for .NET for Win8.1 is included in the DEFCAO-4 rating and is.OK to install unless there is a problem reported.
        We do not recommend installing the Preview .NET patches, however.

      • #2294221

        Thanks PK.  Previews are something I’ve avoided all along.  Now I can do the install & complete my notes for August.  Later gator.

        Win 8.1 (home & pro) Group B, W10/11 Avoider, Linux Dabbler

        • #2294236

          @Purg2 – I do exactly as PKCano says above. Generally speaking I’ve had very good success (luck?) with .NET Rollups with a bunch of Win 7 machines and now also with a single 8.1 machine. It was the other updates on Win 7 that drove me nuts sometimes (good riddance!). I’ve never had any kind of trouble with patches on 8.1.

          1 user thanked author for this post.
          • #2294315

            @Purg2– I have had good luck in installing .NET updates as well. As advised by PKCano,  I DON’T install .NET previews or previews of ANY kind.

            As Woody says in the monthly ComputerWorld articles for patching when MSDEFCON4 or higher is reached, Windows 8.1 continues to be the most stable operating system 🙂

            Win 10 ver. 22H2 x64

            1 user thanked author for this post.
    • #2294238

      What are we meant to do about KB4571744?

      • #2294248

        KB4571744 is a Preview Cumulative Update
        We do not recommend installing Preview updates.

        + Hide it with wushowhide.
        + If you are running Win10 Pro, use Group Policy settings so it is not offered.
        + If you are using Win10 Pro with Group Policy set to “notify download/install.” ignore it. It will be superseded Tuesday by the Patch Tuesday Security CU.

        • #2294253

          + If you are running Win10 Pro, use Group Policy settings so it is not offered.

          I thought that individual policy setting applied only to preview “Builds” of the entire OS, like opting out of the Insider previews of the coming OS releases. I’m talking about the setting under the “Windows Update for Business” sub-key of the Windows Update key in gpedit.

          If I’m thinking of the wrong policy within gpedit, then which is the correct one to set to avoid these previews of the .NET framework updates?

           

          • #2294275

            I have this stting set to disable but it doesnt seem to make any impact on msft- I have kbxxxx900 installed twice , 2 days apart 4 aug and 6aug.

    • #2294307

      My old Thinkpad T61 laptop is running Win 10 version 1909 OS Build 18363.900

      I never do any updating except when Woody raises the Defcon level.  So after imaging my disk, I looked at Windows Update just now, expecting perhaps some patches for Win 1909.

      Instead I have only two Updates available, both show as “Pending Download”

      1.  Feature Update to Windows 10, version 2004   [NO KB number]
      2. 2020-08 Cumulative Update Preview of .Net Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4570723)

      Given the newness of Win 2004, is my best bet to do nothing now and wait another month?  If so,  will this machine be significantly vulnerable to recently-emerged cyberthreats?

      Since the .Net patch is a Preview anyway, I think it’s easy to ignore that one.

      By the way, this PC also has Office 2010 installed, I know that is almost at EOL but works fine for me.  I have not been offered any updates for any Office component in months.

      Thanks for the great advice here.

       

    • #2294309

      Yesterday I finished updating all computers with Aug. patches bringing me up to W10 Pro 1909 bld. 18363.1016.

      Since I don’t use wushowhide, I got KB 4023057 on 2 older Intel computers and I got the preview .net KB 4570723 on all computers along with KB 4565351 cum. w/SSU KB 4569073.

      Without wushowhide, you get what MS wants to give you for the monthly update when you click “Resume Updates”. I have 2004 blocked in Gr Po for 365.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • #2294316

      I am running Windows 10 1903 home edition.  I don’t want to upgrade to 2004 yet as per Woody’s advice, but the upgrade is listed in my updates and I can’t see any way of delaying it without  delaying all this month’s updates.

      I used to have  Wushowhide installed, but it has disappeared. Will that allow me to stop the 2004 update as it doesen’t have a KB number?

      I am not very tech savvy, (over 70) so any info I can understand will be appreciated.

       

      • #2294319

        wushowhide.diagcab is here.
        Download it and put it on your desktop where you can find it easily.
        It does not install, it just “runs” when you double click on it.
        See if you can hide v2004.

        But v1903 will be EOL in December, so you need to upgrade to either v1909 (preferred) or v2004.
        If you want v1909, you need to download the Windows and Office ISO Download Tool from Heidoc.net and use it to download the v1909 ISO. Use the ISO to upgrade to v1909. If you don’t know how to do this, create a new topic under the Windows 10 Forum and someone will help you.

        3 users thanked author for this post.
    • #2294321

      Help! My mailbox is full.  I am not subscribed to this topic and I have unchecked the box indicating to email me follow-up posts.  But the emails just keep coming.  Is there a way to stop them?

      I’ll drop back and look later.  I don’t want to check the box.

      HP Pavilion Desktop TP01-0050 – 64 bit
      Windows 10 Home Version 22H2
      OS build 19045.5487
      Windows Defender and Windows Firewall
      Microsoft Office Home and Business 2019
      -Version 2501(Build 18429.20132 C2R)

      • #2294323

        Click the link under your avatar.
        Click on “Subscriptions”
        Click on the Topic
        Clik on “Unsubscribe”

        1 user thanked author for this post.
        mpw
    • #2294345

      Topic wasn’t listed.  Maybe unchecking the box the second time stopped the subscription.  I  think the emails also have stopped.  I didn’t get a notice of your post.

      I had already done what you suggested but misread the page.  At the top it said, “Oh, bother! No forums were found here.”  On closer look however I am subscribed to a bunch of topics.

      My bad.  Need to slow down and read carefully.

      HP Pavilion Desktop TP01-0050 – 64 bit
      Windows 10 Home Version 22H2
      OS build 19045.5487
      Windows Defender and Windows Firewall
      Microsoft Office Home and Business 2019
      -Version 2501(Build 18429.20132 C2R)

    • #2294365

      Updated Win10 Pro v 1909 as follows without problems so far:

      KB4565351 August 2020 Cumulative update
      KB4569751 August 2020 .NET Cumulative Update

      I was apparently lucky and avoided the .NET Preview KB4570723. On August 21 it showed up in wushowhide, so I hid it. (I also hid KB4023057, which showed up at the same time.)

      When I then opened Windows Update, the .NET Cumulative Update KB4569751 showed up there, along with the August monthly CU KB 4565351.

      So does this mean I happened to catch the .NET Preview in wushowhide in time to hide it before it superseded the .NET CU, which was already in the Windows Update queue? The .NET CU KB4569751 never appeared in wushowhide after that, although it continued to appear in Windows Update. I don’t remember having seen it in wushowhide before then, either, but I wasn’t paying close attention around Patch Tuesday.

      At any rate, as I was getting ready to install the updates yesterday, I checked wushowhide and the .NET Preview was still showing hidden. Although the .NET Cumulative Update KB4569751 didn’t show up in wushowhide, it did still show up in Windows Update, pending download, so all was good.

      The Windows Defender Antimalware platform update to 4.18.2008.9 also appeared in Windows Update (and in wushowhide) along with the latest Defender “Security Intelligence Update.” As usual, the first time I clicked the Download button in Windows Update, the Defender updates disappeared, since they had already installed automatically, and I was again offered the Download button, which I clicked again to start the downloads. The installation took about 35 minutes before the restart.

      The updates and the SSU for this month are showing up as expected in Installed Updates, and the laptop is now on version 18363.1016. Everything seems to be working normally so far.

      I also updated our Windows 7 Home Premium laptop with the following updates using the abbodi86 standalone installer:
      KB4571729 August 2020 Monthly Rollup
      KB4570673 SSU, and
      KB4569767 .NET 3.5.1 update.
      Then I used the revised DotNET installer_r to install KB4569775 .NET 4.7 update.

      That laptop is also working fine, and I haven’t had any problems with printing.

      Thanks again to abbodi86 and to Woody, PKCano, and everybody else who shares their information here on AskWoody. Your help is much appreciated.

      Linux Mint Cinnamon 21.1
      Group A:
      Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux
      Win l0 Pro x64 v22H2 Haswell, dual boot with Linux
      Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux,offline
      Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline

      2 users thanked author for this post.
    • #2294443

      Having had so many problems with the ESU scheme, I finally gave up on it and considered it £60 wasted, despite using hours of web surfing looking for answers that didn’t work.

      I thought “Why not?!” and installed the only available option of Windows 10 2004. I have been following your site for advice, and made the decision to install the updates, minus the optional preview. I have to say I was pleasantly surprised not to have any obvious issues with the update.

      I have noticed though that the Windows Defender Smartscreen is running a lot and using 14% of my Intel i7 7700K Quad CPU for long periods of time. I cannot however honestly attribute this to any update. However it is an issue and trying to use the web just confused things, as any opinions/answers given were for earlier versions. And there are changes!

      One suggested setting MsMpEng.exe “Affinity” (number of CPU’s used) in GPedit.msc; to a lower level, unfortunately, this has”Access Denied” when I tried, though it did not seem to use a lot of the CPU, it did use a lot of memory. I then saw that the process pointed to Smartscreen.exe. Here I could set affinity to half, though it made no difference.

      Lastly on this topic, I would like to say that when I unplugged my USB External drives, Smartscreen seemed to stop running for a while and only com on during ‘opening an App’ or going on the ‘Web’; this was the expected use for it all along.

      For Clarification, my USB External drives are a 4TB WD-Elements (USB Type A) and a 20TB WD-My Book Duo (USB Type C) set to raid 1 (Mirror); I see no reason for this behaviour, as these disks only run at night on a schedule (usually). Unfortunately, again, I cannot state that this was the cause of the cumulative update, but can say there are differences in access between versions of Windows 10. I wish I had tried an earlier version first!

    • #2294452

      On my Win10 Pro pc version 1909 build 18363.959:

      Do you mean click: “check for updates”??

      What about: KB 4562900? I had it in hidden updates, now it disappeared.

      I also have a hidden Silverlight update Kb 4481252: I thought that app no longer existed. Unhide it?

       

      On my Win10 Home 1909, build 18363.959:

      How do I set metered connections to ON?

      Just click resume updates?

      wushowhide on this pc does not show version 2004 to hide.

      • #2294473

        Do you mean click: “check for updates”??

        NEVER click: “check for updates.” It doesn’t mean “check.” It means download and install everything pending (available) without notification.

        What about: KB 4562900? I had it in hidden updates, now it disappeared.

        When a hidden update is superseded by a pending update, the hidden update will disappear b/c it is no longer available.

        How do I set metered connections to ON?

        Metered connections does not have a direct relation to Pause.
        Set Metered Connections ON/OFF in the Settings App->Network->Status

        You can leave Silverlight where it is.

        1 user thanked author for this post.
        Ken
    • #2294550

      On my W10 Home pc, I turned metered connections ON.

      wushowhide does not seem to work: I tried to hide NET preview and four Realtek software updates. They all appeared again. The only one that stayed hidden is  Silverlight.  Any solution?

      CU 4565351 appears to be stuck at 70% “getting things ready”. Now what? Reboot and see what happens?

      On my W10 Pro pc, two updates installed without any problems.

      • #2294560

        If yu have metered connections ON, it may prevent the CU from completing the download.

        1 user thanked author for this post.
        Ken
    • #2294552

      PS: on Home pc, Feature update appeared but I have the option to “download and install”.

    • #2294565

      If yu have metered connections ON, it may prevent the CU from completing the download.

      Yes, I got the option to continue downloads, which I did….. but the .NET preview also downloaded as well as the Realtek updates. Now I have paused it all again, pending the rest of your responses.

      • #2294568

        If it has finished downloading all the updates, all of them will install on reboot. Further Pausing is useless.
        After the update completes, then Pause so you won’t get the Sept updates tomorrow.

        1 user thanked author for this post.
        Ken
    • #2294616

      Amazing: on my Home pc,  the hidden updates stayed hidden after resuming updates again, only the 3 updates I left available installed successfully!

      1 user thanked author for this post.
    • #2294641

      Success!!! Here to report all August updates installed successfully, without any unwanted updates being offered or installed in the background.  Updated Build# v1909 18363.1016 (previously 18363.959) on both Win10 Pro x64 v1909 PC’s.  Flawless!

      Kudos to @Woody, @PKCano, @Alex5723, @PatchLady, and all the other contributing forum members for your knowledge, assistance,  and patience walking me through this process, thank you!

      This is the first monthly update where I’ve trusted and ran AKB2000016 Guide for Windows Update Settings with Sections 3 & 4 followed exactly as written and began using wushowhide properly.  It took me a while to get here.

      I’ve been following the forum for quite some time, but started to really pay attention with the June updates, specifically on June 10th, the day after Patch Tuesday.  Thankfully v2004 was “still not ready for my PC’s yet”…whew.

      During the month of June I applied most of the settings outlined in these articles to prepare for the July update.  I did everything other than disable “Pause Updates,” I still didn’t “trust” this setup would work for me and had no idea of how wushowhide works, let alone, when to run it.  This was a practice month.  July updates were deferred until later in the month, released from wushowhide, and installed after Woody gave the thumbs up, but still had Pause Updates in play.

      I then tempted fate and disabled Pause Updates in preparation for August.  August updates came in, including .NET preview.  Ran wushowhide and hid the updates.

      Defcon 4 hits for September, “get all August updates installed.”  Everything worked like a charm…perfection.  I ran wushowhide to see what was already hidden, KB4565351 and others.  Ran it again to see if any updates were available to hide, nothing.  Opened wushowhide this time to release KB4565351 for update.  Opened wushowhide a fourth time (before opening WU) to get it “staged,” ready to search and hide if WU presents anything I didn’t want.  Opened WU, KB4565351 not showing up.  Waited for WU to check on its own and later in the day KB4565351 appears, click download and installs.

      On a side note, I learned so much more than just deferring and installing the Cumulative Updates.  After reading many other threads on Ask Woody, I created a “playbook” of how and what to do for the monthly CU, .NET, other KB’s to watch out for, what to allow for installation, Service Stacks, optional updates, how to determine if an update was installed but not showing in Update History, and many more.  It helped me develop a plan of what, how, and when to maintain my systems with greater control instead of letting the “Mothership” have more control than what I prefer.

      Thank you again,

      Speed

      ASUS TUF SABERTOOTH Z170s Motherboard, Intel i7-6700k CPU, Corsair 32GB DDR4-3200 RAM, ASUS ROG STRIX GeForce GTX-1070 Video Card, 1x BPX M.2 240GB NVMe SSD, 1x Samsung 850 EVO 1TB SSD, 2x WD Black 6TB HDD, Windows 10 Pro 64bit v1909

      • This reply was modified 4 years, 6 months ago by Speed Racer.
      3 users thanked author for this post.
    • #2294837

      I have Windows 10 Pro 1909 OS Build 18363.959 and when I check Windows Update I don’t get anything for August 2020 on one computer and on the second computer I only got the .net preview.

      I have Feature Updates set for 360 days and Quality Updates set for 30 days on both computers

      I’m mainly concerned about any security updates I may not be getting

      • #2294839

        If you want Aug updates, set your Quality Update deferral to 10 (before MS releases Sept updates at 10:00am PDT US – in about 2 hours from this post). You are blocking the Aug updates from Windows Update with the deferral.

        If you do this, you have to finish the updates and put the deferral back to the higher value BEFORE the Sept release.

        See AKB2000016 for information on Update settings.

        2 users thanked author for this post.
        • #2295142

          PKCano,

          Thank you so much, your instructions worked well.  I’m new to Win 10 and it’s challenging learning all of the settings and tricks for updates.  I miss the simplicity of Win 7.

          1 user thanked author for this post.
      • #2294850

        I also have them on 360/30 – permanently. If you want to avoid having to change deferrals every time, just leave them as is and download the monthly updates via https://www.catalog.update.microsoft.com/Home.aspx once DEFCON is on 3 or more. Works like a charm.

    • #2294869

      I successfully installed my Win10 version 1909 updates on my main desktop machine yesterday, notably the cumulative update KB4565351 and the preview .Net Framework KB4570723. Both completed within about 45 minutes. Version 2004 remains an optional offering.

      I am no longer handling Windows updates on my Win7 second machine as I have in the last few days installed 0patch Pro on it and set Windows Updates to “Never check”.

      1 user thanked author for this post.
    • #2294880

      Re: Malicious Software Removal Tool

      Late last night (September 7) I clicked “Resume updates.” The Malicious Software Removal Tool was not offered even though Microsoft previously announced that the tool would be issued on the second Tuesday of February/May/August/November.

      Has anyone seen the August version?

      Windows 10 Pro version 1909

      2 users thanked author for this post.
      • #2294975

        Windows 10 Pro version 1909

        I haven’t seen an August version of the MSRT, but there was one (v5.83) in the WU queue today, Tues Sept 8 (Patch Tuesday). I figure it’s the September version.

        I’ve hidden the3 September patches that came down the pike today — dotNET CU for 1909–KB4576484, CU for 1909–KB4574727, and MSRT x64 v5.83)

        2 users thanked author for this post.
      • #2294976

        Someone had stated a few months ago that, starting May 2020, MSRT will be released on a quarterly basis.

        Win 7 SP1 Home Premium 64-bit; Office 2010; Group B (SaS); Former 'Tech Weenie'
        1 user thanked author for this post.
        • #2294977

          Yes, I read that, and the quarterly months were supposed to be February/May/August/November. Maybe, it’s changed to the financial quarterly months of March/June, September/December ??

          1 user thanked author for this post.
    • #2294973

      can anyone please let me know if the current MS-DEFCON 4 includes the Preview Cumulative Update that MS usually releases in the weeks following Patch Tuesday

      No. Defcon 3/4 never includes preview updates.

    • #2295264

      I have 32-bit Windows 7 Professional with Extended Security Updates.  I got a late start this month with installing the August patches.  I didn’t start until after Patch Tuesday for September.  I went ahead and installed the Windows Updates today (Wednesday September 9th) and everything went OK with that.  But I have some questions about the Office and .NET Framework updates.  Some of the Office Updates and the .NET Framework Update that were offered to me by Windows Updates prior to Patch Tuesday are no longer shown now.  I assumed that they should be installed so I tried installing them manually.  The ones for Office installed OK,  but I don’t know how to install the one for .NET Framework  (KB4570506),  because when I go to the Microsoft Catalog for KB4570506,  it lists about six different files to download,  some of which are .exe files and some of which are .msu files,  and also it doesn’t say specifically that these are for 32-bit,  which is the “bittedness” of my computer.  Windows Updates does offer me a newer version of the .NET Framework,  which is KB4576628,  but I assume that we shouldn’t install that until Woody gives the go-ahead for the September Updates,  which is probably a few weeks from now.  What should I do in the meantime?  Should I install all six of those .msu and .exe files that I see listed for KB4570506?

      Also,  Windows Updates is now offering me some newer Office updates that it hadn’t offered to me prior to Patch Tuesday.  Should I just hold off on installing those until Woody gives the go-ahead for the September Updates?

      • #2295270

        See #2294901 and the links therin. If you HIDE the Sept updates in Windows Update, the Aug patches will show up for installation. Right click on the update and choose hide.

        Most of the information about Win7 is there. That post talks about generally what patches you need.

        The .NET patches have the version of .NET in the name of the download. If you have .NET 4.5 installed there will be a “45” in the name of the patch you need (for example). If you click on the Rollup in the Catalog you only need the ones for the version(s) you have installed on your computer. One of the posts linked shows you that information. But if you have ESU, you should be offered the .NET Rollup through Windows Update and Windows will take care of what you need.

        Don’t worry about patches that have disappeared from Windows Update. With Cumulative updates, the current/latest one contains all the past ones. If you have ESU, let Windows Update decide what you need.

        If you need the information about August updates see #2287923.

        • #2295273

          PK:  Thanks for your response.  I took a look at the links you provided,  but some of that is over my head.  As I mentioned above,  I’ve already installed the Office Updates by manual means.  So for the .NET Framework update,  should I just go ahead and hide the September updates,  and then when the August .NET Framework update shows up,  install that and be done with it for August?  If I do that,  I gather from your link that the SSU for September will not show up,  as SSUs in the past have done,  Is that correct?   And also,  I had asked in my previous post about  the Office Updates that showed up after yesterday’s Patch Tuesday.   Should I leave those uninstalled until Woody gives the go-ahead for the September updates?

          • #2295279

            Hide any Sept patches (including Office).
            Be sure you have the JULY SSU KB4565354 installed – it is a prereq for the Aug patches.
            The Aug patches should then show up.
            The Aug SSU KB4570673 will be offered after you install all the Aug patches and reboot. The Windows Update Important update queue has to be empty for it to show up.

            When you get through, be sure to unhide the Sept patches (so you won’t forget).

    Viewing 48 reply threads
    Reply To: Reply #2294007 in MS-DEFCON 4: Install the August updates, but avoid the Optional and non-security patches

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information:




    Cancel