|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
ISSUE 19.17.1 • 2022-04-26 By Susan Bradley I’ve been holding my breath. For the past few weeks, I’ve been watching for attacks that researchers indic
[See the full post at: MS-DEFCON 4: Protect yourself with patches]
Susan Bradley Patch Lady/Prudent patcher
There are still problems with installing KB5012599
Windows 10 Update KB5012599 stalls with install error 0x8024200B and 0x800F0831
As of April 12, 2022, Microsoft has released security updates for Windows 10 and Windows Server. I have received information via user comments that the update KB5012599 for Windows 10 version 20H2-21H2 causes problems with some installations. The installation aborts with error code 0x800F0831 or error code 0x8024200B. In the meantime, I have done some research and summarized the issue in the following article…
Issue: Install error 0x8024200B
Regarding the update KB5012599, however, there are various user reports that it cannot be installed, but is aborted with the error code 0x8024200B…Problem: Installation error 0x800f0831
In the Microsoft Answers forum, there is this thread, where a user complains about installation error 0x800f0831. The error 0x800f0831 stands for CBS_E_STORE_CORRUPTION, and can have several causes. One cause, according to Microsoft, is that Windows has lost access to the Microsoft update servers (because, for example, a VPN, proxy or virus scanner blocks this access)…
Not seeing it widespread in consumer or even businesses. I think it’s something unique in their deployment. It’s a unique bug, not something that will be seen by Askwoody readership.
Susan Bradley Patch Lady/Prudent patcher
This is another one that I didn’t see widespread and impacting everyone. Fortunately that patch is a non security one so if you are impacted you can uninstall it.
Susan Bradley Patch Lady/Prudent patcher
Typo in patch list-
For office 2016 non-security updates:
5002188 (incorrect patch) links to 5002141 (correct patch)
5002185 (incorrect patch ) links to5002132 (correct patch)
I solved it.
I suddenly remembered that I recently had to install MS Windws Desktop runtime 6 for an app that I later uninstalled.
After uninstalling the runtime, KB5012117 installed fine.
Thanks anyway
I have updated Windows 10 21H2 with .net 3.5 and 4.8 as well as .net 5.0.16 and .net 6.04
Issue: Office 2016 Retail (C2R) updated to Preview version
Windows 10 21H2 Build 19044.1586, Office 2016 Retail (C2R) V2203 Build 15028.20160, updated 3/25/2022, one version newer than the approved version in the Master Update List (MPL) because C2R updates are restricted to “Enable Updates” and “Update Now”, which is a typical issue every month.
The MPL approved update as of today (04/26/2022) is V2203 Build 15028.20204, but after performing the same update procedure “About Outlook” tells me I now have Version 2204 Build 15128.20178 C2R. The only info I could find is that this is a “Current Channel (Preview) update.
I have no experience nor interest in testing a preview update, so where do I go from here? What could possibly go wrong?
“About Outlook” tells me I now have Version 2204 Build 15128.20178 C2R. The only info I could find is that this is a “Current Channel (Preview) update.
That build was released to the Current Channel yesterday:
KB5012599 (Win CU) and KB4012117 (.NET 3.5/4.8) installed successfully on Win 10 21H1 Home x64. Both done manually (from MS Catalog). No install issues and no other issues found so far.
Updated my two machines with the following April patches using WUMgr. No issues to report as far as I can tell:
1) Windows 10 Pro 21H2
– KB5012599 (Win CU)
– KB5012117 (.NET 3.5/4.8)
– KB890830 (MSRT)
2) Windows 10 Home 21H2
– KB5012599 (Win CU)
– KB5012117 (.NET 3.5/4.8)
– KB890830 (MSRT)
– Office 2013 April security patches
BTW, on both machines I was also offered, but did not install yet another release of the pesky KB4023057 update.
On the Home 21H2 machine only (apparently), I was also offered a new version of KB5005463, i.e. PC Health Check Application, which I did not install: no need for yet another tool that tries to mess with my updates seeing that the KB article mentions that “ PC Health Check application … will automatically install important application updates when they become available. PC Health Check users will not be able to turn off automatic updates.“.
. Reason: Fixed KB number of .NET framework update
Windows 8.1 Pro x64. Installed the following without any apparent problems.
.NET Framework (KB5012331) followed by Restart (Restart not required)
The latest Security Stack Update (SSU), KB5012672, followed by Restart (again, the Restart is not required). Manually downloaded and installed from the MS update catalog.
April Rollup (KB5012670), followed by Restart (required).
I’m in the habit of restarting (as opposed to shutdown and subsequent start) after every update even if it’s not required.
The latest SSU is required this month for installing the Rollup.
Thank you!
Just received and installed KB5005463 PC Health Check Application for W10 Pro 21H2.
And so you are now not able to turn off automatic updates?
The bold text has nothing to do with monthly Windows update. Running the tool will update important application (PC Health) updates not Windows updates.
April patches installed with no problems to report on Win 8.1. 🙂
Installation Successful: Windows successfully installed the following update: 2022-04 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 for x64 (KB5012331)
Installation Successful: Windows successfully installed the following update: 2022-04 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB5012670)
Installation Successful: Windows successfully installed the following update: 2022-04 Servicing Stack Update for Windows 8.1 for x64-based Systems (KB5012672)
Win 10 ver. 22H2 x64
Sigh!
On reading this post I updated my Dell’s Win10 straight away… or attempted to.
Windows seemed to be doing fine but the update stalled. I gave it half an hour. No go. Windows being the boy that cried ‘wolf’ (stalled updates with no reason provided by Windows) I thought this was a regular stall that would fix with a restart. Windows woke up very sick. I decided to perform a system restore (Windows not Dell). Windows woke up dead!
My account as well as Windows was unrecoverable using Dell’s recovery option. {Dell has a monstrous set of support assist remediation backups. What a waste of disk space they turned out to be!}
My choice was to reset the laptop to original. The laptop is aging so had an old version of Windows 10. It had to go through a couple of rounds of update and restart before deciding Stick with 10 or “Windows 11 time” and via upgrade rather than clean install (which I suspect would wipe Dell’s useful recovery options as well Dell’s unwanted trash and I did not wish to toss the baby out with the bath water). Windows would not let me upgrade to 11 before upgrading to something more recent. Sigh!
Hours later, Windows 11 is running. Hours later, regular programs are installed and most problems are resolved (the big one was Defender interface would not load – reset via powershell cured it) and I desperately need sleep. To do list: Tweak, tweak, tweak.
So, why did it break, you ask. I discovered later when Windows awoke sick that Internet was down. My guess is that update wanted something it could not fetch. My impatience and lack of a simple check contributed.
Moral of the story. If update stalls, check internet status as well as giving it the usual long wait before trying a restart.
PS I use a cloud service to store data (including desktop where current things reside) so absolutely nothing of any importance was lost. (I also have a thumb drive that Windows backs data to continuously and an offline disk used periodically).
PPS Rather than Powershell, Ipossibly could have right-clicked the Windows Security icon, chosen ‘Settings’ and used Repair then the option to Reset if that failed.
Finally: It will take a while to get used to the changes (e.g. locating different settings) but so far my experience with Windows 11 indicates the change is positive.
Group A (but Telemetry disabled Tasks and Registry)
1) Dell Inspiron with Win 11 64 Home permanently in dock due to "sorry spares no longer made".
2) Dell Inspiron with Win 11 64 Home (substantial discount with Pro version available only at full price)
I consider Windows Update to be fragile. Having the Internet go down or a power loss or re-booting or canceling at the wrong moment may prevent Windows from recovering. So my recommendations include:
1) Follow MS-DEFCON recommendations.
2) Make sure your security software is up to date.
3) Do image backups. Have at least an incremental backup before doing Windows Update.
4) Have a recent re-boot and an idle system before starting.
5) Require good weather when running Windows Update to reduce the likelihood of power failure.
6) Have a strong known working Internet connection. Do a quick browsing sanity check before starting.
7) Do not update while traveling.
8) Have a lot of patience. Don’t be quick to cancel. Some Windows Update processes like TiWorker.exe can run slowly for long periods and some machines are under-powered for Windows 10+, such as my laptop, which takes many hours to update.
9) Don’t re-boot until Windows Update shows it’s really finished installing all permitted updates.
Windows 10 22H2 desktops & laptops on Dell, HP, ASUS; No servers, no domain.
I consider Windows Update to be fragile …
How about adding
10) If there is more than 1 update, do them one at a time. If you are using WUMgr or WUSHOWHIDE, unhide and install them one at a time. Let one finish and let the system restart, before unhiding and installing another one ?
…If there is more than 1 update, do them one at a time…install them one at a time. Let one finish and let the system restart, before unhiding and installing another one…
AMEN!!! That exact procedure has kept me safe and sane with regards to WU since 2004 after witnessing a good friend’s unit succumb to excessive updates trying to individually reboot the computer when the others weren’t done installing. My friend and I were partly to blame, as we told WU to install all of the updates in the rather lengthy list, trusting it (WU) to make the right decision(s) with regards to timely rebooting during the updates’ installation routines.
The computer (with Windows XP) blue screened while we had gone out to get a bite to eat. We returned after about an hour to the blue screen. Several attempts were made to resurrect the computer, but to very limited success…half the hard drive was unusable due to excessive errors from what I recall.
After that fiasco/debacle/(pick your own very strongly phrased word of choice to express extreme disappointment), I decided that I would NEVER allow WU to go it alone with regards to installing a list of more than one update. I have since then insisted on having WU install updates one at a time in numerical order (with regards to the assigned KB number of each update), rebooting if requested after the update’s installation. The only exception I’ve made is to the now-monthly MSRT…I’ll let it install and if its log indicates that it didn’t find anything, I’ll proceed to install the next update and then reboot the machine. And so on and so on.
This month for the April updates, I rebooted twice, first after installing MSRT and the .NET update and a second time after installing the monthly parch for Windows, KB5012599. WU did not prompt me for a reboot after installing the .NET update, but I did so anyway in keeping with my policy as stated above.
Back in 2016 Brian Krebs wrote “Anytime there’s a .NET Framework update available, I always uncheck those updates to install and then reboot and install the .NET updates; I’ve had too many .NET update failures muddy the process of figuring out which update borked a Windows machine after a batch of patches to do otherwise”.
I’ve always followed this advice.
Windows 10 Home 22H2, Acer Aspire TC-1660 desktop + LibreOffice, non-techie
Updated my two machines with the following April patches one by one, creating a restore point each time before using WUSHOWHIDE to unhide, then download and install, in the following order. No issues to report:
Windows 10 Pro 21H
– KB5012117 (.NET 3.5/4.8) – requires a restart. 2 minutes
– KB KB5013354 (.NET 5.0.16) – no restart required. 1 minute
– KB890830 (MSRT) – no restart required. 1 minute
– Powershell’s sfc /verifyonly afterward – no integrity errors
– KB5012599 (Win CU)
…..download (7 min)
…..install (10 min)
…..restart to finish (3 min) = 20 min total
–sfc /verifyonly afterward – no integrity errors
Another reminder to never install optional updates. Microsoft does it again.
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.
