If you’re running Windows 7 Service Pack 1 or Windows Server 2008 RS2 Service Pack 1 and having problems installing the August Windows security updates, SHA-2 support may be missing. Check our dashboard for more information:

Windows 10 message center - Windows Release Information | Microsoft Docs

Tweet

— Twitter API (@user) View on Twitter

UPDATE 8/14:

"Known issues" updated. See first post for more details.

There's inside the Tuesday Patch August 13, 2019 - KB4512506 (Monthly Rollup) a CVE ID: CVE-2019-9506 that needs the end-user having to set-up a manual modification in Regedit about to protect against "Key Negotiation of Bluetooth" (KNOB) attack.

Dword value "EnableMinimumEncryptionKeySize" (without quote) have to be set to 1 in the path:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies\Hardware\Bluetooth.


On my machine, I can see Bluetooth related .dll & .exe files have been updated to number 6.1.7601.24511 in System32.
My key stop at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies....

Can't find exact MS article id where the registry key has to be set or not to 1, only a source that mention that key without link. Any clue? Thanks

NoN said:

There's a Inside the Tuesday Patch August 13, 2019 - KB4512506 (Monthly Rollup) a CVE ID: CVE-2019-9506 that needs the end-user having to set-up a manual modification in Regedit about to protect against "Key Negotiation of Bluetooth" (KNOB) attack.

Dword value "EnableMinimumEncryptionKeySize" (without quote) have to be set to 1 in the path:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies\Hardware\Bluetooth.


On my machine, I can see Bluetooth related .dll & .exe files have been updated to number 6.1.7601.24511 in System32.
My key stop at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies....

Can't find exact MS article id where the registry key has to be set or not to 1, only a source that mention that key without link. Any clue? Thanks

This one?

https://support.microsoft.com/en-us/...th-enforcement

Thanks!

Please note we are shipping this mitigation off by default because during testing of encryption key length enforcement, we found that some Bluetooth controllers may not respond or stop pairing. Some BT devices may not support the minimum encryption key length enforced by the Microsoft update. We understand that compatibility with your devices is important and as we cannot guarantee compatibility with key enforcement enabled. You can enable the mitigation based on your own risk assessment and compatibility needs. If you have access to sensitive data and use the device in an area that does not have physical security, we recommend enabling the mitigation for this security vulnerability.

That's all i wanted to know about...

I've tried installing this update this morning but it is failed with error code 80092004.

From the little I've read on the net, this has come about for those that installed"June’s Preview of Monthly QualityRollup for Windows 7 for x64-basedSystems (KB4503277)” which fixed an error caused by a previous update.

I can’t find any clear guidance from MS on what to do. Should I uninstall KB4503277 and try again to install KB4512506 OR just leave it until MS presumably fix this update. I don’t want to muck up my computer which to date has installed all updates just fine.

Due to work, I’ve got limited time (not to mention patience) to spend on this. Any ideas would be welcome.

svnfrms2r said:

The article does not say if the DWORD should be 32 or 64 bit.
Had to create the the whole thing from incl Policies... is that a sign that something is wrong, and if so, what?


Thank you!
:)

Usually it will be for "DWORD (32-bit) Value".