• KB 4023057 is back again. Again.

    Home » Forums » Newsletter and Homepage topics » KB 4023057 is back again. Again.

    • This topic has 24 replies, 18 voices, and was last updated 6 years ago.
    Author
    Topic
    #166218

    While sifting through the latest KB article change list, I noticed that our old friend KB 4023057 is back. Now titled Update to Windows 10 Versions 15
    [See the full post at: KB 4023057 is back again. Again.]

    3 users thanked author for this post.
    Viewing 21 reply threads
    Author
    Replies
    • #166237

      Woody,
      Well, our other old “FRIEND” KB2952664 has shown its’ ugly face to me this morning. Again, it got hidden. Maybe I’m just an old stick in the mud, but personally I want NOTHING to do with Wwin10, or it’s problems. MS just doesn’t get it. WE DON’T WANT IT ! ! !

      Sorry for the rant. When this machine gives up the ghost, the net one WILL be Linux.

      Dave

      2 users thanked author for this post.
    • #166238

      I have CEIP turned of on all my Win7/8.1 machines and KB2952664 and KB2976978 have appeared as unchecked optionals. They are not CEIP dependent.

      My prediction: The patches will disappear from the unchecked optional list sometime late Monday or early Tuesday before Patch Tuesday release. They will then reappear as CHECKED important updates with the Patch Tues update release.

      9 users thanked author for this post.
    • #166242

      I have CEIP turned of on all my Win7/8.1 machines and KB2952664 and KB2976978 have appeared as unchecked optionals. They are not CEIP dependent. My prediction: The patches will disappear from the unchecked optional list sometime late Monday or early Tuesday before Patch Tuesday release. They will then reappear as CHECKED important updates with the Patch Tues update release.

      kb2952664 showed up for me also this morning.  I hid it.  Now I have 2 hidden.  One optional (today) and one recommended (from before).

    • #166249

      KB2952664/KB2976978 do not cause problems themselves, but the Compatibility Appraiser schedule task can consume cpu/ram/disk when it appraise the system and programs

      BTW, the update descroption about KB4023057 🙂
      https://www.askwoody.com/forums/topic/another-complaint-about-kb-4023057/page/2/#post-163295

      6 users thanked author for this post.
    • #166253

      KB2952664/KB2976978 … the Compatibility Appraiser schedule task can consume cpu/ram/disk when it appraise the system and programs

      Exactly right. They’re running their software primarily for their benefit, taking up your disk space and computer resources.

      The only potential (tenuous) benefit to you is that they will know your computer’s hardware and software configuration and might consider it in their plans to engineer Windows 10, so that allowing those updates to run might net you a small additional chance that your system will be supported by Windows 10.

      To consider this a benefit at all, it of course is assumed that you actually WANT Windows 10 on your current system.

      I’ve never installed these updates, which have always come up as “optional”, and I’ve never had any problems I can sense as a result.

      By the way, the Microsoft Compatibility Appraiser task doesn’t appear to be the only thing scheduled more for their benefit than yours. It’s never a bad idea to sweep through the (big) list of scheduled tasks and improve your understanding of what your computer is set to do on its own.

      -Noel

      7 users thanked author for this post.
      • #166275

        Yup, found KB2952664 on the WIN 7 boxes; they’re once again hidden (as previously).

        Now for the jugglers & clowns… .

    • #166255

      Installed KB2952664 on two Windows 7/64-bit systems yesterday.

      No brick. No problem. And both computers booted up. Sunshine.

      On permanent hiatus {with backup and coffee}
      offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
      offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
      online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender
    • #166256

      Installed KB2952664 on two Windows 7/64-bit systems yesterday. No brick. No problem. And both computers booted up. Sunshine.

      OMG!!!
      You intentionally installed….
      A snooping telemetry patch?…
      That was in the “optional” list?….
      UNCHECKED?

      11 users thanked author for this post.
    • #166258

      The only potential (tenuous) benefit to you is that they will know your computer’s hardware and software configuration and might consider it in their plans to engineer Windows 10, so that allowing those updates to run might net you a small additional chance that your system will be supported by Windows 10.

      I’d be a lot more amenable to that idea if MS hadn’t chosen to fire their paid beta testers right when they started ramping up on all of this stuff.  A Windows user has an obvious interest in making Windows better, but he also has an interest in not allowing himself to be used as a beta tester so MS can save money on real beta testers.

      Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
      XPG Xenia 15, i7-9750H/32GB & GTX1660ti, KDE Neon
      Acer Swift Go 14, i5-1335U/16GB, KDE Neon (and Win 11)

      3 users thanked author for this post.
    • #166266

      Could the Remediation Shell be a prelude to 1709 going CBB?

    • #166271

      Could the Remediation Shell be a prelude to 1709 going CBB?

      1709 has already been blessed for general use (CBB old designation).

    • #166279

      I hid KB2976978 immediately yesterday.

    • #166295

      Installed KB2952664 on two Windows 7/64-bit systems yesterday. No brick. No problem. And both computers booted up. Sunshine.

      OMG!!!
      You intentionally installed….
      A snooping telemetry patch?…
      That was in the “optional” list?….
      UNCHECKED?

      Well, some like it rough! 😀

    • #166301

      Could the Remediation Shell be a prelude to 1709 going CBB?

      1709 turned CBB, er, “Semi-Annual Channel” last month

      https://www.computerworld.com/article/3247864/microsoft-windows/microsoft-stamps-octobers-windows-10-feature-upgrade-as-enterprise-worthy.html

      https://technet.microsoft.com/en-us/windows/release-info.aspx

      There was a CBB false start back in November

      https://www.askwoody.com/2017/microsoft-confirms-that-win10-1703-users-are-being-upgraded-without-warning-to-1709/

      Personally, I’m waiting for this month’s 1709 cumulative update, to see if it’s any better than the three cumulative updates we saw last month, before upgrading my production machines to 1709.

    • #166317

      OMG!!! You intentionally installed…. A snooping telemetry patch?… That was in the “optional” list?…. UNCHECKED?

      Group A+?

      1 user thanked author for this post.
    • #166385

      You have to wonder what their thought process is with some of these patches. It’s starting to remind me a little of Clippy. “It looks like you still haven’t installed our Windows 10 update telemetry patch. Would you like help with that?”

      1 user thanked author for this post.
    • #166389

      KB 2952664 showed up for me after I installed the IE security only patch yesterday evening; hid it again…

      Win7x64 group B

      Group B HP Pavilion-dv6 Win7x64 Home Premium-Intel Core i5-3210M CPU

      1 user thanked author for this post.
    • #166419

      UPDATE: Günter Born notes that KB 2952664 for Win7 and KB 2976978 for Win8.1 (both unchecked and optional) were also released yesterday. Born’s take on the Win7 and 8.1 versions is different from mine

      These updates have been good for problems in the past and also had to be withdrawn by Microsoft in some cases. There were machines that hung themselves, where the fan was running at full speed, or where websites or the machine was freezing for short periods of time (see here). Herehere and here are older threads mentions install errors with these updates. Here someone mentions boot issues in November 2017. Weighting all this risks against the benefits of a ‘diagnosis update’, I recommend to hide these updates.

      I’ve hidden the KB2952664 update from our W7 Pro 64 machines more times than I can count, but it keeps rising from the grave in subsequent MS update lists.  I always check for such recidivist updates (and hide them if I find them) before pushing the Go button to install updates, but this cat-and-mouse game with KB2952664 is getting tiresome.

      If anyone knows a way to put a stake through the heart of this KB2952664 creature so that it will die and stay dead, I’d appreciate knowing it.

      EDIT html to text (in copied blockquotes at top)

      2 users thanked author for this post.
    • #166427

      I’ve hidden the KB2952664 update from our W7 Pro 64 machines more times than I can count, but it keeps rising from the grave in subsequent MS update lists.

      Every time MS changes KB2952664 (Win7) or KB2976978 (win8.1) it becomes a different patch, albeit with the same name (like having two people with the same name) – they are actually two different entities. The change can be in the actual makeup of the patch or in its change from “optional” to “recommended.” That’s why two with the same KB number can coexist. If you look in hidden updates and find two, you will find that to be the case.

      On patch Tues, if you had left the latest one in the “optional” list unchecked, you will find that is has disappeared from there and reappeared in the “important” list as a checked “recommended.” This keeps happening b/c MS keeps changing the update and reissuing it with the same name.

      1 user thanked author for this post.
    • #166426

      If the ‘free’ update from 7/8.1 to Windows 10 is no longer publicly available, even though it appears to still be supported, why is Microsoft still pushing these updates? Would it be for the 1 in every 10000 people who may buy an in-place upgrade from 7/8.1 to 10, or could there be plans for a further supported free-for-all push to 10 ie the return of GWX?

    • #166429

      If the ‘free’ update from 7/8.1 to Windows 10 is no longer publicly available, even though it appears to still be supported, why is Microsoft still pushing these updates? Would it be for the 1 in every 10000 people who may buy an in-place upgrade from 7/8.1 to 10, or could there be plans for a further supported free-for-all push to 10 ie the return of GWX?

      GWX is dead. MS has said that won’t happen again.

      KB2952664 (Win7) and KB2976978 (win8.1) are for MS’s benefit to collect information on your computer by telemetry.

      1 user thanked author for this post.
    • #166434

      If the ‘free’ update from 7/8.1 to Windows 10 is no longer publicly available, even though it appears to still be supported, why is Microsoft still pushing these updates? Would it be for the 1 in every 10000 people who may buy an in-place upgrade from 7/8.1 to 10, or could there be plans for a further supported free-for-all push to 10 ie the return of GWX?

      GWX is dead. MS has said that won’t happen again. KB2952664 (Win7) and KB2976978 (win8.1) are for MS’s benefit to collect information on your computer by telemetry.

      Microsoft have said a lot of things. I no longer believe a word they say. I retain GWX Control Panel on my machines as it does no harm, is a quick way of checking the WU settings, and may just alert me to any future compromise whether by Microsoft or some other malware distributor.

      3 users thanked author for this post.
    • #167155

      The obnoxious telemetry appraisers KB2952664/KB2976978 are now “Important” updates in Windows 7/8.1

      they never steped up beyond “Recommended” state since the release

      3 users thanked author for this post.
    Viewing 21 reply threads
    Reply To: KB 4023057 is back again. Again.

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

    Your information: