New
#1
Any anomalies with this one, folks?
I'm waiting until Friday or Saturday.
June 12, 2018 - KB4284867 (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 support to control use of Indirect Branch Prediction Barrier (IBPB) on some AMD processors (CPUs) for mitigating CVE-2017-5715, Spectre Variant 2 when switching from user context to kernel context. (See AMD Architecture Guidelines for Indirect Branch Control and AMD Security Updates for more details). 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 use of IBPB on some AMD processors (CPUs) for mitigating Spectre Variant 2 when switching from user context to kernel context.
- Provides protections from an additional subclass of speculative execution side channel vulnerability known as Speculative Store Bypass (CVE-2018-3639). 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 this guidance document to enable mitigations for Speculative Store Bypass (CVE-2018-3639) in addition to the mitigations that have already been released for Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754).
- Security updates to Windows apps, Windows Server, Windows storage and filesystems, Windows wireless networking, and Windows virtualization and kernel.
For more information about the resolved security vulnerabilities, see the Security Update Guide.
Known issues in this update
Symptom
A stop error occurs on computers that don't support Streaming Single Instructions Multiple Data (SIMD) Extensions 2 (SSE2).
Workaround
Microsoft is working on a resolution and will provide an update in an upcoming release.
Symptom
There is an issue with Windows and third-party software that is related to a missing file (oem<number>.inf). Because of this issue, after you apply this update, the network interface controller will stop working.
Workaround
- To locate the network device, launch devmgmt.msc; it may appear under Other Devices.
- To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
a. Alternatively, install the drivers for the network device by right-clicking the device and selecting Update. Then select Search automatically for updated driver software or Browse my computer for driver software.
How to get this update
This update is now available for installation through WSUS. To get the standalone 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 4284867.
Source: https://support.microsoft.com/en-us/help/4284867
Direct download links for KB4284867 MSU file from Microsoft Update Catalog:
Download KB4284867 MSU for Windows 7 32-bit (x86) - 15.3 MB
Download KB4284867 MSU for Windows 7 64-bit (x64) - 26.3 MB
Any anomalies with this one, folks?
I'm waiting until Friday or Saturday.
After last month's fiasco with my wireless card, I restored from a system image and skipped the May security-only update.
Normally I wait a week before installing, but wanted to see if this month's update had fixed the issue.
Made a System image with Macrium.
Installed the IE11 cumulative update first - no reboot.
Installed last month's security update (KB4103712) - no reboot.
Immediately installed this month's, then I rebooted.
So far, I haven't had any issues with wireless card or NIC uninstalling on my other systems, so this update seems to have fixed last month's issue for me. Not sure if it'll work for anyone else with NIC issues though.
Interesting from THIS LINK:
But at the Download site the update was still from June 9?Last Updated: Jun 15, 2018
So they changed the documentation but not the actual Update.
Also, I did not get this update. Does this mean that there was an issue with it so was not pushed out to some people until they made a change?
These are the only two I got just today:
2018-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4284826)
Windows Malicious Software Removal Tool x64 - June 2018 (KB890830)
You don't get the Security-only updates through Windows update, they're manual install only.
You don't need them anyway if you install the rollups, as the security updates are already included in the rollups.
Some users, including myself, don't install the rollups, they just want the Security updates.
Yes, they updated the issues section to remove the references to NIC issues.
You mean the Security-only updates? Nobody gets offered those through Windows update anymore, since MS changed the update servicing model for 7/8.1 in late 2016. Only Security updates that were issued before the change are offered through Windows update.
If you're getting the rollups through Windows update then you don't need to worry about the Security-only updates.
I was talking about these, the normal Rollup and MSRT. They came out on the 9th and just getting them today. My computer is on all day every day usually till late at night. What could be the reason, or is this somewhat normal?These are the only two I got just today:
2018-06 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4284826)
Windows Malicious Software Removal Tool x64 - June 2018 (KB890830)
Not sure why it says the 9th, I got the Rollup offered to me on the 12th (usual patch Tuesday), before I hid it. Maybe MS releases them on the Update Catalog site a couple days before they're pushed through Windows update.
I wouldn't be concerned about them being offered a
day or two late, it's happened to me before. I have noticed Windows has been a little slower for me this week whilst checking for updates, so perhaps some server issues on MS side. Not 100% sure though.