Patch list for January 2023 – final update

Topic

New Reply

I realized tonight that I hadn’t done my final recap of the January updates on the Master Patch List page We’re just about to get ready for the Februa
[See the full post at: Patch list for January 2023 – final update]

Susan Bradley Patch Lady

2 users thanked author for this post.

Mike W, deuce120

Reply | Quote

Replies

You might receive an error with apphelp.dll from apps using DirectX

After installing KB5019980, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 26.20.100.7463 up to 30.0.101.1190. This issue might happen intermittently and affects apps which use DirectX or Direct3D to render part or all of their content.

Workaround: To mitigate this issue, you can install an Intel graphics driver with a later version than 30.0.101.1190. It is recommended to check your Windows device manufacturer’s support for the latest version of the Intel graphics driver for your device. If they do not offer a driver later than 30.0.101.1190, you can check List of Drivers for Intel Graphics for information on how to download and install the latest Intel graphics driver available from Intel directly.

Next steps: We are working on a resolution and will provide an update in an upcoming release…

Affected platforms:

​Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
​Server: Windows Server 2022

* Windows 11(KB5019980/KB5019961), Windows 10 (KB5019959)

Reply | Quote

I have Windows 10 Pro Version 21H2 installed on my PC. I want to install Version 22H2. I entered “Windows 10” and Target Version “22H2” instead of leaving the Target Version blank.  This is the method I’ve used in the past.  Please confirm this method will install Version 22H2.  Thank you.

Reply | Quote

That method should cause you computer to be offered Win10 22H2 in Windows Update (provided you have no other settings or software blocking it).

2 users thanked author for this post.

280park, Mike W

Reply | Quote

Worked for me a few days ago. Had just applied 2023-01 updates to our household’s last 21H2 system. Changed targets and rebooted. Since I had a fresh backup just before the update, I clicked Check for updates and the 22H2 update started immediately.

1 user thanked author for this post.

Mike W

Reply | Quote

I failed to install the Windows 10 Pro Version 21H2 (January 2023 Update) before upgrading to Windows 10 Pro Version 22H2.  Consequentially, Windows 10 Pro Version 22H2 and the Windows 10 Pro Version 21H2 (January 2023 Update) were installed at the same time and probably in that sequence (unless Windows Update had the intelligence to install the 22H2 (January 2023 Update) instead of the 21H2 (January 2023 Update).  I cannot tell for sure which version was installed.  My PC is not having any problems so don’t intend to do anything else.

Questions:

(1) How can I determine whether the 21H2 or 22H2 version of the January 2023 Update was installed?

(2) Should the installation sequence described above cause any problems?

(3) I assume that, going forward, the 22H2 version of the February 2022 Update will be installed, which will supercede and fix any potential problems.  Is this correct?

Reply | Quote

The January update for 21H2 and 22H2 are both the same KB5022282 (Builds 19044.2486 and 19045.2486).
The difference is that 22H2 has the Feature Experience Pack for 22H2 turned ON, and 21H2 does not.

To see what’s installed go to:
Settings\Update & Security\Windows Update\View Update history
At the top click on “Uninstall updates”

To see what you are running:
Settings\System\About

1 user thanked author for this post.

Mike W

Reply | Quote

Settings\System\About indicates that my PC is running Windows 10 Pro Version 22H2, OS Build 19045.2486 with Windows Feature Experience Pack 120.2212.4190.0.  Does this information indicate whether the 21H2 or 22H2 (January 2023 Update) was installed?

Reply | Quote

PKCano wrote:

To see what’s installed go to: Settings\Update & Security\Windows Update\View Update history At the top click on “Uninstall updates”

KB5022282 listed at “View update history” and found at the above location (if you looked) show 2023-01 (that’s January 2023).

And KB5022282 shows the date and the Build number.

So if you see any of that information, it would indicate it is installed.

1 user thanked author for this post.

Mike W

Reply | Quote

KB5022282 OS Build 19045.2486 is installed.  There’s no “2023-01” notation but KB5022282 is known to be 2023-01.  My question is whether the 21H2 Version or 22H2 Version of KB5022282 is installed.  Thanks.

Reply | Quote

Run winver.

1 user thanked author for this post.

Mike W

Reply | Quote

KB5022282 is the SAME for both versions – there is NO KB5022282 for 21H2 different from 22H2. 21H1, 21H2 and 22H2 all have the SAME CU. The only difference is which Enablement Package is turned ON. You have the Package for 22H2, 21H2 has a different Package.

1 user thanked author for this post.

Mike W

Reply | Quote

Mike W wrote:

My question is whether the 21H2 Version or 22H2 Version of KB5022282 is installed. Thanks.

@Mike-W –

If you carefully read through the bulletin for KB5022282 by clicking on the down arrows under the “Improvements” category in the bulletin for each version that the KB article covers, you’ll see that there is no difference between what the monthly update does for 21H2 and 22H2. So, you’re basically worrying about nothing. There’s no difference in what is in the monthly update for 21H2 and 22H2.

Count the fact that you’re fully updated to 22H2 with the January patch successfully installed as a solid win! Just so you know, build number 19045 indicates you’re on 22H2 and the .2486 indicates that you’ve got KB5022282 installed.

When I updated from 21H2 to 22H2 at the end of this past November, I did it AFTER having successfully installed the latest monthly update for that lower version (21H2) FIRST. After seeing that my machine had successfully installed the monthly update and successfully rebooted after the installation, I then proceeded to allow it to update from 21H2 to 22H2. The change from 21H2 to 22H2 took only about two or three minutes.

The above procedure is exactly what I’ve done ever since coming into the Windows 10 fold back in 2020 with Windows 10 version 2004, and it’s worked perfectly every time since.

Going forward from here, when the next Feature Update comes out late this year, which will probably be called 23H2 (or maybe even 2300), it will “automatically” include the latest monthly patch that was last released. So, for example, if 23H2 comes out in late October, it will include by default the October monthly patch. This can be problematic if the October monthly patch is currently causing problems, as updating to 23H2 will do the same since it will “include” the October update. Therefore, the best thing for you to do next time you want to install a Feature Update is to wait until after Susan has green-lighted both the Feature Update’s installation AND green-lighted the latest monthly update as well.

I hope this helps resolve any confusion you may have had.

1 user thanked author for this post.

Mike W

Reply | Quote

Bob99 – Thank you for your very detailed response and education about the Windows Feature Updates and Monthly Windows Updates.  And thank you to PK Cano for always answering my questions in a thorough and timely manner.  I’ll continue to follow Susan Bradley’s advice and also save the information you both provided for future reference.

Reply | Quote