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
  • No fireworks, closing out 2019 updating

    Posted on Tracey Capen Comment on the AskWoody Lounge

    Home Forums AskWoody blog No fireworks, closing out 2019 updating

    This topic contains 7 replies, has 7 voices, and was last updated by  Myst 1 week, 6 days ago.

    • Author
      Posts
    • #2040932 Reply

      Tracey Capen
      AskWoody MVP

      PATCH WATCH By Susan Bradley The past year of Windows and Office patching sure had its ups and downs, false alarms, and true debacles. Fortunately, we
      [See the full post at: No fireworks, closing out 2019 updating]

      2 users thanked author for this post.
    • #2040978 Reply

      Pim
      AskWoody Plus

      The recommendation for Windows 7 is to add a DiscontinueEOS registry key with value 00000001 to prevent the EOL notification on January 15th. This registry key as well as the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\EOSNotify key are not present after installing the December rollup KB4530734 and thus have to be added manually. Would it not be simpler and less work to just let the notification appear on January 15th and then click “Don’t remind me again”? From what I understand that action also sets the DiscontinueEOS registry key to 00000001. I think accepting the notification once and then clicking “Don’t remind me again” is less effort.

      Also, the Newsletter refers to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\EOSNotify whereas other sites (e.g. ghacks) refer to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\EOSNotify. This confuses me, especially because one has to add the key manually. In my case, I think I will just sit out the notification and then click “Don’t remind me again”.

      ASRock Beebox J3160 - Win7 Ultimate x64
      Asus VivoPC VC62B - Win7 Ultimate x64
      Dell Latitude E6430 - Win7 Ultimate x64
      Dell Latitude XT3 - Vista Ultimate x86 (still...)
      Gigabyte GA-H110M-HD3 DDR3 - Win10 Pro 1809 x64

      • This reply was modified 3 weeks ago by  Pim. Reason: Link added
      2 users thanked author for this post.
      • #2084635 Reply

        Myst
        AskWoody Plus

        From what I understand that action also sets the DiscontinueEOS registry key to 00000001.

        I read this on a couple sites, at ghacks for one, sets the value to 1 after checking the “do not notify me again” box.

        Also, the Newsletter refers to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\EOSNotify whereas other sites (e.g. ghacks) refer to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\EOSNotify. This confuses me

        And I also saw this explained somewhere in my search (possibly again on ghacks, sorry I didn’t make note), the CURRENT user is just that, a single target, and the LOCAL machine defines the group of users on that particular system.

        Win7 SP1 Home 64-bit, GrpA / MacOS / Chromebook

    • #2041029 Reply

      WildBill
      AskWoody Plus

      Reviewed your Win8.1-Server 2012 R2 list for .NET Security/Quality rollups & double-checked the Master Patch List. Not seeing KB4533097, which is the rollup for everything (3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8). That’s a Recommended update that I see on my Win8.1 Windows Update. I know Woody & probably you consider Recommended the same as Optional, & it’s automatically unchecked on my system. Since I do my image backup before any updates (Windows & Office 2013 click-to-run), I’ll click it. Haven’t had problems with Recommended updates (so far… or at least, in a long while); assuming anything that needed to be fixed in .NET has been. According to raymondcc .NET Detector, I have 2.0 Service Pack 2, 3.0 Service Pack 2, & 3.5 Service Pack 1 installed.

      Windows 8.1, 64-bit, back in Group A... & leaning toward Windows 10 V1909. As long as it's a Lot Less Buggy!
      Wild Bill Rides Again...

      • #2041248 Reply

        anonymous

        I’m getting ready to go SATA SSD shopping to replace the spinning rust(With Windows 7 Pro) before installing the Windows 8/8.1 Pro that the Laptop is actually licensed to run. So I’m mostly thinking about the different SATA(Serial ATA) generations used and finding that correct SATA generation on my Laptop and how to query that on Windows 7. I’m assuming that it’s one of the SATA 3.# versions but I’m going to be installing Windows 8/8.1 from the Laptop OEM’s Supplied Wiindows 8 recovery DVDs onto a new SSD to replace that old Hard Drive that will still have Windows 7 Pro on it when its removed, with all my personal info removed/backed up to a USB drive.

        But I Skipped the Windows 7 Security Only updating for Dec 2019 to avoid that nagware and I’ll probably have 8.8.1 installed on one of my laptops before the Jan DEFCON3+ for that month’s final EOL updates happens. So I’m pretty much done with any Windows 7 Pro updating on that one laptop that’s going to have 8.1 installed in the next week.

        I’m still seeing that Dec 2019’s DEFCON level remains at 2 so I still have some remaining laptops to get squared away with a possible 8.1 install on one other and other options for some laptops that are really too old anyways. But it’s looking good for maybe installing the IE 11 patch for Dec 2019 and the Dec 2019 SSU for Windows 7 as well.

        • #2041275 Reply

          Paul T
          AskWoody MVP

          Any SSD that has the right connector will work on your controller because they are backward compatible.

          As you have 2 machines, why not make an image of one and then upgrade to W10?

          cheers, Paul

        • #2041318 Reply

          Matthew
          AskWoody Plus

          Anonymous, please let us know how your upgrade goes, and how you get everything on the new 8.1 SSD — programs and setting, etc. — basically back to the way they were on the 7 HDD.  (I’ve got a 7 Pro laptop with 8.1 license as well.)  Thanks.

           

          • #2041329 Reply

            anonymous

            I’m not actually migrating any of the old data or software over and as I only use Open Source software mostly I’ll just be re-installing that all over again. I’m not even going to be setting the 8/8.1 install up under any personally identifiable naming because that’s just not worth it for only 3 more years and all my personal information will be kept off of my laptops anyways on USB external backup drives or flash drives/SD cards. I’m going to anonymize  my laptops that run Windows 8.1 Pro and that will be running Linux so no worries about skipping any Windows 7/8/8.1 Security Only updates that have telemetry foisted inside.

            I plan to skip any of the 8/8.1 Security Only Updates that contain telemetry so that’s Windows 8/8.1 group B for 3 more years until 2023.

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

    Reply To: No fireworks, closing out 2019 updating

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