MS-DEFCON 2: Batten down the hatches for January

Topic

New Reply

ISSUE 19.01.1 • 2022-01-06 By Susan Bradley Microsoft has started off the patching year — and not in a good way. Soon after midnight all across the wo
[See the full post at: MS-DEFCON 2: Batten down the hatches for January]

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Replies

Amazing. When I first learnt to program properly in 1969, integer overflow issues were one of the first things we were taught to watch for.

Chris
Win 10 Pro x64 Group A

Reply | Quote

Chris B wrote:

Amazing.

Yeah, same here (but a few years later). Boundary conditions was one of the first concepts drilled into me.

Reply | Quote

Hi, small correction on the Y2K22 bug: according to MS Exchange Team blog, it’s popping up in EXCH 2016 / 2019, but not 2013.

BfN, Konrad

Reply | Quote

Updated the post, thanks.  Actually all three are impacted but only 2016/2019 got nailed and wouldn’t send emails.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

It’s not only Microsoft. Recently read an article from Jalopnick(?) that said Honda cars are having the same problem – resetting the date back.

Reply | Quote

From the DailyMailOnline:

“Owners of older Honda cars have been left baffled, after a technology glitch caused the clocks in their cars to get stuck 20 years in the past, displaying the year 2002. People driving Honda vehicles from 2004 to 2012 seem to have been hit by the issue, with dozens taking to social media and Honda forums to complain. It appears to be isolated to models equipped with navigation systems, causing the clock to switch from 2022 to 2002 every time the engine is started.”

Coincidence? Mmm, well, maybe!

Reply | Quote

Unverified but strongly suspected related fallout. Just got call from hospital saying that my health insurance for 2022 is unverified (i.e., canceled) even though it was for all of 2021 and earlier, and that I may be responsible for paying for tomorrow’s MRI.

It seems that the hospital has noted that ALL patients with this particular health insurance provider and the physician’s group are in the same quagmire, so I’m not alone.

I hope that between the two computer departments that they figure out the problem soon and apply the patches. To be (suddenly) financial liable for thousands of dollars for medical procedures is quite alarming.

1 user thanked author for this post.

wavy

Reply | Quote

2022 wobblyness is not just a Microsoft thing:

https://www.bleepingcomputer.com/news/technology/honda-acura-cars-hit-by-y2k22-bug-that-rolls-back-clocks-to-2002/

Still I probably won’t be dealing with the potential internet wide issues coming around 2030 (hopefully 2036, 2038 being designed out by now..). This is a fun read:

https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs#Year_2031

 

 

 

Reply | Quote

Hi, Have updated both my PCs to W1021H2 as inctructed. Falling off a log would have been much harder. But when can we have a reg. file for the next feature update we have to worry about? I love Susan’s little reg. files!

1 user thanked author for this post.

Coldheart9020

Reply | Quote

The next feature update won’t be until fall 2022. You’ve got plenty of time.

You did not mention whether you are running Home or Pro. If you are running Pro, you can use Group Policy to manage the updates.

--Joe

Reply | Quote

Many thanks. My desktop tower is Pro, my laptop Home. I do use Group Policy for the tower, but would be lost without a reg. file for my laptop.

Reply | Quote

I’ll be doing the reg files on a regular basis, so no worries.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

CAS, The Surfing Pensioner

Reply | Quote

Wait, you posted a .reg file / fix that lets us prevent Windows 10 Home v.20H2 from being updated to v.21H2, and I missed it? Heavens to Betsy! Where, oh where, can I find that .reg file/fix?

 

Reply | Quote

oldguy wrote:

2022 wobblyness is not just a Microsoft thing

There’s a saying: “When Heathrow sneezes, all of Europe gets a cold.”

Bugs from Microsoft have a global impact.

Reply | Quote

WSstarvinmarvin wrote:

prevent Windows 10 Home v.20H2 from being updated to v.21H2,

21H2 is a small couple of minutes enablement package update and is recommended.
There is no need preventing the update.

Reply | Quote

Which update is it that takes away Control Panel?

Reply | Quote

I’ve just updated to W1021H2 and I’ve still got a Control Panel. Don’t panic. Nothing critical gets snitched away.

Reply | Quote

On both my machines, on Windows 10 Pro, it took a couple of hours to go from 21H1 to 21H2, but both installed OK

Chris
Win 10 Pro x64 Group A

Reply | Quote

WSstarvinmarvin wrote:

Which update is it that takes away Control Panel?

None.

Reply | Quote

Will Fastie wrote:

There’s a saying: “When Heathrow sneezes, all of Europe gets a cold.”

The way that Heathrow, and its major client, BA, is running its business, it is becoming less and less relevant to Europe.

But then, this is a computing forum and not an airlines forum.

Dell E5570 Latitude, Intel Core i5 6440@2.60 GHz, 8.00 GB - Win 10 Pro

Reply | Quote

Chris B wrote:

it took a couple of hours to go from 21H1 to 21H2

On my Windows 10 Pro it took 3 minutes (downloading – installing) using WUmgr.

Reply | Quote

Susan suggests deferring until Jan 25 but my maximum deferral date is Jan 20, not very long past the upcoming Patch Tuesday.

I’m wondering which patching poison is less harmful: Update now before Patch Tuesday or defer until Jan 20 and hope the next patch batch is less awful than the current.

Advice?

Edition Windows 10 Pro
Version 21H1
Installed on ‎6/‎7/‎21
OS build 19043.1415
Experience Windows Feature Experience Pack 120.2212.3920.0

Reply | Quote

https://www.askwoody.com/2020/is-there-a-way-to-cheat-pause-update/

cheers, Paul

Reply | Quote

I am running the latest Microsoft Edge 97.0.1072.55 and it never closes when I shut it down. Anybody else seeing this. I’m running WIN 10 21H2 19044.1415.

I know this because I have CCleaner Professional that should automatically clean up wjen Edge shuts down but it doesn’t

Reply | Quote

Open Task Manager (right click on the Task Bar) and look for Edge processes. If there are none, Edge has shut down.

cheers, Paul

Reply | Quote

Check whether “Startup boost” and/or “Continue running background extensions and apps when Microsoft Edge is closed” is enabled at Edge, Settings, System and performance:

To improve Microsoft Edge startup speed, we have developed a feature called startup boost. Startup boost keeps the browser running in the background with minimal processes, so Microsoft Edge will start more quickly when launched.

Get help with startup boost

By default, Microsoft Edge allows background apps and extensions to continue running in the background, even after you close Microsoft Edge.

Disable Continue Running Background Apps when Microsoft Edge is Closed

Reply | Quote

I disabled the Continue Running Background Apps and this made no difference.

Thanks

Reply | Quote

And Startup boost is off?

Reply | Quote

Just set that to OFF and it closes now. I might try setting the Continue Running Background Extensions to ON again and see whether this is the magic combination.

Thanks

Reply | Quote

I set the Continue Running Background Extensions to Enabled and it closes fine.

Something else to watch for after January patches.

Reply | Quote

Just updated to 97.0.1062.62 without the January fixes and it still needs the Startup boost to ne disabled.

Reply | Quote

Made the registry change detailed in todays entry and again this made no difference. I still have to have Startup Boost disabled for Edge to close when I click the close X

Reply | Quote

SuzCPA2 wrote:

Update now before Patch Tuesday or defer until Jan 20 and hope the next patch batch is less awful than the current.

Update now (and defer tomorrow patch Tuesday 11/01/2021) as Dec. 2020 got defcon=4.

1 user thanked author for this post.

SuzCPA2

Reply | Quote