Meltdown and Spectre patches have been rereleased and they don’t crash AMD machines any more!
During january’s Patch Tuesday, Microsoft released patches for both Meltdown and Spectre. They worked, too. Well, for Intel processors, anyway. AMD processors didn’t have as great an experience. Some AMD based computers ended up getting bricked. Once the reports of this reached Microsoft, they pulled the patches, cand cancelled Patch Tuesday.
On 2018-01-17, Microsoft rereleased AMD based patches for Windows 10. What makes this a bit confusing for many is that depending on the version of Windows 10 you’re running, you obviously end up with a different build for that version of Windows 10. Microsoft released build 14393.2034 for the Anniversary Update and build 15063.877 for the Creators update. Microsoft also released build 16299.194 for the Fall Creators Update. This last build contained a fix for AMD devices.
There are a few issues that you need to be aware of in all of these builds. Thankfully, Neowin kindly pulled the following information together for everyone.
| Symptom | Workaround |
| Windows Update History reports that KB4054517 failed to install because of Error 0x80070643. | Even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. To verify the installation, select Check for Updates to confirm that there are no additional updates available.
You can also type About your PC in the Search box on your taskbar to confirm that your device is using the expected OS build. Microsoft is working on a resolution and will provide an update in an upcoming release. |
| When calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions.
When calling CoInitializeSecurity, the call may fail when passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error returned on failure is STATUS_BAD_IMPERSONATION_LEVEL. |
Change the authentication level parameter to RPC_C_AUTHN_LEVEL_CALL.
Microsoft is working on a resolution and will provide an update in an upcoming release. |
| Due to compatibility issues with some versions of antivirus software, this update causes stop errors or abrupt reboots. | Contact your antivirus (AV) vendor and follow their guidance. |
Microsoft further released additional patches for Windows 10 Version 1511, Build 10586.1358. This update further has AMD based fixes in it. There are also known issues with it, and again, thanks to Neowin, we have the following details
| Symptom | Workaround |
| When calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions.
When calling CoInitializeSecurity, the call may fail when passing RPC_C_AUTHN_LEVEL_NONE as the authentication level. The error returned on failure is STATUS_BAD_IMPERSONATION_LEVEL. |
Change the authentication level parameter to RPC_C_AUTHN_LEVEL_CALL.
Microsoft is working on a resolution and will provide an update in an upcoming release. |
| Due to an issue with some versions of antivirus software, this fix only applies to the machines where the antivirus ISV has updated the ALLOW REGKEY. | Contact your antivirus AV to confirm that
their software is compatible and have set the following REGKEY on the machine Key=”HKEY_LOCAL_MACHINE” Subkey=”SOFTWARE\Microsoft\ Windows\CurrentVersion\QualityCompat” Value Name=”cadca5fe-87d3-4b96-b7fb-a231484277cc” Type=”REG_DWORD” Data=”0x00000000” |
The post Microsoft Releases Additional Patches appeared first on Soft32 Blog.
Meltdown and Spectre patches have been rereleased and they don’t crash AMD machines any more! During january’s Patch Tuesday, Microsoft released patches for both Meltdown and Spectre. They worked, too. Well, for Intel processors, anyway. AMD processors didn’t have as great an experience. Some AMD based computers ended up getting bricked. Once the reports […]
The post Microsoft Releases Additional Patches appeared first on Soft32 Blog.
2018-03-08T12:36:09.000Z[Collection]https://www.soft32.com/blog/platforms/windows/microsoft-releases-additional-patches/#respond
No comments: