- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 297
- Reaction score
- 7
Anyone else hit a wall with DX11 ImGui overlays on the latest 24H2 build? I'm running into a consistent blackscreen when injecting via mmap or LoadLibrary into a legit process. Works fine as a standalone exe, and no issues on Win10 or 23H2.
Technical Breakdown:
Has anyone else mapped their overlay on 24H2 and encountered this blackscreen, or am I looking at a new display state verification check?
Technical Breakdown:
- Target: DX11 hooks inside a target process.
- Current method: Standard mmap injection.
- OS Behavior: 24H2 seems to be handling the swapchain or the presentation flow differently once the overlay is injected, resulting in a black render target rather than the overlay.
- Observation: Rendering is functional as a standalone executable, suggesting the hook logic itself isn't broken, but the context of the injection on 24H2 is causing a conflict with the display subsystem or the hooked context.
I've checked my swapchain pointers and the device context validity post-injection. It seems 24H2 might be more aggressive with how it monitors the window messaging or the device states when the process is being managed via standard injection hooks. If you've been reversing the 24H2 kernel/user-mode display changes, let me know if there's a specific flag I'm missing.
Has anyone else mapped their overlay on 24H2 and encountered this blackscreen, or am I looking at a new display state verification check?