News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • December 2019 Patch Tuesday running commentary

    Home Forums AskWoody blog December 2019 Patch Tuesday running commentary

    Viewing 25 reply threads
    • Author
      Posts
      • #2017420 Reply
        woody
        Da Boss

        I’m looking at 133 downloadable patches on the Update Catalog. Details to follow.
        [See the full post at: December 2019 Patch Tuesday running commentary]

        4 users thanked author for this post.
      • #2017432 Reply
        anonymous
        Guest

        Wow, Cumulative Win 8,1 update this month… 493MB, and it’s the only patch… curious.

        • #2017504 Reply
          warrenrumak
          AskWoody Plus

          It’s large because the monthly Windows 8.1 cumulative update (as released on the Download Center) includes every patch released since Windows 8.1 Update was released in 2014.  Hence the term “cumulative”.

          If you install directly through Windows Update, the download is smaller because it knows what patch you level you already have, so it only sends you what you need.

          • This reply was modified 6 months, 3 weeks ago by warrenrumak.
          • #2017552 Reply
            Microfix
            AskWoody MVP

            It’s large because the monthly Windows 8.1 cumulative update (as released on the Download Center) includes every patch released since Windows 8.1 Update was released in 2014. .

            I’m sure it was October 2016 when CU’s were introduced for Win7 and Win8.1 and patches previous to this were singular.

            | Win8.1 Pro x64 | Linux Hybrids x86/x64 | Win7 Pro x86/x64 Offline |
            1 user thanked author for this post.
      • #2017437 Reply
        PKCano
        Da Boss

        Group B Security-only Updates and the IE11 Cumulative Update have been updated for December on AKB2000003.

        Notice: the Security-only patch contains a Win7 EOL nag screen

        IMPORTANT Starting on January 15, 2020, a full-screen notification will appear that describes the risk of continuing to use Windows 7 Service Pack 1 after it reaches end of support on January 14, 2020. The notification will remain on the screen until you interact with it. This notification will only appear on the following editions of Windows 7 Service Pack 1:

        Note The notification will not appear on domain-joined machines or machines in kiosk mode.

        UPDATE: @abbodi86 has updated the  win10Tel script in AKB2000012 to surpress the Win7 EOS notification installed with Rollup KB4530734 and SO KB4530692 . See #2017648.

        NOTE: There is a new SSU for Win7 KB4531786.

        • This reply was modified 6 months, 3 weeks ago by PKCano.
        • #2017546 Reply
          Charlie
          AskWoody Plus

          Notice: the Security-only patch contains a Win7 EOL nag screen

          D#%&!  That really makes me mad.  I really hope there’s a way to undo that Nag.  Maybe a registry entry or something.

          Thanks very much for letting us know about that PK.

          Win 7, Sandy Bridge 3.3GHz, Linux Mint 19.1, Klaatu barada nikto

          • #2017572 Reply
            woody
            Da Boss

            Looks like you only have to click on “Do not show again” or something similar.

            6 users thanked author for this post.
            • #2017611 Reply
              OscarCP
              AskWoody Plus

              In Windows 7, at least, the magic word is “hide”. Open Windows Update and right-click the name of the unwanted update listed there as waiting to be installed, to get the choice to hide it. Or any other update you don’t want. I always hide the S&Q Rollup and all the Preliminary releases, plus whatever else I don’t want ever to be installed.

              If later there is a good reason to change your mind, you can look or the update in the “Hidden Updates” list, also somewhere in Windows Update, to “unhide” and install it.

              Windows 7 Professional, SP1, x64 Group W (ex B) & macOS + Linux (Mint)

              1 user thanked author for this post.
              Geo
          • #2017757 Reply
            Pierre77
            AskWoody Plus

            This may be of some use on how to remove it.

            EOS-Windows-7

             

            Attachments:
            1 user thanked author for this post.
            Pim
        • #2017551 Reply
          anonymous
          Guest

          Well that just means that I do not have to worry about Installing that “Security Only” Dec 2019 patch on any of my 4 Windows 7 laptops. I’ll just have to live with skipping 2 of the other months of “Security Only” updates and Dec as well.

          Some folks have been skipping updates starting from Oct 2016 and onward  so a few skipped months are not the end of the world.

          That 8.1 rollup is large but does that include Telemetry as well and will there still be a Group B option via the update catalog for any 8.1 “Security Updates” that may need to be skipped.

        • #2017589 Reply

          I know this going to sound kinda dumb, but Patch Lady said she was going to be looking into how 7 Pro users could ge an extra year for $50; Woody expressed interest too. Now, I went thru all those links about how to get an ESU, and I’m more confused than ever.  Questions:

          1. Has anyone here successfully gotten a $50 ESU yet?
          2. Can you use PayPal?

          I guess I need a simpleton’s road map for this.

          Thanks to all!

          Win7 Pro SP1 64-bit ESU, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", Group "Patch List", Multiple Air-Gapped backup drives in different locations, "Don't auto-check for updates-Full Manual Mode." Linux Mint Greenhorn
          --
          "A committee is the only known form of life that has at least six legs and no brain."

          -Robert Heinlein

          1 user thanked author for this post.
      • #2017461 Reply
        b
        AskWoody Plus

        We’ll keep you posted on any identified bugs, of course.

        How will you know if “all Windows users need to take a few minutes to make sure our machines don’t have a “Kick Me” sign pasted on them.”?

      • #2017464 Reply
        anonymous
        Guest

        There is a reincarnation of KB4493132 (Windows 7 EOS nagware). This time, it is included in KB4530692 (December Security-only update). Particularly, it is
        Eosnotify.exe (version 6.1.7601.24541, dated 6-Dec-19,1:40).
        It is mentioned in https://support.microsoft.com/en-us/help/4530692/windows-7-update-kb4530692:

        IMPORTANT Starting on January 15, 2020, a full-screen notification will appear that describes the risk of continuing to use Windows 7 Service Pack 1 after it reaches end of support on January 14, 2020. The notification will remain on the screen until you interact with it. This notification will only appear on the following editions of Windows 7 Service Pack 1:

        Note The notification will not appear on domain-joined machines or machines in kiosk mode.

        Checked file information for KB4530692 (available at https://download.microsoft.com/download/d/8/4/d84af77d-cd59-46d6-a5ad-c83effa42882/4530692.csv), and found no telemetry stuff this month.

        And, there is also new Servicing Stack for Windows 7 – KB4531786. Of course, we have also Cumulative security update for IE11 – KB4530677.

        5 users thanked author for this post.
        • #2017513 Reply
          Pepsiboy
          AskWoody Lounger

          Can the “Eosnotify.exe” be removed before installing? Or, can it be removed after install and before it starts to nag?

           

          Dave

          2 users thanked author for this post.
          • #2017523 Reply
            b
            AskWoody Plus

            Isn’t the easiest way just to click “Don’t remind me again” when it appears?

            • #2017550 Reply
              Charlie
              AskWoody Plus

              And trust MS to not nag you again to convert to Win X?

              Win 7, Sandy Bridge 3.3GHz, Linux Mint 19.1, Klaatu barada nikto

              1 user thanked author for this post.
            • #2017613 Reply
              Seff
              AskWoody Plus

              The easiest way is to anticipate EOL by a couple of months and not install any further updates from and including the December ones.

              That’s a course I may end up taking anyway given that the November updates are the likely cause of an ongoing problem with my first machine as a result of which I haven’t installed them on my other machine. I’ll review the situation when I get to the bottom of the problem, but I won’t lose any sleep over missing the last couple of months worth of updates from here on, while I finalise what to do in terms of upgrading my existing machines or replacing at least one of them as I was previously planning on doing during the 1st or 2nd quarter of 2020. It’s either carry on with Windows 7 or move to Windows 10 for me, there aren’t any other viable options, but I’m not going to panic over sorting it by mid-January, that’s for sure.

              • #2017919 Reply
                GreatAndPowerfulTech
                AskWoody Plus

                Seff: You should look at the 0patch.com website to get critical updates for Windows 7. Woody wrote about it recently, as did Martin on ghacks.

                GreatAndPowerfulTech

        • #2017603 Reply
          anonymous
          Guest

          KB4531786, and why so many Servicing Stack updates in the final months of Windows 7’s life. And I’m beginning to suspect that something else is going on there.

          I’ve already removed MSE from the 3 out of 4 Laptops that had MSE installed because one of those laptops had update issues related to MSE’s signature errors and my event logs full of MSE errors on that one laptop after Installing Nov’s SSU and trying to install the Nov 2019 Win 7 security only update that failed because the laptop black screened while rebooting to apply the Nov SO update.

          I’m really wanting to hear more about just what’s having to be fixed, on almost a monthly basis, with these Windows 7 Servicing Stack updates.

          MSE is going by by as well but MSE really has had issues starting properly after an update reboot over the past 8 months for me on my 3 laptops that had MSE installed. And on more than on occasion after restarting to apply updates MSE would itself fail to start at all and I’d have to reboot again to be safe.

          I guess after 7 goes EOL it will take a good while before other software products begin to drop support as well but how long did that take for XP once XP’s time was “officially” up before the third party software ecosystem transitioned fully to Windows 7.

      • #2017503 Reply
        sheldon
        AskWoody Plus

        Win10 1903 – I see an autopilot update.  What is this about?

        • #2017516 Reply
          b
          AskWoody Plus
        • #2017573 Reply
          woody
          Da Boss

          It’s being offered to all Pro machines, whether they have AutoPilot or now.

          It’s also being re-offered, after installation.

          Just like October. Undoubtedly the same bug. I bet MS pulls it in the next few hours.

          2 users thanked author for this post.
          • #2017579 Reply
            sheldon
            AskWoody Plus

            Thanks – I will leave it hidden via wushowhide.

          • #2017624 Reply
            howardagoldberg
            AskWoody Plus

            I was offered the auto-pilot update on 1909 x64 Pro. Installed. Was not offered again after reboot. So, I can’t speak to whether or not the update *should* have been offered, but it did install and checking for updates after reboot shows that I’m up to date …

            1 user thanked author for this post.
            b
      • #2017514 Reply
        Tex265
        AskWoody Plus

        Moved to Win10 ver 1903 several weeks ago.

        Checked the Forums here at Woody regarding 1909 – nothing much negative reported.

        Can someone advise if we have the go-ahead to upgrade to 1909 and if not, what is/are the issues we are waiting a fix for?

        Windows 10 Pro x64 v1909 and Windows 7 Pro SP1 x64 (RIP)
        • #2017518 Reply
          b
          AskWoody Plus

          It’ll be interesting to see if MS fixed the File Explorer Search bugs in 1909 that have been widely reported.

          2 users thanked author for this post.
        • #2017533 Reply
          PKCano
          Da Boss

          This is what Woody wrote in a ComputerWorld article:

          Version 1909 — The minimally invasive “service pack” version — has a few bugs of its own, mostly Explorer Search related, but it’s only been available for a few weeks. If you trust Microsoft’s patching ability, there’s no reason to delay moving to 1909. On the other hand, if you want to wait and see what happens, you’d be well advised to wait a couple of months or more.

      • #2017541 Reply
        Alex5723
        AskWoody Plus

        The notification will remain on the screen until you interact with it.

        Microsoft will display a red X that will install Windows 10 1909 when clicked on ?

        6 users thanked author for this post.
      • #2017575 Reply
        CraigS26
        AskWoody Plus

        A W10-1709 new HP desktop purch’d Feb ’19 …  I’m at 1909 and continue issue-free use and Updates of Win 10. 2016 Hm-Stdnt Office C2R also updated rapidly. Only show Kb4530684 Dec Cum Update and Kb 4533002 Net Frmwk (I’m 4.8) in both Settings & Con Panel WU History. Macrium images always ready at WU …. W10-64 1909 — 18363.535 ……………

         

        W10-64 1909 Pro / Hm-Stdnt Ofce '16 C2R / HP Envy i5-8400/ 12 GB / 256G SSD + 1 TB HDD / InSpectre #8 = GREEN

        • This reply was modified 6 months, 3 weeks ago by CraigS26.
      • #2017590 Reply
        anonymous
        Guest

        Seems like EOS nagware can be disabled in a simple way using taskschd.msc (Task Scheduler).

        It creates new grop (under: \Microsoft\Windows) , named ‘Setup’, which contains two tasks: ‘EOSNotify’ and ‘EOSNotify2’. By default, the latter is set to run everyday at 12 AM, starting from January, 15. They simply run ‘%windir%\System32\EOSNotify.exe’

        It can be disabled and/or deleted via command prompt:

        Disable:

        schtasks /Change /DISABLE /TN “Microsoft\Windows\Setup\EOSNotify”

        schtasks /Change /DISABLE /TN “Microsoft\Windows\Setup\EOSNotify2”

        Removal:

        schtasks /Delete /F /TN “Microsoft\Windows\Setup\EOSnotify”

        schtasks /Delete /F /TN “Microsoft\Windows\Setup\EOSnotify2”

        2 users thanked author for this post.
      • #2017641 Reply
        anonymous
        Guest

        Not going to install Dec. updates yet, but I noticed the .Net update list has an update to 4.8. I hope that it doesn’t install 4.8 as I don’t want it. Does anyone know if it’s going to install it or just update it if it’s already installed ?

        • #2017653 Reply
          PKCano
          Da Boss

          KB4533095 is the .NET Rollup for Win7. If .NET 4.8 is not installed, it won’t install the .NET 4.8 or the update for it.
          If the patch says MS .NET Framework  4.8,x it is the installer for that version and if you don’t want it, don’t install it.

          • #2018017 Reply
            anonymous
            Guest

            The dot Net rollups are cumulative so because of that  I usually skip those for a few months to see if any issues have occurred. So I’m usually skipping a few dot Net rollups by the time the next update arrives if they come in rapid procession.

      • #2017649 Reply
        abbodi86
        AskWoody_MVP

        1903 Autopilot patch seems pulled

        2 users thanked author for this post.
        • #2017671 Reply
          woody
          Da Boss

          Doesn’t surprise me.

          • #2017714 Reply
            sheldon
            AskWoody Plus

            Had it hid in wushowhide and now it gone

            1 user thanked author for this post.
        • #2017890 Reply
          woody
          Da Boss

          The KB article has been modified to say:

          This update was available through Windows Update. However, we have removed it because it was being offered incorrectly. When an organization registers or configures a device for Windows Autopilot deployment, the device setup automatically updates Windows Autopilot to the latest version.

          Note There is no effect on Windows Autopilot being offered to Windows 10 devices. If you were offered this update and do not use Autopilot, installing this update will not affect you. Windows Autopilot update should not be offered to Windows 10 Home.

          Translation: We screwed up again, just like we did in October.

          1 user thanked author for this post.
      • #2017670 Reply
        anonymous
        Guest

        I installed this patch just now on 1909 and encountered an issue.

        After installing and rebooting, I noticed the panel with pinned icons was missing from the start menu. Additionally, programs that are not pinned (appears to be EVERY non UWP app stored in %APPDATA% and C:\ProgramData) also disappeared, despite the shortcuts being on my disk just fine.

        After a minute, the pinned panel itself came back up. All the shortcuts are still there, but the text and icons are missing, and they just say things like W~C:\Program\path or W~UUID or W~{UUID} or W~Microsoft.AutoGenerated.{UUID}

        My search indexing service is off (but it’s always been off and the startmenu has worked without hitches). Probably not a dealbreaker like that 100% CPU usage bug, but annoying. It may resolve after a restart or a log in/log out like some minor start menu issues I’ve ran into.

        Not sure how this happened with a security patch, even when I ran into the CPU usage bug all the shortcuts were still there… Never seen anything like it.

        • #2017677 Reply
          anonymous
          Guest

          And… it’s gone after a reboot (unsurprisingly). Not sure if any of the updates I installed today (below) even impact the start menu (I guess I could look at the manifests). Maybe the update process just exposed some race condition or loose logic. But I’ve never had this happen before.

          • Windows Malicious Software Removal Tool x64 – December 2019 (KB890830)
          • 2019-12 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4533002)
          • 2019-12 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4530684)
          • Update for Microsoft Visual Studio 2010 Tools for Office Runtime (KB3001652)
      • #2017678 Reply
        anonymous
        Guest

        I’ve read on another forum that adding this reg key will get rid of the EOS nag.

         

        HKEY_LOCAL_MACHIN\Software\Microsoft\Windows\CurrentVersion\EOSNotify] “DiscontinueEOS”=dword:00000001

        • #2017942 Reply
          ashfan212
          AskWoody Lounger

          I have seen conflicting information as to whether the registry key belongs under HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE. Can someone please clarify.

          Also, the registry path cited above is appearing as truncated. I would assume that the intended registry path ends with …CurrentVersion\EOSNotify but I am not sure.

          • #2017959 Reply
            abbodi86
            AskWoody_MVP

            It works for both, the HKEY_LOCAL_MACHINE one should suppress it for all users

            Windows Registry Editor Version 5.00

            [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\EOSNotify]
            “DiscontinueEOS”=dword:00000001

            [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\EOSNotify]
            “DiscontinueEOS”=dword:00000001

            2 users thanked author for this post.
        • #2017943 Reply
          Microfix
          AskWoody MVP

          see:
          https://www.bleepingcomputer.com/news/microsoft/windows-7-to-show-full-screen-windows-10-upgrade-alerts/
          looks like it’s HKCU

          | Win8.1 Pro x64 | Linux Hybrids x86/x64 | Win7 Pro x86/x64 Offline |
          1 user thanked author for this post.
      • #2017694 Reply
        James Bond 007
        AskWoody Lounger

        An unavoidable nag screen for Windows 7 users? I wonder if the nag screen can be dismissed permanently or if it will appear on every boot like that “Unsupported Hardware” screen which appears every time I boot Windows 8.1 on my system using a Ryzen 7 1700X CPU (curiously it does not appear when I boot Windows 7 on that system).

        The note does not mention Windows 7 Enterprise so if I am running that version I assume the nag screen will not appear.

        If there is no way to dismiss it permanently I may consider not installing the patches for the last 2 months (except Windows 7 Enterprise). Let the Windows 7 systems stay on November 2019 patch level.

        Hope for the best. Prepare for the worst.

        • #2017756 Reply
          OscarCP
          AskWoody Plus

          I think that I’ll also stay away from those two last Security Only patches and try using 0patch (the free version) instead, until I decide whether to switch to their paid ‘Pro’ version or to stop using 0patch altogether.

          Windows 7 Professional, SP1, x64 Group W (ex B) & macOS + Linux (Mint)

      • #2017701 Reply
        RetiredGeek
        AskWoody MVP

        Hey Y’all,

        I accidentally installed the Dec patches on my TEST machine. How did I do that you may ask. Well I turned it on and went do do something else and when I returned there is the “Reboot Now” message. Well since I have a image taken Friday and It’s a test machine I said what the heck. I’ll let you know if I run into any problems. 😎

        Win-Dec-Updates

        May the Forces of good computing be with you!

        RG

        PowerShell & VBA Rule!
        Computer Specs

        Attachments:
        1 user thanked author for this post.
      • #2017718 Reply
        Susan Bradley
        AskWoody MVP

        How about making it easier to buy the extended support updates and not just code up a nag screen?

        Susan Bradley Patch Lady

        10 users thanked author for this post.
        • #2017735 Reply
          Carl D
          AskWoody Lounger

          Yes, MS seem to be great at coding things like “W7 end of support” and “W7 and 8.1 unsupported hardware” nag screens and the entire former (has it really ended?) GWX campaign.

          Perhaps they should concentrate a bit more on coding security and bug fixes instead.

          A little less ‘Ninja Cats’ and ‘Taco Hats’ and instead, getting on with the job of providing a secure and stable operating system for all of their paying customers.

          Gigabyte GA-B250M-D3H Motherboard, Intel i5-7600 CPU, 32GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 860 EVO 250GB SSD, 1x Samsung 850 EVO 250GB SSD, Windows 10 Professional 2004 64bit.

          • This reply was modified 6 months, 3 weeks ago by Carl D.
          2 users thanked author for this post.
        • #2017749 Reply

          Right on, Susan!

          (See above post #2017589)

          I followed all those links in PCano’s post #2017437, and I wound up more confused than ever. Maybe that’s the idea: to have the process so labyrinthine so ordinary folks with 7 Pro can’t figure it out!

          Win7 Pro SP1 64-bit ESU, Dell Latitude E6330, Intel CORE i5 "Ivy Bridge", Group "Patch List", Multiple Air-Gapped backup drives in different locations, "Don't auto-check for updates-Full Manual Mode." Linux Mint Greenhorn
          --
          "A committee is the only known form of life that has at least six legs and no brain."

          -Robert Heinlein

          1 user thanked author for this post.
        • #2017879 Reply
          woody
          Da Boss

          Here, here!

      • #2017732 Reply
        E Pericoloso Sporgersi
        AskWoody Plus

        I just patched my Win-10-Home-64bit-1909.

        Microsoft fed me
        KB4533002 Cumulative Update for .NET Framework 3.5 and 4.8
        KB4530684 Cumulative Update (OS Build 18363.535)

        It installed flawlessly.

      • #2017921 Reply
        IndyPilot80
        AskWoody Lounger

        Not sure if I’m missing something here. I see KB4533002 (.NET Update) in WSUS. The title says for 1903 but in the description it says for 1903 and 1909. My test workstations aren’t getting it from WSUS and it says it isn’t applicable. But, when I use “Check Online for Updates from Microsoft”, it downloads it but it update title says it’s for 1909.

        Have they not released it for 1909 in WSUS yet?

      • #2017987 Reply
        anonymous
        Guest

        All our Server 2012 (non R2) servers got caught in restart loops. Had to boot into Safe Mode to break out of it. Server 2016 installed it, restarted multiple times, then came up. KB4530689 shows installed in history and is also pending/available for install. So looks like it reverted. Haven’t checked the R2 boxes yet since they all seemed to reboot and come up in our early ring that auto updates.

        1 user thanked author for this post.
      • #2017994 Reply
        Microfix
        AskWoody MVP

        Woody, On a slight side note to the running commentry..MSFT has pulled December 10th Office 365 Client Updates From Catalog:
        More info over on bleepingcomputer

        | Win8.1 Pro x64 | Linux Hybrids x86/x64 | Win7 Pro x86/x64 Offline |
        1 user thanked author for this post.
        • #2018067 Reply
          abbodi86
          AskWoody_MVP

          How come Office 2019 still in the catalog?

          i’m pretty sure the error is caused by the switch from sha1/sha2 signature to sha2 only

          1 user thanked author for this post.
      • #2018015 Reply
        anonymous
        Guest

        I will report a big problem with KB4530734.  Using Windows 7 Professional.

        On reboot, the system got stuck on “preparing to configure windows.”  I waited maybe 15 or 20 minutes.  I had to do a hard reboot, then boot into safe mode.  Safe mode then gave me a message saying IIRC update failed, reverting to previous version.  After a bit of activity, the safe mode booted itself into regular mode, where I got the same message, update failed, reverting to previous version.  The system then came up normally.

        I gave it another try, since windows update reported this was still a pending update.  I had to go through exactly the same process.  So I have hidden KB4530734 and will not be dealing with it again.

        The November patch failed and I could only install it manually.  Up until November, I installed all important updates easily and quickly.  I don’t know what is going on, but I am inclined to ignore the next and final Windows 7 patch.

        • #2018031 Reply
          jabeattyauditor
          AskWoody Lounger

          It’s quite likely you didn’t wait long enough before interrupting the update process.

          • #2018033 Reply
            anonymous
            Guest

            Thank you for this answer.  I will admit I sort of panicked…this process has been more or less immediate during all previous updates.  I know it was large.  I wonder if anyone else using W7 Professional has installed this and what is an expected time to wait in this particular case.

            • #2018036 Reply
              PKCano
              Da Boss

              We are still under DEFCON-2 for December patches. That means WAIT and let someone else be the Guinea pig Beta tester.
              When Woody increases the the DEFCON number to 3 or greater, he gives instructions for safe patching. Ther is no hurry to patch immediately.

              1 user thanked author for this post.
              • #2018050 Reply
                anonymous
                Guest

                Thanks for the very helpful discussion.  Based on the first answer, I tried again and it took almost exactly 20 minutes to finish, and it did finish.  I was just a bit too impatient last night.

      • #2018126 Reply
        anonymous
        Guest

        The MS Update Catalog shows a December 2019 cumulative update for W10 1803 (KB4530717) — seems as if MS is extending security update support even for EOL Win 10 versions.

        • #2018130 Reply
          PKCano
          Da Boss

          That’s not for consumer Win10 1803. Win10 Enterprise (and I think Education) have an extra year of support that the Home/Pro do not have.

          1 user thanked author for this post.
          • #2018258 Reply
            anonymous
            Guest

            Thanks PKCano for comment.  However, it’s not clear how MS is controlling this update and its application to different Win editions.  It actually installs successfully on Win10 Pro 1803 64 bit by download and standalone Win installer, moving up from build 17134.1130 (Nov) to 17134.1184 (Dec).   No messages, errors, or immediate stability issues.  So it would seem that some 1803 users can continue to update 1803 manually from the Update Catalog a bit longer,  while checking on version 1909.

          • #2018366 Reply
            mn–
            AskWoody Lounger

            I am seeing this offered automatically for some otherwise normal-looking W10 Pro 1803 boxes.

            Something is definitely funny in here.

            Hm, right, should check the deferral settings on these… since I’m not seeing a feature update queued for them.

            1 user thanked author for this post.
      • #2018368 Reply
        mn–
        AskWoody Lounger

        Oh hey, my guinea pig 1909 box just failed the cumulative.

        Installation Failure: Windows failed to install the following update with error 0x800F0845: 2019-12 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4530684).

        So. That’s a 4th-gen Intel Core i5 (HD 4600 GPU)… Sophos AV/etc suite.

        • #2018393 Reply
          mn–
          AskWoody Lounger

          … Worked on the second attempt.

      • #2022222 Reply
        PKCano
        Da Boss

        Time to report my experience with December updates.

        + Win10 v1903 – Feature deferrals set to 365 days (no 1909, thank you). Updated KB4530684 Build 18362.535 without a problem.
        + Win10 1809 – Feature deferrals set to 365 days. Updated to KB4530715 Build 17763.914 without any problems.
        + Win10 v1803- Feature deferrals set to 365 days. Big surprise. It’s supposed to be EOL, but I was offered and installed KB4530717 Build 17134.1184. No sign of the offer for any later version or the “Download and install now” section b/c of the 365 deferral.
        + (4) Win8.1 Pro, one 32-bit, three 64-bit, using Windows Update, including updates for .NET, Office 2010 and MSRT. No problems.

        + (8) Win7 combination of  four h/w installs and four VMs. Two 32-bit Home, one 32-bit Pro, one 64-bit Home and three 64-bit Ultimate. All were done using Windows Update, including Rollups, .NET, Office 2010, and MSRT. In all cases the SSU was installed when it showed up AFTER the install/reboot.
        I did experience two reboots during the main install and the screen being black for longer than usual (but not excessively long). I just waited and the install completed with no problems.
        On the two 32-bit Home machines, when I ran CCleaner Portable as cleanup afterward, it crashed. Both machines are running Bitdefender Free. The fix was to make an exception for the ccleaner.exe in Bitdefender. I turned the exception off and on to prove the solution. This happened ONLY with 32-bit Home, and not with any other 32 or 64 bit combination.

        4 users thanked author for this post.
        • #2022814 Reply
          EyesOnWindows
          AskWoody Lounger

          PKCano wrote:
          +Win10 v1803- Feature deferrals set to 365 days. Big surprise. It’s supposed to be EOL, but I was offered and installed KB4530717 Build 17134.1184.

          Much to my surprise, running Windows 10 Pro Version 1803 with a 13 day update deferral and feature deferrals set to 365 days, I just had the same experience today.

          HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 1803
          Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 4.00 GB
          EyesOnWindows

      • #2022233 Reply
        Alex5723
        AskWoody Plus

        Win10 v1903 – Feature deferrals set to 365 days (no 1909, thank you). Updated KB4530684 Build 18362.535 without a problem.

        Upgraded Win 10 1809 Pro (by setting Feature deferrals to 120 days and Quality Updates to 0) to 1903 :
        KB4530684 (18362.535), KB4522741 (CU.NET), KB4519573 (CU .NET), KB4524569 (Servicing Stack), Flash Update.

        1 problem : creating new folder, files, copying files.. to an external USB 3.0 HD doesn’t show in Windows Explorer unless I click on the refresh icon.

        1 user thanked author for this post.
    Viewing 25 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: December 2019 Patch Tuesday running commentary

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