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
  • Patch Lady – That SMB issue isn’t SMB

    Posted on Susan Bradley Comment on the AskWoody Lounge

    Home Forums AskWoody blog Patch Lady – That SMB issue isn’t SMB

    This topic contains 8 replies, has 9 voices, and was last updated by

     SonicMojo 3 days, 2 hours ago.

    • Author
    • #309101 Reply

      Susan Bradley

      As a follow up to Woody’s earlier post on the issue of  KB4480970 (Monthly Rollup) and KB4480960 (Security only) causing issues with networking and di
      [See the full post at: Patch Lady – That SMB issue isn’t SMB]

      Susan Bradley Patch Lady

      7 users thanked author for this post.
    • #309126 Reply

      AskWoody Lounger

      Just like no one should be running Windows XP at this point. Yet they are out there. Old phone systems, massage beds, entertainment systems, etc.

      Group A | Windows 7 Pro 64-bit | Windows 10 Pro 1809 64-bit
    • #309344 Reply


      @susan, thx for your post. Some additional thoughts are here: Fix for the Windows 7 SMB network bug caused by Update KB4480970/KB4480960

      1 user thanked author for this post.
    • #309379 Reply


      Is KB4487345 a security only quality update? The windows update catalog does not indicate that it’s a security only quality update! I’m only security only so what are my options? It could be that it’s just a stright up fix but I always look for the words “security only quality update: before I’ll trust it.

      I’m also concerned about any windows end of life nagware that my slip in a similar manner to XP’s nagware when it was getting close to its EOL.

      • #309387 Reply


        Per Microsoft:

        This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates.

        It is a fix for security updates, whether the Security Only, or the security part of the Monthly Quality and Security update. It is not yet (if it will be) included in a Security Only update. It will most probably be included in the next Monthly Quality and Security update. It isn’t a rollup or cummulative update that includes telemetry (if that is what you are worried about).

        It is one of the problems discovered, and then fixed, after the January patches were issued. It is a good example why most of us follow the DEFCON system and wait for these problems to be discovered by others. Woody will provide instructions as to how to navigate through this, when the DEFCON level changes.

        As far as I know, no one is reporting any ‘end of life’ nagware for Windows 7, yet. One of the problems that Microsoft faces, is that it has lost the trust of many customers… a sad state of affairs, even if they don’t acknowledge it.

        Win 7 Home, 64 bit, Group B

    • #309393 Reply

      AskWoody Plus

      This has hit several of my small clients (home and very small office) with their network scanners.

      Installing the hotfix seems to have cleared the problem.

      ~ Group "Weekend" ~

    • #309461 Reply

      AskWoody Lounger

      Does the new patch KB4487345 replace KB 4480960? I notice both are around the same size. (I haven’t installed KB 4480960 yet.)

      W7HP SP 1 64-bit laptop, T4400, 3 GB RAM, Patch Group B

      • #309462 Reply

        AskWoody Plus

        Using the helpful link @netdef provided above to check the Package Details, the supercedence shows as:

        This update replaces the following updates:
        Update for Windows 7 for x64-based Systems (KB3121255)
        Update for Windows 7 for x64-based Systems (KB3156417)

    • #309566 Reply

      AskWoody Lounger

      “I’m looking at you 1809 for the number of consultants I see complaining about excessive CPU, the need to constantly install updated drivers, and interactions with printers that worked fine with prior feature releases)”

      I spent the better part of a week troubleshooting why my perfectly good HP LaserJet 1505n printer fully supported on my 1709 machines – only to discover that ALL prior HP drivers that shipped with the OS have been stripped out and “moved” to Windows Update. Which of course is completely useless if using WSUS – and even more useless after I tested Windows Update and my 1505n driver is nowhere to be found on WU.

      Luckily I managed to figure out where the missing driver was being installed from in 1709 (Driverstore/FileRespository) and made a backup of that folder and was able to get my new 1809 machines working correctly.

      I almost gave up on this printer to buy a new one if not for this week of troubleshooting. It just shows me how little thought Microsoft gives to Windows 10 and how it could care less about the hoops users have to go through to actually use their perfectly fine existing hardware.


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

    Reply To: Patch Lady – That SMB issue isn’t SMB

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

    Your information:

    Comments are closed.