Bork Tuesday, Any Problems Yet?

Installed without issue as per usual.

https://support.microsoft.com/en-gb...-preview-237a9048-f853-4e29-a3a2-62efdbea95e2

 

Roger that. Thanks.

Its cool @Krusty

 

Thanks, no issues as well on my machine.

 

Microsoft confirms Windows 10 desktop and taskbar issue
Nov 17, 2022
https://www.ghacks.net/2022/11/17/microsoft-confirms-windows-10-desktop-and-taskbar-issue/

 

I just got a cumulative update in the Release Preview channel (KB5020044). Not sure if it is released for standard release builds or not.

 

I have not noticed anything as of yet on stable.

 

Well they stated the year breaking domain controllers. They may as well wind it down doing it again. Probably not many "insiders" (unpaid beta testers) that have users running domain controllers in the insider program.

 

So was this the third Domain Controller bork of the year? They obviously aren't using any in their "testing".

 

All updates went well x2 Windows 10 machines today.

 

Same here, although several restarts were required...

 

Same here. Trouble free Tuesday patch updates. Only one restart needed.

 

Quick and easy install after manual download from Windows Catalog. Each update (.NET and CU) needed one reboot. W10 22H2, old i3 laptop w/ SSD

 

https://www.ghacks.net/2022/12/18/several-windows-10-versions-affected-by-blue-screen-issue/

 

I have not installed updates this month yet. If i do it now will i get the fixed 1233 update.

 

No.

https://learn.microsoft.com/en-us/w...eive-an-error--0xc000021a--with-a-blue-screen

 

Thankfully, no blue screens here. Both installed fine and haven't had any issues (yet). I did a "cleanup" also afterwards and like I said: everything's good. Wish that ghacks article was a tad more specific.

 

I've had no crashes since installing the CU. The Microsoft article references "hidparse.sys in c:/windows/system32," which I don't have on W10-64 22H2 even with hidden files shown, but there is another hidparse.sys in a different subfolder, which matches exactly the hash of the one in /drivers. I don't know why some users (but not others) would have a copy in /system32.

 

Found it in the drivers subfolder

 

My speculation is the screw up is in the Win cleanup processing.

Below is where hidparse.sys is normally found in System32 directory on Win 10:



The backup copy of the driver is located in the DriverStore subdirectory.

When the cleanup utility runs, it is updating what is in DriverStore directory with the hidparse.sys version previously updated in the drivers subdirectory. The replacement version of hidparse.sys is just temporarily stored in the System32 directory and then deleted once cleanup processing completes. Somehow a wrong version of hidparse.sys is being loaded in this processing. It also appears the above activity goes on at system boot time.

By forcing both versions of hidparse.sys to be the same via noted Recovery Environment action, it allows cleanup processing to complete successfully and not BSOD the device.

 

Further speculation is this BSOD issue only occurs when the hidparse.sys driver is loaded when CU KB5021233 is applied.

It appears that hidparse.sys is used in USB drive processing. I therefore theorize that only affected Win 10 installations that happened to have a USB drive connected when KB5021233 was run and subsequently rebooted, are the installations affected.

 

Let me know when 1233 update BSOD problem is fixed and i can install it.