Microsoft pushes Win10 KB5014666 (19044.1806) update, confirming that 22H2 is coming

IT House reported on June 24 that although Win11 has arrived, Microsoft still plans to continue to support Windows 10 systems at least until the end of 2025. This means that users will not need to worry about security issues for the next few years, and there will be several major “feature updates” coming.

Microsoft today released optional cumulative update KB5014666 for Windows 10. Microsoft said that this version mainly fixes the problems that caused the game to crash and update.

The cumulative update is reported to be part of Microsoft’s June Update “C” update, which is designed to enable Windows customers to test and fix bugs ahead of the July 12 release to all users, which will then be available as the next Patch Tuesday part of it appears on all user PCs.

Unlike the regular Tuesday Update, this Windows Non-Security Preview update is optional and only provides bug fixes and performance improvements.

Existing foreign media found that Microsoft integrated the content of the next version (22H2) in KB5014666/with the help of the command line. We can see that Windows 10 22H2 is version 19045.

Users who have downloaded and installed KB5014666 can activate version 22H2 using the command prompt.

IT House learned that we just need to start CMD as administrator and paste the following:

dism /online /add-package /packagepath:%windir%servicingPackagesMicrosoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum
dism /online /add -package /packagepath:%windir%serviceingPackagesMicrosoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
dism /online /add-package /packagepath:%windir% servicingPackagesMicrosoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum
dism /online /add-package /packagepath:%windir%servicing PackagesMicrosoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
dism /online /add-package /packagepath:%windir%servicingPackagesMicrosoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum
dism /online /add-package /packagepath:%windir%servicingPackagesMicrosoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
dism /online /add-package /packagepath:%windir%servicingPackagesMicrosoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1806.mum
dism /online /add-package /packagepath:% windir%servicingPackagesMicrosoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum

It’s worth mentioning that if you want to undo your changes, you can replace add-package on each line with remove-package and execute.

Of course, forcing Windows 10 22H2 won’t bring you any new features either.

In fact, Windows 10 22H2 may not bring any consumer-facing feature updates at all. Referring to the previous practice, Microsoft is likely to use it as a small update, and it only needs to be automatically switched to 22H2 after an update enables the package, like several previous “feature updates”.