Patch Lady – That SMB issue isn’t SMB

Topic

New Reply

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/Prudent patcher

8 users thanked author for this post.

cesmart4125, SueW, abbodi86, PhotM, AJNorth, woody, Elly, JSTechGeek

Reply | Quote

Replies

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

Reply | Quote

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

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

NetDef

Reply | Quote

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.

Reply | Quote

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.

Non-techy Win 10 Pro and Linux Mint experimenter

Reply | Quote

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.

http://www.catalog.update.microsoft.com/Search.aspx?q=KB4487345

~ Group "Weekend" ~

Reply | Quote

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

Windows 10 Home 64-bit

Reply | Quote

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)

Reply | Quote

“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.

Sonic

Reply | Quote

note to Susan (Patch Lady):

this was recently posted on Born’s web site:
https://borncity.com/win/2019/01/19/does-the-fix-kb4487345-fail-on-windows-server-2008-r2/

Reply | Quote

Susan,

Please tell me what SMB and NTLM are.  Thanks.

Reply | Quote

Acronyms and abbreviations often take on lives of their own and become their own definitions. It can be difficult to remember what radar or laser originally stood for in full words.

Server Message Block is quick, but Windows New Technology Local Area Network Manager has nested acronyms within it. (Windows NT LAN manager)

Reply | Quote

Many thanks, anonymous for your help.

 

Reply | Quote

“An authentication error has occurred
The local security authority cannot be contacted”

After fixing this back in January with KB4487345, I noticed this behavior returned after the following updates installed on February 20th:

“2019-02 Security and Quality Rollup for .NET Framework (KB4487078)” and
“2019-02 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4486563)”

I uninstalled KB4487345 and restarted.  I am not getting the error anymore.
Is anyone else experiencing this behavior?

 

Reply | Quote