Microsoft has provided a Windows 10 update in the release preview channel that is supposed to iron out some errors. It can already be switched to 22H2.
Microsoft’s recent release preview -The Windows 10 update provided by Chanel contains references to an upcoming feature update to Windows 10 22H2. It also fixes some bugs and adds new security features.
Actually, everything about the update is ordinary. Microsoft also provides a blog post with the changes. As a result, the update from the release preview channel with the knowledgebase entry KB5014666 raises the Windows version to Windows 10 21H2 Build 19044.1806.
Normal update at first glance
There were also some improvements from the update for Windows 11 in the most recent Windows 11 update preview. To improve security audits, for example, Windows Remote Management (WinRM) now logs the IP addresses for more events. One of the exclusive Windows 10 changes is that Microsoft now supports the Internet Print Protocol (IPP) not only for network printers, but also for those that search via USB connection. In addition, the print can be protected against unauthorized access by entering a PIN using IPP or Universal Printing. The linked blog post lists several other small improvements.
On closer inspection, however, there are eight .mum files in the Windows directory for the update packages that already have 22H2 as part of their name. These can be installed with the dism command.
The %windir%servicingPackages directory contains the .mum packages
Microsoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1806.mum< br>Microsoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
Microsoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~de -DE~10.0.19041.1806.mum
Microsoft-Windows-Product-Data-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
Microsoft-Windows-UpdateTargeting-ClientOS-22h2- EKB-Package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1806.mum
Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
Microsoft-Windows -UpdateTargeting-ClientOS-22h2-EKB-Wrapp er-Package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1806.mum
Microsoft-Windows-UpdateTargeting-ClientOS-22h2-EKB-Wrapper-Package~31bf3856ad364e35~amd64~~10.0.19041.1806.mum
Into the future
After opening an administrative command line and changing to the directory using cd %windir%servicingPackages, calling dism /online /add-package /packagepath:<package name> the packages, in this specific example:
dism /online /add-package /packagepath:Microsoft-Windows-Product-Data-22h2-EKB-Package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1806 .mum
After administrative users have gone through all eight files, Windows is already showing itself as Windows 10 22H2 Build 19045.1806.
So far, however, nothing else has changed. No new functions are available, after searching in Windows Update there are no further updates. It is therefore merely proof that the 22H2 update can also be expected for Windows 10 in autumn.
Up to now, the import of the 22H2 packages has had no further side effects. However, if upcoming updates are no longer offered or cannot be installed, users can easily uninstall the packages again. All you need to do is change the above dism call to dism /online /remove-package /packagepath:<package name>, for all eight packages.
