Microsoft just released a new Windows 10 cumulative update, obviously included in the August 2022 Patch Tuesday rollout, so the focus is clearly on security improvements.

The new cumulative update for Windows 10 version 21H2, which is the most recent version of the operating-system, is KB5016616, also it obviously has the same improvements as for Windows 10 version 21H1 - these two releases share a similar codebase, so Microsoft ships exactly the same update for of these.

Given it's an area Tuesday release, KB5016616 is first of all supposed to address security vulnerabilities within the operating system.

But simultaneously, additionally, it comes with three more fixes, including for printing and the Language Bar.

Microsoft lists the next improvements as part of cumulative update KB5016616:

Addresses an element that affects the printing of files you submit to a printer.
Addresses a known issue that may avoid the Input Indicator and Language Bar from displaying in the notification area. This problem affects devices which have several language installed.
Addresses security issues for your Windows based pc.

There are also several known issues in this cumulative update, and one of these only has recently been acknowledged by Microsoft. Also affecting Windows 11, this bug impacts XPS Viewer, therefore it only affects the computers where this app has been manually installed.

"After installing this update, XPS Viewer may be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files," Microsoft says.

"When encountering this issue, you might get an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and also have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer isn't closed it could reach up to 2.5GB of memory usage before closing unexpectedly."

A treatment for this issue is already in the works, Microsoft says.