BitLocker Recovery Mode after Restart

**Describe the issue**
Windows 11 ARM Virtual Machine. Because of organization compliance policies the drive is BitLockered. Every time when restarting the VM the VM goes into BitLocker recovery mode.

**Configuration**
* UTM Version: Version 4.6.5 (108)
* macOS Version: Sequoia 15.1 (24B2083)
* Mac Chip (Intel, M1, ...): M4 Pro

**Crash log**
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to `Crash Reports`, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-\*. Right click and choose `Reveal in Finder`. Attach the report here.
[UTM-2025-08-25-155208.ips.zip](https://github.com/user-attachments/files/22004749/UTM-2025-08-25-155208.ips.zip)

**Debug log**
For all issues related to running a VM, _including_ crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the `QEMU` page is `Debug Log`. Turn it on and save the VM. After you experience the issue, open the VM settings again and select `Export Log...` and attach it here. --> Export Debug Log is greyed out, option is enabled.

**Upload VM**
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

Start with the VM settings QEMU page and the attached crash log, then try to reproduce the BitLocker recovery state after restarting the Windows 11 ARM VM. Inspect the exported Debug Log if it becomes available and compare the VM's config.plist; done means identifying a reproducible cause and confirming that restart no longer triggers recovery.

Written by the indexing model from the issue text.