Don't know why but my Windows VM I've used for almost a decade has shit the bed. I updated my packages for the first time in a few months a couple days ago and apparently my VM was so old QEMU told me the architecture was no longer going to be supported. I updated the config and got it to run again, but now I can't use it for longer than 10 minutes without it freezing. When I go to run it afterwards, it tells me that it can't access the ISO file.
Error starting domain: internal error: process exited while connecting to monitor: 2025-07-13T00:53:34.756281Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/dev/windoze/W10.img","node-name":"libvirt-1-storage","read-only":false}: Could not open '/dev/windoze/W10.img': Read-only file system

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
callback(asyncjob, *args, **kwargs)
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 107, in tmpcb
callback(*args, **kwargs)
~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1384, in startup
self._backend.create()
~~~~~~~~~~~~~~~~~~~~^^
File "/usr/lib/python3.13/site-packages/libvirt.py", line 1390, in create
raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-07-13T00:53:34.756281Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/dev/windoze/W10.img","node-name":"libvirt-1-storage","read-only":false}: Could not open '/dev/windoze/W10.img': Read-only file system


Downgrading is tempting, but as I'm not seeing others report similar I feel I need to bite the bullet. Hard to troubleshoot since I must cold boot to "unlock" the image file every time.