Microsoft reports that some 32-bit applications are affected by recurring errors when saving and copying files across multiple versions of Windows (especially when copying to network shares).
See also: Malicious Windows kernel drivers used in BlackCat ransomware attacks
The intermittent issue only affects applications that are aware of large addresses and also use the CopyFile API on Windows 11 21H2 and 22H2 (after installing KB5023774 or later released updates) or Windows 10 21H2 and 22H2 (after installing KB5023773 or later updates).
According to Redmond, there have been no reports that the file copy functionality of File Explorer is affected, however, the CopyFile API used in certain applications may be impacted.
Microsoft Office applications , such as Word and Excel, are only vulnerable to this issue when using 32-bit versions , with affected users potentially receiving “Document not saved” error messages .
This known issue is unlikely to occur for consumers using Windows devices in personal or unmanaged commercial settings.
Suggestion: Windows 11: New test build brings new features
The latest version of Windows 11 is still awaiting a fix
From all affected versions, Microsoft has not yet addressed the copy and file‑saving failures in the latest version, Windows 11, version 22H2.
However, the company says that affected customers can work around the issue by saving or re-copying files until a fix is ready.
Microsoft has already fixed the issue in versions 10 and 11 21H2 via Known Issue Rollback (KIR), a Windows feature designed to roll back problematic non-security fixes pushed through Windows Update.
Windows administrators should install and configure a KIR Group Policy on all affected enterprise-managed devices to resolve these file transfer and storage issues.
You can download the Group Policies by clicking the links below:
- KB5023774 Known Issue Rollback — Windows 11, version 21H2
- KB5023773 Known Issue Rollback — Windows 10 21H2/22H2
After installation, you will find the Group Policy under Computer Configuration -> Administrative Templates. To deploy the known issue rollback, you need to go to Local Computer Policy or Domain Policy on domain controller using the Group Policy Editor to select the version you want to target.
For more information, you can visit the Microsoft.
Read also: Windows admins can sign up for email alerts of "known issues"
source of information:bleepingcomputer.com
