Will inpoutx64.dll work after April 2026 Windows 11 update?

[GeniusPilot2016]

With the Windows 11 update rolling out in April 2026, Microsoft will start treating cross-signed drivers as untrusted. This raises concerns about the continued compatibility of inpoutx64.dll, which relies on such drivers for its operation.

Update:

• The fixed .sys form of InpOutX64 is VeriSign signed.
• The implications for the .dll form are uncertain; it may or may not be affected due to its delivery as a DLL rather than a direct driver, and confirmation is needed once the update ships.
• Forum discussions of InpOutx64 is still active (posts from just days ago), but there aren't any definitive developer updates on new driver signing policy compatibility.
• The PawnIO is confirmed that it's unaffected from that Windows 11 update that'll be rolled up about April 14, 2026 [it's properly signed with both individual (namazso.eu) and Microsoft Hardware Compatibility Publisher (WHCP) signatures].

Custom Made CI Test Result (April 14, 2026):

• The attached image below shows results from a custom made 3-in-1 CI Checker program, which is derived from PowerShell scripts in FAQ section in this article and added PIT read and write test, is tested on Windows 11 25H2 (Build 26200.8246, which is April 2026 update) with inpoutx64.sys present.
• The system is running in Evaluation (Audit) Mode, and inpoutx64.sys is found active without any audit or enforcement events logged for the driver.
• Code Integrity logs show no enforcement actions, and the driver handle remains open during PIT read/write operations, with successful I/O and no indication of blocking or I/O enforcement.
• Notably, after 3 days since the April 2026 update release, the custom made CI checker tool is still not reporting any log activity (including audit or enforcement events) regarding inpoutx64.sys. This suggests that, for now, the driver continues to operate without indication of being impacted by the new policies.
• Update (1 Week After Release):
  • It has now been a week since the Windows 11 April 2026 update was released. inpoutx64.dll is still working normally, and the custom made CI checker tool still does not list any audit or blocking event related to inpoutx64.sys. No enforcement or blocking has been observed so far.
• Conclusion: At least in audit mode, inpoutx64.sys continues to function without any indication of impending enforcement.

New Update (Enforcement Mode, May 2026):

• My custom made CI checker tool now reports that the system is in Enforcement Mode (no longer just Audit/Evaluation Mode). The new version of my CI checker also tracks accumulated uptime and reboot count, which are increasing as expected and are not being reset.
• Importantly, even in enforcement mode with the increased uptime/reboot tracking features, the filtered code integrity event list remains empty—there are no 3076/3077 enforcement or audit events logged regarding inpoutx64.sys. Driver presence and handle status remain normal, and the PIT channel read/write I/O test continues to show successful hardware access.
• Each CI checker step now includes additional descriptive explanations and metrics (uptime and reboot count aggregation) for clarity and repeatability.
• Summary: Despite the system policy now running in full enforcement mode, there are still no event log entries indicating that inpoutx64.sys is being blocked or subject to I/O enforcement by Windows. The driver remains functional based on all measurable criteria so far.

Status:

• In progress: As a precaution, a custom PawnIO module is being written to control the system speaker with only allowed values. This module will be tested and steps will be taken to sign it to work it in signed mode of PawnIO.
• @namazso has been assigned to oversee this precautionary migration and implementation.
• I'm running the CI checker program every day and will continue to run it for a few more days to monitor whether any audit or enforcement events appear. Currently, there are no logs indicating that inpoutx64.sys is being blocked, but I'm keeping a close watch as more time passes after the update release.
• The PawnIO-based solution remains available as a backup method for now.

Action Point:

• @namazso, please prepare a migration or investigation regarding the use of your PawnIO library as a potential alternative if inpoutx64.dll becomes nonfunctional or blocked after the Windows 11 April 2026 update.

Question:
Will inpoutx64.dll keep working with NeoBleeper after the update, or will it be blocked due to the new driver signing policies?

Context:
Many hardware interfaces and legacy sensor input solutions (including system speaker) depend on inpoutx64.dll for low-level port access. This is commonly addressed via cross-signed kernel-mode drivers, which could now be flagged as untrusted by Windows 11.

Expected Outcome:

• Clarify if inpoutx64.dll will still work as intended on Windows 11 from April 2026 onwards, despite it's a library.
• If not, suggest mitigation options or alternative solutions.

References:

• Advancing Windows driver security: Removing trust for the cross-signed driver program

---

This is a potential blocker for users planning future deployments. Any insights, tests, or updates on this topic would be valuable!