|
There are isolated problems with current patches, but they are well-known and documented on this site. |
Annnndddd here we go again…. It’s Second Tuesday of the Month and Microsoft is releasing their updates: Remember first and foremost to always update
[See the full post at: It’s time for those August updates to be deferred]
Susan Bradley Patch Lady/Prudent patcher
AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on August 9, 2022.
There is a Security-only Update for those with Win7 ESU subscriptions.
There is an August IE11 CU KB5016618 for Win7 ESU subscriptions.
August Rollup KB5016676 Download 32-bit or 64-bit for those with Win7 ESU subscriptions.
You must have at least the August 2020 Servicing Stack KB4570673 previously installed to receive these updates).
There is a July 2022 Servicing Stack KB5016057– Download 32-bit or 64-bit for those with Win7 ESU subscriptions.
There are .NET Framework updates listed for Win7. See #2468767.
Note for 8.1 — the .net security issue originally fixed in May is rolled up into this:
To comprehensively address this vulnerability, Microsoft has released Monthly Rollup KB5016268 for .NET Framework 3.5 installed on Windows 8.1 and Windows Server 2012 R2. Microsoft strongly recommends that customers install the update to be fully protected from the vulnerability. Customers whose systems are configured to receive automatic updates do not need to take any further action.
Susan Bradley Patch Lady/Prudent patcher
(KB5016629) 2022-08 Cumulative Update for Windows 11 for x64-based Systems
(KB5012170) 2022-08 Security Update for Windows 11 for x64-based Systems
(KB890830) Windows Malicious Software Removal Tool x64 – v5.104
Installed, no hiccups, via Windows Update > Check for updates.
Overnight my NAS got the push,
(KB5016616) 2022-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems
(KB5012170) 2022-08 Security Update for Windows 10 Version 21H2 for x64-based Systems
(KB890830) Windows Malicious Software Removal Tool x64 – v5.104
Installed, no hiccups.
Win 10 21H2 – 19044.1889 if updated
I match geekdom using WUMgr and having to Clk Install TWICE for Win 10 21H2 = Failed Install. 2nd time quickly showed 3/3 (CU was 3rd in list) at about 70% Green Progress bar & the last 30% took 15-20 minutes. I NEVER have CU issues so I was due – but All is Well, so far.
W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0
that new KB5012170 secure boot dbx update replaces the KB4535680 update as noted by Microsoft in support article 5012170
although the older KB4535680 update is for 64bit Windows OSes only and KB5012170 covers both 32bit & 64bit Windows OSes
Running Windows 10 Home x64 OS
Getting Error Code: “0x800F0922”: Failed to install “Security Update for Windows (KB5012170)”
Tried a few online fix tips but still fails to install.
According to the release notes for KB5012170, some OEM firmware might not allow installation of this update. It doesn’t mention how it might fail or corresponding errors.
Can you tell us more about your system? Maybe you could check your OEM support site to see if there is any guidance.
There is at least one comment in this topic that would suggest it can successfully install on a Win10 MBR boot system
Successfully installed KB5012170 on Win10 21H2 (build 19044.1826) yesterday with no problems and it uses MBR (OS was “in-place” updated from Win7 to Win10 back in 2019.)
So MBR vs GPT shouldn’t be the real reason it’s failing to install.
BTW, I haven’t bothered converting my MBR drive to GPT (although I “did” verify it’d work using the mbr2gpt /validate /allowFullOS command) simply because I don’t use BitLocker or Secure Boot.
Of course, if I ever decide to upgrade to Win11 (which, the way things currently stand, ain’t gonna be any time soon) I’ll have to convert to GPT and enable Secure Boot.
Microsoft admits there is a problem with KB5012170 and is working on a solution, to be released soon. Whoop-dee-doo!
https://msrc.microsoft.com/update-guide/releaseNote/2022-Aug
Windows 8.1 is Issues-Free 🙂
well, except that Secure Boot update
Although offered, I don’t have secure boot on the Win8.1 test device..alarm bells rung! IIRC the last secure boot update eventually disappeared from WU by some MS miracle..hmmm
So the kb5012170 Secure Boot DBX update is in the WU sin-bin for now, otherwise a painless Win8.1 update experience this month.
So far, so good: no SFC errors, event viewer clean and WinSxS analysis is good after a post patch purge.imaged prior to updates 😉
Win 11 Pro now at build 22000.856 after
2022-08 Cumulative Update for Windows 11 for x64-based Systems (KB5016629)
2022-08 Security Update for Windows 11 for x64-based Systems (KB5012170)
2022-08 .NET Core 3.1.28 Security Update for x64 Client (KB5016987)
2022-08 .NET 6.0.8 Security Update for x64 Client (KB5016990)
Windows Malicious Software Removal Tool x64 – v5.104 (KB890830)
No Problems
--Joe
Successful update on 3 Win 10 Pro machines (2 Desktop 1 Laptop).
Win 10 Pro 21H2 – 19044.1889
No install or operational problems.
HTH
Updated Dell Optiplex 9020 to the latest KB5016616 and the other updates that came with windows update. Windows 10 21H2, no issues, stable machine.
I got the Secure boot update also, though my machine is legacy MBR. I will probably convert to GPT and UEFI at some point, or not.
Updated Win 21H2.
All well.
I updated my wifes computer this morning. Everything installed fine, Windows 10 Home 21H2.
After the update I attempted to boot from a bootable flash drive with my backup utility I use that I have used for 10 years. Upon selecting the boot device, I was surprised to see the message, “Invalid signature detected – Check secure boot policy in setup”.
I have never had that happen on her machine. She has UEFI mode secure boot system enabled, but I have been using this bootable flash drive to back up her system for years.
Only thing I can figure out is the update for Secure Boot KB5012170 has caused this. Anyone else have this happen? I shouldn’t have to go into BIOS and disable secure boot just to boot a properly setup USB flash drive. Should I uninstall the secure boot update?
I’m just looking for some advice, as I have never seen this error come up before on her machine when trying to boot the flashdrive. The backup utility is “Image for Linux” from Terabyte Unlimited. Never had issue with it until installing the secure boot update this morning.
Thank you for any advice…
Hi Susan:
Windows Update successfully installed the following Aug 2022 Patch Tuesday updates on my Win 10 Pro v21H2 laptop and I haven’t noticed any negative effects so far:
I did not receive this month’s KB5015733 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, but that’s expected since I have the Windows Update settings in my Local Group Policy Editor configured to only deliver stable .NET Framework updates that include a security patch.
Regarding the KB5012170 security update for Secure Boot DBX, also note that my BIOS Mode is UEFI and my system supports Secure Boot. I checked the status of Secure Boot in System Information (I entered msinfo32 in a Run dialog box) and confirmed that Secure Boot was disabled both before and after my Aug 2022 Patch Tuesday updates were installed (see attached image).
The only minor glitch I noticed this month was that it took several minutes for the status of KB5016616 [2022-08 Cumulative Update for Win 10 Version 21H2 x64 (OS Build 19044.1889)] to change from “Downloading – 100%” to “Pending Install“, but this isn’t unusual on my machine – I’ve reported this before for previous Patch Tuesdays. I also took the extra precaution this month of temporarily disabling my Malwarebytes Premium real-time protection after Windows Update started downloading my Aug 2022 Patch Tuesday updates – I don’t think this was necessary but some Win 11 users reported <here> in the Malwarebytes forum that Malwarebytes interfered with installation of KB5015814 during last month’s July 2022 Patch Tuesday updates.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1889 * Firefox v103.0.2 * Microsoft Defender v4.18.2205.7-1.1.19500.2 * Malwarebytes Premium v4.5.12.204-1.0.1725 * Macrium Reflect Free v8.0.6867
I still have KB5012170 hiddden, so it hasn’t run yet. I wonder what will happen, were it installed?
Hi WCHS:
Sorry, I have no idea how a BIOS update might effect the installation of KB5012170 (Security Update for Secure Boot DBX: August 9, 2022) or the status of Secure Boot on your Dell computer. Our models use different Dell BIOS versions – the support page <here> for your Inspiron 5482 2-in-1 recommends Dell Inspiron 5480/5488/5482/5580/5582 and Vostro 5481/5581 System BIOS v2.15.1 (released 21-Jul-2022), while the support page <here> for my Inspiron 5584 laptop recommends Dell Inspiron 5583/5584 System BIOS v1.20.0 (released 04-Aug-2022).
I reset my Inspiron 5584 to factory condition on 30-Aug-2020, which rolled my Win 10 Pro OS back to v1903. The attached image of a Belarc Advisor report captured a few days later shows my Secure Boot was already disabled in Sept 2020. I’m not certain, but as far as I know Secure Boot was disabled by default on my Inspiron 5584 when it shipped from the factory in Aug 2019 (see my 13-May-2021 post in DanDaMiniFig’s Dell G7 17 7790 Possible SupportAssist Error in the Dell forum for further information). Also note that I’m currently using Dell Inspiron 5583/5584 System BIOS v1.18.0 (released 13-Apr-2022) and don’t plan to update my BIOS to the latest v1.20.0 until I’m sure my August 2022 Patch Tuesday updates haven’t caused any adverse effects.
—————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1889 * Firefox v103.0.2 * Microsoft Defender v4.18.2205.7-1.1.19500.2 * Malwarebytes Premium v4.5.12.204-1.0.1725 * Macrium Reflect Free v8.0.6867 * Inspiron 5583/5584 BIOS v1.18.0
No issues after installing the Monthly Rollup (KB5016681) on two Windows 8.1 Pro desktops. The End of Support (EOS) notification tasks remain disabled (as reported in last month’s July updates).
The Security update for Secure Boot DBX (KB5012170) did show up in Windows Update. But I don’t use or need the feature so I did not install it (instead right click and hid it).
Successful updates so far:
x1 Win11 Pro on ARM Insider Beta 22H2 (KB5016694 22622.575, MSRT)
x1 Win11 Pro 21H2 (KB5016629 CU 22000.856, Security update KB5012170, MSRT)
x4 Win10 Pro 21H2 (KB5016616 CU 19044.1899, Security update KB5012170, MSRT)
x2 Win8.1 Pro (KB5016681 Rollup, KB5016740 .NET Rollup, MSRT)
x2 Win7 Pro (KB5016676 Rollup. KB5016367 .NET 4.8, MSRT)
NOTE: I allowed KB5012170 on my Win10 and Win11 installations, but NOT on my Win8.1 installations (hidden). So far, I have seen no problems, touch wood.
NOTE ALSO: None of my Win10/11 installations are Bitlocker encrypted.
Hi Susan:
I’m not sure if this is related to KB5012170 (Security Update for Secure Boot DBX: August 9, 2022) but there are Dell users posting in ecarpenter’s 11-Aug-2022 Inspiron 7391 Bios Update Enabled Bitlocker that they have been unable to boot their machines and log into Windows since their August 2022 Patch Tuesday were installed because they are seeing a message saying “Bitlocker needs your recovery key to unlock your drive because Secure Boot Policy has unexpectedly changed“. Both users insist that BitLocker has never been enabled before on their system and neither has any idea what their recovery key is.
The OP ecarpenter suspects a BIOS update triggered the problem on their Inspiron 7391 (“Literally the only thing I was doing was Windows updated and decided to do the Dell BIOS update last“), but user nobox posted <here> that they’re sure it was a Windows update that triggered this problem on their Vostro 5515.
Everything still looks fine on my Inspiron 5584 per my post # 2469714.
—————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1889 * Firefox v103.0.2 * Microsoft Defender v4.18.2205.7-1.1.19500.2 * Malwarebytes Premium v4.5.12.204-1.0.1725 * Macrium Reflect Free v8.0.6867 * Inspiron 5583/5584 BIOS v1.20.0
It has been my experience that Win10 and Win11 Pro turn on Bitlocker in the OOBE by default (at least the ones I have dealt with in the last year plus). The average user has no clue that this is happening, what Bitlocker is, or that there is even a Bitlocker key. And, if a Local ID is chosen over a Microsoft account, the key is not recorded without effort on the User’s part.
To me, this is setting up a disaster waiting to happen for that User. It’s not IF, it’s WHEN.
Not just Pro, but it’s suspended until the key is backed up:
When a clean installation of Windows 11 or Windows 10 is completed and the out-of-box experience is finished, the computer is prepared for first use. As part of this preparation, BitLocker Device Encryption is initialized on the operating system drive and fixed data drives on the computer with a clear key (this is the equivalent of standard BitLocker suspended state). In this state, the drive is shown with a warning icon in Windows Explorer. The yellow warning icon is removed after the TPM protector is created and the recovery key is backed up, as explained in the following bullet points.
Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge
I’ve got a Win8.1 to move over to Win10 in the coming weeks for family members as well as a Win7 to Win10..looking forward to the challenge!
Hacksaw, scalpel and USB toolkit at the ready 😛
After the Settings App, Group Policy, Regedit, and WUMgr, try this 😉 :
https://www.askwoody.com/forums/topic/removing-built-in-apps-from-win10-2004-20h2-21h1/
I neither want nor need encrypted drives. Is there some simple language somewhere that someone can direct me to that will explain how to keep encryption from being enabled.
If you’re confident that laptops will never be lost or stolen, then:
Microsoft recommends that BitLocker Device Encryption be enabled on any systems that support it, but the automatic BitLocker Device Encryption process can be prevented by changing the following registry setting:
Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker
Value: PreventDeviceEncryption equal to True (1)
Type: REG_DWORD
Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge
Windows 10 doesn’t automatically encrypt unless it’s specific units like Surface/certain Dell units.
If you want to bitlocker a drive, you have to enable it.
Susan Bradley Patch Lady/Prudent patcher
Search the net for Microsoft device encryption. This will lead to Microsoft support info on Bitlocker and Windows device encryption (for Home). The unwary can enable it inadvertently on their first signon to a Microsoft account.
For Windows 10, Convertible laptops are susceptible (modern standby for touch screens). On setting up my wife’s new 2020 HP Envy X360 15 with Windows 10 Home pre-installed and a Local admin account, I started to tinker with a few settings. On looking at Disk Management, I was startled to discover that Bitlocker was ready to go on my boot drive. After discovering and reading the support article, I was able to turn off encryption/Bitlocker before it became active (Phew).
HTH
Regards, Phil
Like you, I’d removed all the “built-in” apps, except those that simply can’t be uninstalled, way back in May 21 and hadn’t experienced any problems with installing previous monthly updates.
I was very surprised when it turned out to be at least one of those apps that caused the problems I encounter with this month’s update (why should this month be any different than all the prior months 
Anyway, once I “know” the update hasn’t caused any other problems, I’ll go back and removed those apps again.
I had the same experience as @Microfix . I have deprovisioned all the built in apps except the few like he left – on both x4 Win10 and x1 Win11. They have been gone since around the time I published this, on the Win10 installations, over a year ago:
https://www.askwoody.com/forums/topic/removing-built-in-apps-from-win10-2004-20h2-21h1/
No problem with the updates since then, including Aug updates this year.
KB5012170 : Some devices might start up into BitLocker Recovery
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:…
… but it’s not clear about what to do if you do NOT have Bitlocker enabled, ….I am Win10, 21H2, Secure Boot State is ON.
Hi WCHS:
Further to alejr’s post # 2471526, I believe the Bitlocker Recovery prompt that says “BitLocker needs your recovery key to unlock your drive because Secure Boot policy has unexpectedly changed” will only appear on some devices after KB5012170 (Security Update for Secure Boot DBX: August 9, 2022) is installed if:
So far, I haven’t heard of any Win 10 machines that are affected by this issue.
Unlike the Windows 11 v21H2 list of Known Issues <here> which specifically documents the KB5012170 / BitLocker Recovery prompt issue, the Windows 10 v21H2 list of Known Issues <here> only notes that the KB5012170 might fail to install with a 0x800f0922 error. This issue is still under investigation but the details <here> show that this 0x800f0922 installation error (which can occur with both Win 10 and Win 11) can sometimes be fixed “by updating the UEFI bios to the latest version before attempting to install KB5012170“.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1889 * Firefox v103.0.2 * Microsoft Defender v4.18.2205.7-1.1.19500.2 * Malwarebytes Premium v4.5.13.208-1.0.1740 * Macrium Reflect Free v8.0.6867 * Inspiron 5583/5584 BIOS v1.20.0
I ran wushowhide to see what was in the WU chute, and KB5012170 was pre-checked in the hide section. That was the first time that I got the result with an update pre-checked. I don’t have Bitlocker enabled but opted to hide the update for now.
I checked to see if I had BitLocker encryption option or enabled on my laptop. It is not listed in my device encryption options under Control Panel>Systems & Security. Also under Security & Updates>Device Encryption the info link for BitLocker says BitLocker is not available for Win 10 Home Edition, which is what I have. My device is protected by other device encryption which is turned on.
KB5015878 OS Build 19044.1865
Resolved: 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…
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...
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
