Today, Microsoft released updates for all supported versions of Windows, as it does every second Tuesday of the month. It updated all four versions of Windows 10, but it also released patches for Windows 7 and 8.1.
If you're still on Windows 7 or Server 2008 R2 SP1, the monthly rollup is KB4025341, and you can get it from the Microsoft Update Catalog here. Here's what got fixed:
Addressed issue called out in KB4022168 where Internet Explorer 11 may close unexpectedly when you visit some websites.
Security updates to Microsoft Graphics Component, Windows Search, Windows Virtualization, Windows Storage and File Systems, Datacenter Networking, Windows Server, Windows kernel, Microsoft PowerShell, Windows shell, Internet Explorer 11, Microsoft NTFS, Windows kernel-mode drivers, and ASP.NET.
There's an important note, which also applies to the rest of the updates that were offered.
- After installing the security updates for CVE-2017-8563, administrators need to set registry key LdapEnforceChannelBinding to enable the fix for the CVE. For more information about setting the registry key, see Microsoft Knowledge Base article 4034879.
There's also a security-only update, KB4025337, which must be manually downloaded here, just in case you don't want the full monthly rollup. Obviously, the changelog is similar to the security section of KB4025341.
Windows 8.1 and Server 2012 R2 get KB4025336 today, and as with the others, it can be obtained via the Microsoft Update Catalog. Here's what got fixed:
Addressed issue called out in KB4022720 where Internet Explorer 11 may close unexpectedly when you visit some websites.
Addressed issue that causes .jpx and .jbig2 images to stop rendering in PDF files.
Security updates to Windows kernel, ASP.NET, Internet Explorer 11, Windows Search, Windows Storage and Files Systems, Datacenter Networking, Windows Virtualization, Windows Server, Windows shell, Microsoft NTFS, Microsoft PowerShell, Windows kernel-mode drivers, and Microsoft Graphics Component.
Unlike with the Windows 7 updates, there is a known issue to be aware of:
| Symptom | Workaround |
|---|---|
| If an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected. | Microsoft is working on a resolution and will provide an update in an upcoming release. |
The security-only update for Windows 8.1, KB4025333, can be downloaded here.
3 Comments - Add comment