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
  • Buggy KB 4039884 Win7 patch of a patch, returns with no explanation

    Home Forums AskWoody blog Buggy KB 4039884 Win7 patch of a patch, returns with no explanation

    Viewing 7 reply threads
    • Author
      Posts
      • #131308 Reply
        woody
        Da Boss

        It’s baaaaack. The buggy patch of a buggy patch, KB 4039884, which was pulled yesterday, suddenly re-appeared today, with a different date and a new t
        [See the full post at: Buggy KB 4039884 Win7 patch of a patch, returns with no explanation]

        6 users thanked author for this post.
      • #131335 Reply
        abbodi86
        AskWoody_MVP

        It’s now a separate update from the Monthly Rollup series
        so it will not affect or supersede the current installed rollup (KB4034664 or KB4034670), or cause old components to become active

        5 users thanked author for this post.
      • #131353 Reply
        MrBrian
        AskWoody_MVP

        From https://support.microsoft.com/en-us/help/4039884/windows-7-update-kb4039884: “Before you install this update, you must uninstall any previous version of KB4039884. Then install KB4034664 or KB4034679 before installing this current update of KB4039884.”

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

          If we have uninstalled KB 4039884, when the time comes to safely install the newer version of KB 4039884, is there any reason to uninstall and re-install KB4034679 before doing so?

          • #131396 Reply
            Kirsty
            Da Boss

            After reading @MrBrian‘s MS link, I see that KB4034679 needs to be installed before KB4039884 is reinstalled.
            I didn’t read anything to say KB4034679 needed to be reinstalled though.

            • #131457 Reply
              anonymous
              Guest

              Thanks

        • #131602 Reply
          Noel Carboni
          AskWoody_MVP

          Before you install this update, you must uninstall any previous version of KB4039884. Then install KB4034664 or KB4034679 before installing this current update of KB4039884.

          I agree with Woody’s assessment that this is anything but customer-friendly.

          Could anyone who had already patched Windows 7 and isn’t a career software engineer reasonably be expected to get that right?

          My hat’s off to those who are trying to follow those instructions, especially in light of the fact that when you install KBaaaaaaa you don’t generally see it listed in a WMI QFE LIST output, but rather KBbbbbbbb and KBccccccc instead.

          -Noel

          1 user thanked author for this post.
      • #131432 Reply
        ScaryJohnson
        AskWoody Lounger

        I synched SUS but i don’t see this available.  Is this in SUS or does it not detect and this needs to be manually installed?  Already installed the 2017-08 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4034664) on a few machines and want to make sure they get this update.

        We’re using SCCM CB.

        Thanks

      • #131459 Reply
        anonymous
        Guest

        I haven’t updated my machine now since June 17 (kb 4022722) because MS seemto have started a trend in breaking things that were not broken , My pc is skylake based  so shouldn’t fall foul to the issue in July’s security  patch , but  it continues in august’s patch  with other bug’s If MS can’t be bothered to fix these issues why should we be bothered to keep upto date with patches,  as if you have common sense a good AV and firewall solution  then  the need for patches is negated IMO

      • #131464 Reply
        EP
        AskWoody_MVP

        From MS Update Catalog, the re-released KB4039884 patch names for Win7 are windows6.1-kb4039884-v2-x86_02559e35643b19ab38e8533e7286be13b2f7b37e.msu (for x86 or 32bit systems) and windows6.1-kb4039884-v2-x64_9a38a042759ee7f4b2b3d235822a13414421542c.msu (for x64 or 64bit systems). definitely “V2” versions of KB4039884.

        1 user thanked author for this post.
      • #131847 Reply
        MrBrian
        AskWoody_MVP

        Updated versions of file win32k.sys, the latest version of which apparently fixes this issue, are included often in both the monthly rollups and security-only updates, so even if you don’t install KB4039884, you’ll probably get the fix anyway in the September 12 updates.

        1 user thanked author for this post.
        • #133281 Reply
          MrBrian
          AskWoody_MVP

          This issue is not listed anymore in the knowledge base article for the Windows 7 Sept. 2017 monthly rollup or security-only update.

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

        If you get this in win10, check your display adapter… It may have a new update than needs to be rolled back. In my case, it was Advanced Micro Devices that had a new driver date of 7/2017.. Rolling this back to the old one (ie 2015) fixed the problem

    Viewing 7 reply threads

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

    Reply To: Buggy KB 4039884 Win7 patch of a patch, returns with no explanation

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