Then, silence. The cursor blinked once, twice. A pause. Then, the dreaded blue screen flickered for a microsecond, and the machine rebooted.
The console scrolled. Copying... Done. Verifying... Done. Launching... exit codes windows
Elias knew this. He had written the wrapper script himself. He opened the script file, deploy.ps1 , and scrolled to the line that was causing the reboot. Then, silence
These are STILL_ACTIVE (thread) and STATUS_PENDING (process). Seeing them from GetExitCodeProcess means you called it before the process actually exited. This is a classic race. Then, the dreaded blue screen flickered for a
The legacy_setup.exe was a standard Windows Installer package (MSI) wrapper. Somewhere in its internal logic, it was checking for a driver update, realizing it couldn't replace the file while it was running, and returning 3010 to tell the caller, "Hey, do a reboot when you're ready."
Check against Win32 error codes: