Handle MSI reboot-required exit codes as success in JdkInstaller

[Copilot]

msiexec returns non-zero codes 3010 and 1641 to indicate successful installation with a pending reboot — previously these were incorrectly treated as failures and threw an exception.

Changes

• JdkInstaller.RunPlatformInstaller: detect Windows MSI reboot-required exit codes before the failure check
  • Exit codes 3010 (success, reboot required) and 1641 (success, restart initiated) are treated as success on Windows
  • A TraceLevel.Warning is logged when a reboot is needed
  • Non-zero codes that are not reboot signals still throw InvalidOperationException

var rebootRequired = OS.IsWindows && (exitCode == 3010 || exitCode == 1641);

if (exitCode != 0 && !rebootRequired) {
    var errorOutput = stderr.ToString ();
    logger (TraceLevel.Error, $"Installer failed (exit code {exitCode}): {errorOutput}");
    throw new InvalidOperationException ($"Platform installer failed with exit code {exitCode}: {errorOutput}");
}

if (rebootRequired) {
    logger (TraceLevel.Warning, $"Installer completed successfully but a reboot is required (exit code {exitCode}).");
}

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.