I restored a physical Windows Server 2022 domain controller to an isolated Hyper-V VM using Veeam Instant Recovery. It initially booted with CRITICAL_SERVICE_FAILED, but after CHKDSK and Windows repairs it starts normally, with AD DS, DNS, and Netlogon running.
The production server's C: volume is marked dirty, and CHKDSK reports corruption under Windows.old and recommends spotfix. Is the source filesystem the likely cause, and would you repair it or replace the DC?
Vexora.4d:
I'd also check whether the backup was application-consistent or only crash-consistent. That could help narrow the investigation, though it wouldn't by itself explain the stop code.