Memory leak in ctfmon.exe not scary anymore: Microsoft releases cumulative update

Carding 4 Carders

Professional
Messages
2,731
Reputation
13
Reaction score
1,375
Points
113
Is it worth installing a fix, given all its shortcomings?

Microsoft has released an optional cumulative update KB5031445 for Windows 10 22H2. It contains 9 fixes, including fixing a memory leak in "ctfmon.exe", about real attacks using which we recently reported .

Update KB5031445 is part of Microsoft's "optional pre-release updates" plan. These updates are usually released on the fourth Tuesday of each month. They allow Windows administrators to test out future fixes and features that will appear in next month's Patch Tuesday updates.

Windows users can install this update manually through the "Update and Security" section in the system settings. After installing it, the Windows 10 22H2 version will update to build 19045.3636. The KB5031445 update is also available for manual download and installation from the Microsoft Update catalog .

What's new in Windows 10 Update KB5031445
Microsoft didn't add any new features in this release, but the update addresses 9 known Windows 10 issues. Three key ones:
  • fixing an issue affecting touchscreens;
  • support for daylight saving time in Syria;
  • fixing a memory leak in "ctfmon.exe".

However, the cumulative update also brings one unpleasant bug that Microsoft is already aware of: it can cause errors in BitLocker.

"Using the corrected DRIVESENCRYPTIONTYPE or SystemDrivesEncryptionType policy settings in the BitLocker Configuration Service Provider (CSP) node in Mobile Device Management (MDM) applications may not correctly display error 65000 in the 'Require Device Encryption setting for some devices in your environment," the release notes explain.

That is, when using some BitLocker settings, errors may occur in the "Require device encryption" setting. However, Microsoft previously confirmed that this is only a reporting issue, and not a BitLocker disk encryption issue. The company is working on a solution to this problem and will release it as soon as it is ready.

For a complete list of fixes, see Newsletter KB5031445.
 
Top