Fix Windows Server 2022 infinite reboot loop by reverting to Fedora 42#138
Draft
Fix Windows Server 2022 infinite reboot loop by reverting to Fedora 42#138
Conversation
The issue was caused by certificate trust problems with virtio-win drivers in Fedora 44. Downgrading to Fedora 42 resolves the issue as it uses virtio-win version 0.1.248-1 which has properly trusted certificates for Windows Server 2022. Co-authored-by: mnaser <435815+mnaser@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix Windows Server 2022 reboot cycle post migration
Fix Windows Server 2022 infinite reboot loop by reverting to Fedora 42
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Windows Server 2022 VMs enter an infinite reboot cycle post-migration due to virtio-win driver certificate trust failures in Fedora 44. The
smbus.infdriver installation fails with "certificate chain...not trusted by the trust provider", causing firstboot scripts to exit 249 and retry indefinitely.Root Cause
Fedora 44 ships virtio-win v0.1.285-1 (Sep 2025) with certificate chains incompatible with Windows Server 2022's default trust store. Fedora 42 ships v0.1.248-1 (Feb 2024) with properly trusted certificates.
Breaking change introduced in commit
ccdfc8f(Sept 13, 2025).Changes
fedora:44tofedora:42in both build and runtime stagesError Pattern
User verified last working image (SHA
ead70cfc9efb3163990212f48e56cb347b109cb17a869a1d1c820b1c229700fe) was built pre-Fedora 44 upgrade.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.