Microsoft acknowledges new Windows 11 & Windows 10 issues after recent updates - Fix Bdsthanhhoavn

Microsoft acknowledges new Windows 11 & Windows 10 issues after recent updates

Microsoft has acknowledged new Windows 11 and Windows 10 issues after installation of the recent updates. In case of Windows 11, update installation failures and BitLocker recovery issues are plaguing the user experience. In case of Windows 10, it is Audio not working issue apart from update installation failures.

Coming to Windows 11, the Bitlocker and update installation failure issues have arisen after installation of update KB5012170. Check all the details provided by Microsoft about the issues below. Microsoft is working to provide resolution for these issues.

Windows 11 issues:

Some devices might start up into BitLocker Recovery

 

Status Originating update History
Confirmed OS Build 22000.850
KB5012170
2022-08-09
Last updated: 2022-08-19, 19:36 PT
Opened: 2022-08-19, 19:36 PT

Some devices might enter BitLocker Recovery on the first or second restart after attempting to install Security update for Secure Boot DBX ( KB5012170), released August 9, 2022. Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

Workaround: If your device is prompting for a BitLocker Recovery key, you will need to supply it to start up Windows. For more information, see Finding your BitLocker recovery key in Windows.

If you have not installed KB5012170 yet and have BitLocker enabled on your device, follow the instructions below to temporarily suspend BitLocker before installing.

If you have installed KB5012170 and have not yet restarted your device or have only restarted your device once, temporarily suspend BitLocker using the instructions below.

Important: If you have restarted your device two times or more after installing KB5012170, your device is not affected by this issue

To temporarily suspend BitLocker, or to avoid a BitLocker recovery when deploying KB5012170, follow these steps:

1. Run the following command from Administrator command prompt:

Manage-bde -protectors -disable %systemdrive% -rebootcount 2

2. Install the update KB5012170, if not already installed

3. Restart the device.

4. Restart the device again.

5. BitLocker should automatically be enabled after two boots. If you want to manually resume BitLocker to verify that it is enabled, use the following command:

Manage-bde -protectors -Enable %systemdrive%

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Affected platforms:

  • ​Client: Windows 11, version 21H2
  • ​Server: None

Update might fail to install and you might receive a 0x800f0922 error

 

Status Originating update History
Investigating OS Build 22000.850
KB5012170
2022-08-09
Last updated: 2022-08-12, 17:52 PT
Opened: 2022-08-12, 17:08 PT

When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.

Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

Next steps: We are presently investigating and will provide an update in an upcoming release.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

Windows 10 issues:

The audio issue faced by Windows 10 PCs is seen after installing KB5015878 or later updates. Update installation failure issues have arisen after installation of update KB5012170. Check all the details provided by Microsoft about the issues below. Microsoft is working to provide resolution for these issues.

Audio might stop working

 

Status Originating update History
Resolved OS Build 19044.1865
KB5015878
2022-07-26
Resolved: 2022-08-19, 19:36 PT
Opened: 2022-08-19, 19:36 PT

After installing KB5015878 or later updates, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the “audio enhancements” setting disabled before installing KB5015878 or the sound device driver has issues with the “audio enhancements” feature.

Workaround: This issue can be mitigated differently depending on your symptoms and if you have installed the update already.

If you have not yet installed the update, you can do the following to prevent the issue:

  • ​Updating your audio device driver (also called “sound drivers” or “sound card drivers”) might prevent this issue. If there are updated drivers available on Windows Update or from your Windows device manufacturer’s (OEM) webpage, installing them might prevent this issue.
  • ​If you are using any advanced audio applications such as Open Broadcaster Software (OBS), it is recommended that you backup all your settings before installing the update.

If only certain apps are impacted, you can try the following to mitigate the issue:

  • ​Verify that the audio devices set within those apps are the expected devices. Audio endpoints might be reinitialized after KB5015878 is installed and some apps might set the audio devices for microphone and speakers to default.
  • ​If the device settings within the app are as expected, the apps might be caching the Windows Multimedia Device (MMDevice) ID. Caching the MMDevice ID is not recommended and might require reinstallation of the affected app or contacting support for the developer of the app for how to resolve the issue when audio endpoints are reinitialized and have new MMDevice IDs.

If you have already installed the update and are experiencing issues with audio on all apps, you can try the following to mitigate the issue:

  1. ​The Windows audio or sound troubleshooter might be able to resolve the issue for you. You can launch the troubleshooter from Fix sound or audio problems in Windows by selecting the Open Get Help button in the article. The Get Help dialog window should open, and you will need to select yes to open the troubleshooter.
  2. ​If your device’s audio is still not working as expected, follow the instructions in Disable Audio Enhancements. Note: The article uses the microphone as an example, but you will need to do the steps for any affected audio device.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Note: This KIR will prevent the issue on Windows devices which have not installed KB5015878 but will have no effect on devices already affected by this known issue. Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

Group Policy downloads with Group Policy name:

Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

Affected platforms:

  • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • ​Server: None

Update might fail to install and you might receive a 0x800f0922 error

 

Status Originating update History
Investigating OS Build 19044.1880
KB5012170
2022-08-09
Last updated: 2022-08-12, 17:52 PT
Opened: 2022-08-12, 17:08 PT

When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.

Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

Next steps: We are presently investigating and will provide an update in an upcoming release.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

Tags: #Microsoft #acknowledges #Windows #Windows #issues #updates

Leave a Comment