|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
ISSUE 19.52.1 • 2022-12-27 By Susan Bradley I have a favorite Christmas song titled “We need a little Christmas,” from the Broadway musical “Mame.” Th
[See the full post at: MS-DEFCON 3: Windows 10 22H2 may leave you blue]
Susan Bradley Patch Lady/Prudent patcher
As always, thank you Susan! You recommended an option to defer updates until January. So, I tried setting my advanced windows update settings to later in January, but can only go as far as January 4, since I deferred December and pause settings will only allow 35 days until I update again. Doubtful that MS will fix the issues by then, but I guess I’ll have to take my chances. I do always back-up before updating, and I don’t run any games hardware or software, so fingers crossed.
Cheers
That happened to me once, and what I did out of desperation was to click on “Resume Updates”, but before it really had time to do anything besides begin checking for updates, I clicked on “Pause Updates”. It let me click on it 5 times, to delay another 35 days. I am in nearly the same boat as you, because I am paused until January 6, so I will be trying this strategy again.
It’s been my (limited) experience with Win10 — and I learned this trick from Susan — that you can further extend your existing pause by disconnecting from the internet, then opening Windows Update and clicking Resume (which will fail, because no internet), and then setting a new pause date.
See my How to unpause Windows updates “without” using the Resume updates button topic.
None of the described methods require a reboot. They simply remove the date the pause is scheduled to end and change the update status back to active (without triggering a Windows update check) which then allows you to then go back and pause your updates for up to another 35 days!
If you have a full disk image backup, you boot from the backup program’s Recovery USB drive and restore the image which should be on an external USB hard drive.
You do not boot from the computer’s HDD/SDD.
Thank you for the update.
The knowledge of it will be used at work.
Personally I got so tired of the MS b.s. that I installed Linux about 3 months ago. I haven’t seen an app crash, BSOD, faulty driver or any other issues since then.
Had a couple of corrupted initramfs errors after updates but nothing a fsck or dpkg –reconfigure couldn’t resolve in about 1 minute.
Even all my games play flawlessly.
I am SO impressed by the state of Linux I am going to, time permitting, convert all my PC/Srv’s this year.
My Win10/Win11 images run from upper 20’s GB to around 50GB. It will depend on how much is on your main drive. If you have a lot of pics/movies or other files, it could vary.
I usually do a full image once a month, then differentials once a week in between. I also run a data file back whenever I make a lot of changes (to to my documents or add holiday pics, for example) for quick access.
Also, the drives seem to need the USB C connector and my laptop only has the older larger USB port (A??). Will a converter cable work? Thanks again.
Yes, a USB A to USB C converter cable will work, as long as it’s not a “charging only” cable for a cell phone (those only include the 2 leads needed to transfer power, not the other leads needed to transfer data.) If you use a charging only cable (which are much thinner that a normal USB cable) your PC won’t recognize the drive when you plug it in.
Just FYI, “most” external backup drives that use a USB C connector will include a USB A to USB C cable were thumb drives don’t.
Aging computer? I have a 1998 computer with Win 95B on it and a computer built in 2000 with Win 98 SE on it. Both computers run well and I use them mainly to play old games. Those are, in my opinion, what I consider “aging computers”. 🙂
Usually I’m not in these, however, being years end it gives me a chance to express my thanks for all youses do to keep us informed. It is much appreciated. Cya next year everyone.
Rollup – Hidden
MSRT – Hidden
5021093 – NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 x64 – Installed
5021296 – Security Only – Installed
IE/Edge – Not Applicable
5012170 – Security update for Secure Boot DBX – Not offered, would’ve hidden.
Win 8.1 (home & pro) Group B, Linux Dabbler
Aging computer? I have a 1998 computer with Win 95B on it and a computer built in 2000 with Win 98 SE on it.
I guess you didn’t buy Samsung. I bought a top-of-the-line gaming computer from them in 2013, and have had nothing but trouble with it from the first week when it wouldn’t shut off.
Now the the battery is swollen and is pushing up the keyboard. It takes ten minutes to fully boot. It won’t completely recharge and discharges quickly.
Foolishly, I bought a Samsung printer shortly afterwards and I had so much trouble with it that I had to junk it and buy a new printer.
Wisely, I think, Samsung doesn’t make computers any more. 🙂
I intend to get another Windows computer in the new year, but I dread getting Windows 11 with it.
Mark
Buy it from a company that builds it to order, rather than getting it off the shelf. If in the UK, I’d strongly recommend PC Specialist, but I’m sure there are equivalent companies in the US or elsewhere that others can recommend. That will enable you to specify Windows 10 rather than 11.
Same here. No issue for my two 22H2 Pro and one 22H2 Home for more than a week. Note that none of them has hidparse.sys in \System32, only in \drivers.
Installed December updates without problems on four Windows 10 21H2 computers, two of which had the duplicated hidparse.sys file in the Windows\System32 directory and two that didn’t. That file was last updated with the November updates and didn’t change for December. Afterwards was able to apply the 22H2 feature update to all computers without incident-much less involved than the monthly update as has been the case recently with feature releases.
It’s not obvious from a hardware/software view what leads to the duplicated hidparse.sys file. Three of the four computers were Dell desktops and a laptop, and the fourth was a Surface laptop. The Surface laptop and one of the desktops were the ones without the duplication. I had previously reinstalled 21H2 (not replacing apps and data files) on the desktop last summer to resolve update problems stemming from some corrupted files-maybe that knocked out whatever was doing the duplication? I have two more Dell desktops to update and will see what holds for them, but clearly, the reported December update problems are not driven solely by the presence of that file in the System32 folder, and previous monthly updates appear to have been updating it.
The alerts honestly are not behind a paywall and detail out the situation. The situation is NOT 22H2 rather some computers have two mismatched files. Read the alert here and the details are listed.
I have installed the December updates on all of my 22H2 with no issues. So it’s not EVERY machine impacted. I think it’s third party/gamers most impacted.
Susan Bradley Patch Lady/Prudent patcher
HP Elite Desktop, Win 10 Pro, 21H2. Home user. Took all the December updates. No problems. Allowed me to keep my Classic Shell START. Was able to delete the news icon being offered.
The external hard drive onto which I back up my laptop was left at my place about 10 years ago by a friend who bought it second-hand on Ebay. He used it to download and save films. I came across it in my cupboard earlier this year, formatted it and have been using it ever since for the full image backup. Works fine – had it checked by my PC technician when he was last round.
They just don’t make ’em like that any more.
Spent yesterday updating our fleet of Windows 10 Pro laptops and workstations including our backup PCs that are in storage.
Bottom line, we experienced no issue with our computers running Windows 10 Pro 22H2, 22H1, or 21H2.
Updates for our in-service computers included:
The only problem we experienced was with an old Windows XP workstation – it had problems booting. We are now preparing it for the recycle bin by wiping its drive and removing reusable components.
With only 1 update remaining after this update of Win 8.1 🙁
December patches installed with no problems to report on Win 8.1. 🙂
Installation Successful: Windows successfully installed the following update: 2022-12 Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 for x64 (KB5021093)
Installation Successful: Windows successfully installed the following update: 2022-12 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB5021294)
With the issues going on with Windows 10, for instance the hidparse.sys issue this month, I am sure going to miss the stability of Windows 8.1 when it is eol next month. 🙁
Win 10 ver. 22H2 x64
Thanks! All updates succeeded here too.
Being as you have a new board maybe give it another week or month so if issues pop up you won’t have to wonder if it is from the upgrade. That said, almost everything I maintain (about 50-60 systems) is on 22H2 for a couple months or so and have no reported issues.
Never Say Never
Found this article discussing mitigations: https://windowsreport.com/kb5021233-windows-10-22h2-hidparse-blue-screen/ Downloaded their Rec’d Restore.exe but not installed
That “Restoro” PC Repair tool is a sponsored advertising link unconnected with this issue.
Restoro is treated as a Potentially Unwanted Program by Malwarebytes, as you have to pay $30 or $40 for it to fix anything.
Are Windows 11 PC’s immune to the hidparse blue screen problem? Thanks
This article implies Win11 are susceptible but not mention in this thread:
https://www.thewindowsclub.com/fix-0xc000021a-blue-screen-error-on-windows
They wrote a generic article around a specific solution, and their implication is incorrect.
The hidparse.sys BSOD problem happens on “some” systems when KB5021233 is installed.
KB5021233 only applies to Windows 10!
If you don’t have the file in the C:\Windows\System32\ folder (the only one is in the C:\System32\drivers) or they are identical in both folders (same date/version), you are OK.
Yep, you’re good to go! 👍
Like you, I only have the one version number ending in .2251 in the \drivers folder on both of my computers, and neither one of them had any problems related to that file. I.E. no Blue Screens Of Death.
KB5021233 is the Dec update for Windows 10 20H2, 21H1, 21H2 & 22H2.
KB5022155 is the Dec update for Windows 11 22H2.
And no, if you didn’t experience the BSOD problem (which only happens to some users) , there’s no reason to remove the update.
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.
