Align runtime version banner with the 4.2.9 virtual-machine release

[Copilot]

The script already contained the 4.2.9 virtual-machine support work, but the startup banner still reported 4.2.8. That mismatch created misleading runtime metadata and made it harder to confirm the actual build in the field.

• Summary

  • Align the startup log version with the released implementation state.
  • Keep the runtime banner consistent with the script history and the virtual-machine support update already in code.

• What changed

  • Updated the logged script version in Invoke-CMApplyDriverPackage.ps1 from 4.2.8 to 4.2.9.
  • Kept the fix limited to release metadata; there were no functional behavior changes in the matching or installation logic.

• Why this matters

  • The banner is part of the operational evidence captured in troubleshooting logs.
  • Matching the version string to the actual code release prevents confusion when validating deployments or diagnosing VM-specific package selection behavior.

[Copilot]

🟢 Approval recommended

The change is a single, verified metadata/log string update that brings the startup banner into alignment with the documented 4.2.9 release history.

Pull request overview

Aligns the runtime startup banner version string with the already-shipped 4.2.9 virtual-machine support implementation so operational logs accurately reflect the deployed script version.

Changes:

• Updated the startup log entry in Invoke-CMApplyDriverPackage.ps1 to report script version 4.2.9 instead of 4.2.8.

File summaries

File	Description
Invoke-CMApplyDriverPackage.ps1	Updates the startup banner’s script version string to match the 4.2.9 release state.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.