Product Alerts
Product Alerts provide official notifications about product-related conditions that may affect compatibility, operation, or deployment in specific environments.
These alerts are published to ensure transparency and to support timely assessment and mitigation where required.
AxProtector Compatibility with Windows Update KB5074105
Windows update KB5074105 modifies multiple Windows components, rendering a function-call obfuscation mechanism used by AxProtector for Windows incompatible. Under specific protection configurations, protected applications may fail during startup or operation.
Below you will find answers to frequently asked questions for both end users of protected software and developers providing protected applications. If your question is not covered here, please contact our technical support team.
Frequently Asked Questions
Q: My purchased, licensed software hasn't worked correctly since the last Windows update. What can I do?
A: First, check if update KB5074105 is installed on your system. If so, you can uninstall KB5074105 as an immediate measure; it's an optional update, not a security one. Still, contact the software publisher or check if they've released an updated version compatible with this Windows update.
Q: My purchased software isn't working since the last Windows update, but I don't want to uninstall KB5074105. What else can I do?
A: Either uninstall the update or wait for an updated software version from the manufacturer. There are no other solutions: no system or app setting can bypass this issue.
Q: My purchased software still runs on an old Windows 10 system. Does the error occur there too?
A: Windows Update KB5074105 applies only to Windows 11. Older operating systems don't receive these changes, so no error occurs, and no action is needed.
Frequently Asked Questions for Software Manufacturers Protecting Apps with AxProtector Windows (up to and including Version 11.70c)
Issue Diagnosis
Q: How can I determine if my software is affected?
A: To be certain, test your software thoroughly. Install Windows Update KB5074105 on a Windows 11 system, launch your software, and test functionality. If it crashes, you're likely affected. Uninstall the update and retest; it should now work without crashing.
Q: I've found protection options in a wbc file or log file. How can I check if my software is affected?
A: Look for the -caa option in the file. The following number is the sum of Advanced Protection Schemes (1, 2, 4, 8). Methods 2 and 8 trigger the issue. If the value is -caa1, -caa4, or -caa5, your software is unaffected.
Q: Based on the Advanced Protection Methods value, my software is affected. But tests with KB5074105 installed work fine. Is that possible?
A: The compatibility issue doesn't occur in every case. Wibu-Systems investigations show it only happens if your protected component's (EXE or DLL) import table includes Microsoft APIs identifiable by module names starting with "api-ms," e.g., api-ms-win-crt-runtime.dll.
Q: The encryption log shows "Warning: Static code modification does not have any effect to the current executable!". Does this mean no compatibility issue?
A: Unfortunately not. This output from the encryption process wasn't reliable; it indicates modification couldn't be applied to certain functions, but doesn't guarantee it wasn't applied at all.
Problem Resolution
Q: My software is affected by the KB5074105 compatibility issue. What can I do to provide users with a working app again?
A: Re-encrypt your software using the same AxProtector version as the original release to avoid side effects from other changes. Key difference: Use a -caa value excluding 2 and 8, e.g., -caa5. In the AxProtector GUI, uncheck Static Code Modification. Test the new version and distribute it.
If you already used AxProtector 11.70 or later, switch to 11.70d (in CodeMeter SDK 8.40d), which supports Static Code Modification and Extended Static Modification without issues.
Q: Why doesn't Wibu-Systems provide a new CodeMeter Runtime version to fix this?
A: It's not technically feasible. Changes to loading Microsoft API functions are deeply embedded in the protected app, unrelated to CodeMeter Runtime and unfixable from within the app.
Q: Is there really no way to make the protected software work at the user end without a new version?
A: Users can avoid or uninstall the optional update, restoring functionality temporarily. However, it's unclear how long before this change becomes a prerequisite for future security updates. Wibu-Systems opened Microsoft ticket 2602040050003534 requesting modification of the update changes; outcome is pending.
Miscellaneous
Q: How will Wibu-Systems prevent this in the future?
A: AxProtectors in the CodeMeter Protection Suite are transitioning to new technology. NC variants minimize binary file modifications, offloading API calls, licensing, and security checks to the CodeMeter Protection Suite Runtime (CPSRT) library, part of CodeMeter Runtime or distributable separately. This allows quick responses to incompatibilities via CPSRT updates. It simplifies third-party library swaps post-security incidents (CVEs) and eases Cyber Resilience Act (CRA) compliance. The NC variant of AxProtector Windows launches Q2 2026 in version 11.80 (CodeMeter SDK 9.00).