January 8, 2019 - KB4480960 (Security-only update) Windows 7

[Brink]

January 8, 2019 - KB4480960 (Security-only update)

Applies to: Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1

---

Improvements and fixes

This security update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Provides protections against an additional subclass of speculative execution side-channel vulnerability known as Speculative Store Bypass(CVE-2018-3639) for AMD-based computers. These protections aren't enabled by default. For Windows client (IT pro) guidance, follow the instructions in KB4073119. For Windows Server guidance, follow the instructions in KB4072698. Use these guidance documents to enable mitigations for Speculative Store Bypass (CVE-2018-3639). Additionally, use the mitigations that have already been released for Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754).
• [UPDATED 1/11] Addresses an issue that affects PowerShell remoting loop back using non-administrator accounts. For more details, see Windows Security change affecting PowerShell.
• Security updates to Windows Kernel, Windows Storage and Filesystems, Windows Wireless Networking, and the Microsoft JET Database Engine.

For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.

Known issues in this update



How to get this update

Before installing this update

Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest Rollup. SSUs improve the reliability of the update process to mitigate potential issues while installing the Rollup and applying Microsoft security fixes.

If you are using Windows Update, the latest SSU (KB3177467) will be offered to you automatically. To get the stand-alone package for the latest SSU, go to the Microsoft Update Catalog.

Install this update

This update is now available for installation through WSUS.

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

File information

For a list of the files that are provided in this update, download the file information for update 4480960.

Source: Access Denied

See also:

• KB4487266
• KB4487345

Direct download links for KB4480960 MSU file from Microsoft Update Catalog:

:ar: Download KB4480960 MSU for Windows 7 32-bit (x86) - 18.9 MB

:ar: Download KB4480960 MSU for Windows 7 64-bit (x64) - 28.2 MB

 

[Brds7t7]

Thanks Shawn, and belated Happy New Year!

 

[Brink]

Thank you Lee. I hope you are having a Happy New Year as well.

 

[erpster4]

uh-oh Brink.


Installing the KB4480960 security-only update causes problems with network shares using SMBv2:


Patch Tuesday updates for Win7, KB 4480970 and KB 4480960 knock out networking | Computerworld


Network issues with updates KB4480970 and KB4480960 | Born's Tech and Windows World


Windows 7 and Server 2008 R2 updates KB4480970 and KB4480960 causing network issues - gHacks Tech News

 

[Brds7t7]

Didn't take long for Microsoft's first bork of the year!
This is why I wait at least a week before installing their updates now. Already had an update a few months ago completely knock out my network card. And their supposed "fix" did nothing of the sort!

Installing MS updates day one is just asking for trouble these days. Thank god Macrium exists.

 

[lehnerus2000]

Installing MS updates day one is just asking for trouble these days. Thank god Macrium exists.

Installing W7 updates has been like playing Russian Roulette with 5 bullets in a 6 shot revolver (for the last year).
I haven't installed any since December 2017.

I also read that since October 2018 MS has slipped in "improved Telemetry" code (which I can't confirm or refute).

Thank god Macrium exists.

Agreed.

 

[Brink]

New known issues added to first post.

 

[BlueGuy]

Installing W7 updates has been like playing Russian Roulette with 5 bullets in a 6 shot revolver (for the last year)

Well, none of my January 9 stuff recorded on this machine and I blame the updates* because for the first time, the AVG intercepted CWhelper.exe and stopped it from doing its job and I've missed season 5 episodes 8-12 of Babylon 5 [quite pertinent, given the similarities between Trump and President Clarke] because for some reason all this crap made the HDHomerun tuners undetectable [which I fixed manually] .
I was busy watching Corrie, then Nature and NOVA in the other room, so I didn't catch the error.
I'm pissed, I knew a cock-up would occur when COMET moved everything from once an evening to mini-marathons, now instead of missing just one ep., I'm missing a bunch from a story arc, I'm really pissed.
Hope I can find S05-E8-12 in the 'scene or maybe break down and get the DVD, if its still affordable...remember, I'm a geek, but a poor one. I use the Cliff Watson EPG Project software for the HDHR4 tuners.

*Because the system had to be rebooted, damn it!

 

[Brink]

Microsoft's killer Windows 7 patch: Breaks networking, bricks legit 'Not genuine' PCs | ZDNet

 

[BlueGuy]

I didn't get the 'Not Genuine" bug, it just disrupted/disconnected the HDHR because it is a network attached unit, as a result the tuners weren't active when the Cliff Watson EPG went to record here for Wednesday. Then for the first time I had to make/give CW_EPG.exe and CwHelper.exe an exception within AVG. So you could say that even the security only patch disrupted network operations, even though I still had connections to the outside world. Even SchedulesDirect.com.

I found alternative sources, and though SD @ 704x404 or 480p still looks better than the off-air .ts results from the local COMET sub-channel.

 

[michael diemer]

Wife's laptop got the "not genuine windows" message, and it has been crashing frequently since the update. I'm about to put Linux on it to free her of this continuing windows update madness.

 

[Brds7t7]

I haven't installed any since December 2017.

Can't say I blame you really. I do prefer to keep mine patched with the latest security patches, but that's just my personal preference. I can see why people choose to avoid MS updates lately.

I also read that since October 2018 MS has slipped in "improved Telemetry" code (which I can't confirm or refute).

I haven't noticed anything "extra" being slipped into the Security-only updates though. The telemetry style updates (Diagnostics tracking service, etc) were slipped into the rollups very early on after the servicing model change, late 2016 or early 2017 I believe. I don't install the rollups though, except occasionally in VMs to test something out (usually a rollup installation bork).
My PCs still have the default (out-of-the-box) services listed.

Microsoft's killer Windows 7 patch: Breaks networking, bricks legit 'Not genuine' PCs | ZDNet

Looks like it's another one on my skip list for now.
Apparently the "Not Genuine" issue isn't caused by the latest Security updates though, it's something MS changed server side. MS has said the solution is to remove the update KB971033 on systems with Volume licencing.

Access Denied

 

[Brink]

Release notes for KB4480960 in first post updated.

 

[Brink]

Activation failures and "not genuine" notifications around January 8, 2019, on volume-licensed Windows 7 KMS clients

 

[Brink]

New known issues added to first post.

 

[saty]

They did "fix" it...

Access Denied

KB4487345

Microsoft Update Catalog

I did not try installing this update, as i did uninstall KB4480960 recently.

 

[Brink]

Here's Microsoft's fix for legit Windows 7 PCs labelled 'not genuine' after latest update mishap - TechRepublic

 

[Brds7t7]

That update has always been on my skip list, even on my PCs which don't have volume licencing.
Didn't think "Updated Activation Technologies" was something I really needed anyway, as I've only had genuine windows installs. That update seems more like it's aimed to catch "dodgy" installs.

 

[Efdy]

That update has always been on my skip list, even on my PCs which don't have volume licencing.
Didn't think "Updated Activation Technologies" was something I really needed anyway, as I've only had genuine windows installs. That update seems more like it's aimed to catch "dodgy" installs.

Hello, you guys.

Thank you for the information. I didn't install January updates yet because of reading here about it. So far since I did the repair install after the problems my computer had with Windows Updates a year ago, I have just been installing the stuff that shows up in Windows Updates, which there has not caused any problems I am aware of since the repair install. (It's not set to automatically install anything, but I just install the stuff shows up in Windows Updates, usually Malicious Software Removal Tool, Security Monthly Quality Rollup for Windows 7, and Security and Quality Rollup for .NET Framework, which are the updates in Windows Updates at the moment.) I was considering just installing Security Updates from now on like Brds7t7 does, but I can't even understand something that simple really, like what to make sure I also do in that case such as installing that servicing stack update thing. Is installing that servicing stack update thing something you have to do each month before installing Windows Updates if you only install Security Updates for Windows 7 instead of the Security Monthly Quality Rollup package?

My computer says I have KB971033 installed. I don't even know anything about volume licensing, but I will look for what it is and how to check if I have it. Should I uninstall KB971033? Does KB971033 not need to be installed in either case, whether I have volume licensing or not?

Thank you for reading this.

 

[Struggling7]

.......My computer says I have KB971033 installed. I don't even know anything about volume licensing, but I will look for what it is and how to check if I have it. Should I uninstall KB971033? Does KB971033 not need to be installed in either case, whether I have volume licensing or not?

Thank you for reading this.

I don’t have knowledge to answer your questions, but will pass-along experiment on one machine that is very similar to yours.

My Win 7 professional 64-bit SP1 unit also had KB971033 installed, after an image backup, I did January updates with no problem afterwards. See this link:
January 2019 patch Tuesday updates installed successfully


After seeing this quote from link that Brink posted above (post #17):

The Microsoft advisory note states "we strongly recommend that you uninstall KB 971033 from all volume-licensed Windows 7-based devices", whether or not these devices were affected by these latest problems

Yesterday I uninstalled KB971033 with no problems to this point. However, not long after uninstalling it I got new update available message and it was KB971033 I had uninstalled earlier. So I just hide it for time being waiting to see if I should reinstall knowing it did not cause a problem in first place.