Thank you! I’ve forgotten about system event logs entirely. When filtered on Errors only, I found these peculiar entry:
Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V.
Also this:
The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled
And also this one that talks about HvHost, which might be related to Hyper-V:
The CmService service depends on the HvHost service which failed to start because of the following error:
A device attached to the system is not functioning.
The most interesting was about Secure Mode Extensions enabled in BIOS because I’ve reset the BIOS to the defaults, as instructed by the Framework support. I’ll have to reach out to them with this new information.
Thank you, @mahe, for this suggestion. It enforces my suspicion that it wasn’t Windows 11 at fault and that something else is at play.