Temporarily hold Windows 11 26H2 deployment for devices that depend on .wpd files, complete the rollback test already in progress, and use WordPerfect to export working copies until Microsoft or Corel/Alludo confirms a permanent fix.
Establish the affected update boundary
The current evidence shows correlation, but not yet confirmed causation:
- Build 26300.9974 is delivered by the November 10 security update KB5132061.^1^
- Build 26300.9911 is the November 26H2 hotpatch build.^2^
- Microsoft’s 26H2 release-health page does not currently list
.wpdor WordPerfect import failures as a known issue.^3^ - Separate users have reported WordPerfect macro failures after KB5132061, resolved by uninstalling it, but that is not the same symptom and does not establish the cause of this
.wpdissue.^4^
Since the rollback is already underway:
- Preserve an original
.wpdfile and its hash; test only copies. - Record the installed KBs before rollback:
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 15 HotFixID, InstalledOn - After rollback and restart, test the same copied file in:
- WordPerfect
- Microsoft Word using File → Open → Browse
- Record whether Word imports it correctly again.
- If practical, reinstall the implicated update on one isolated test device and repeat once. Do not reinstall merely to reproduce the issue on a production user’s device.
Removal is temporary containment, not a confirmed permanent resolution. KB5132061 is a security update, so leaving it removed across the fleet creates security exposure. Microsoft documents the UI path as Settings → Windows Update → Update history → Uninstall updates, although some updates cannot be removed.^5^
Fleet workaround
Until the affected layer is identified:
- Use your existing authorized endpoint-management process to stop approving 26H2 for additional WordPerfect-dependent deployment rings.
- Do not broadly uninstall security updates based only on the current two-device comparison.
- Keep one representative 25H2 device available for conversion and validation.
- Open each
.wpdin WordPerfect, then—if that installed WordPerfect version offers it—save a separate copy as.docx,.doc, or.rtf. - Preserve the original
.wpdand compare formatting, tables, fields, embedded objects, and pagination in the converted copy before production use. - Do not assume DOCX preserves WordPerfect macros or application-specific automation; handle those separately in WordPerfect.
Notepad displaying encoded characters is expected for a binary document format. It does not independently demonstrate system-wide corruption. The meaningful regression is that an application which previously imported the same file no longer does so, while WordPerfect still opens it.
Changing Word’s text encoding is not an appropriate workaround for a binary .wpd document; Word’s encoding selection applies when treating input as encoded text.^6^
Report and escalate
For an Enterprise deployment, create both cases:
- Microsoft Support for Business
- Include affected builds 26300.9911 and 26300.9974.
- Include the working 25H2 build 26200.8655.
- Attach installed-KB inventories, Microsoft 365/Word version, WordPerfect version, rollback A/B results, and a non-confidential sample
.wpd. - State whether the device is physical or Windows 365 and how updates are managed.
- Official Corel/Alludo WordPerfect support
- Ask whether the applicable WordPerfect release or import converter requires an update for Windows 11 26H2.
- Include the same sample and before/after results.
Also submit a single organization-wide Feedback Hub report with diagnostics: press Windows+F, choose Report a problem, search for an existing matching report, and link/upvote it or create a new bug. Feedback Hub accepts screenshots, files, and reproduction recordings, but it is for reporting and tracking—not immediate enterprise support.^7^
References
- November 10, 2026—KB5132061 (OS Builds 26300.9974, 26200.9974 and 26100.9974) | Microsoft Support
- Release notes for hotpatch updates on Windows 11 Enterprise version 26H2 | Microsoft Support
- Windows 11, version 26H2 known issues and notifications | Microsoft Learn
- Windows 11 Patch KB5132061 - Microsoft Q&A
- [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/how-to-uninstall-a-windows-update#summary)
- Choose text encoding when you open and save files | Microsoft Support
- Send feedback to Microsoft with the Feedback Hub app