Project Description
Chrome launches flawlessly on my Windows 10 machines, yet on every Windows 11 device the window opens as a solid black screen and instantly becomes unresponsive. No crash dialog, no obvious error code—just a blank shell.
Because this behaviour persists even after standard clean-install routines and profile resets, I’m looking for a reverse-engineering specialist who can dig deeper than conventional troubleshooting. Your task in this first, short demo is to reproduce the failure, pinpoint the root cause at the system or binary level, and supply a verifiable fix. Registry hooks, DLL injection issues, graphics pipeline conflicts, sandbox changes—whatever the culprit is, I need it identified, documented, and resolved so Chrome starts normally on Windows 11.
You’ll likely lean on tools such as WinDbg, ProcMon, IDA, Ghidra, or Chromium’s own symbol server, but the exact toolkit is up to you as long as the outcome meets the criteria below.
Deliverables for this demo:
• Technical report explaining the underlying cause (call stack traces, offending module, or mis-configuration).
• A repeatable fix: this could be a patched DLL, registry/script change, command-line flag set, or detailed step-by-step instructions.
• Confirmation that the same machines now launch Chrome without the black-screen hang.
If this demo is successful, I have ongoing, related Windows-internals work waiting. Let’s start by getting Chrome to open properly on Windows 11.