Hello everyone! I hope to be posting in the correct place, if not please tell me and I’ll delete this. I have a W11 VM on my EndeavourOS KDE laptop that I use because of some software I need for university that does not run under wine (LabVIEW and Keil uVision). The VM is running on virt-manager (QEMU KVM) using the virtio drivers, and it works really well (I mean, to be windows). The only problem is that today I run a windows update and… sbem, BSOD after reboot. The automatic diagnostic fails to do anything, uninstalling updates fails, of all possible recovery options the only one that does “something” is the command prompt, that I have 0 experience using. This was the first time updating since I created the VM a few weeks ago. Now my question is: is this fixable? Is there at least a way to recover my files, perhaps using the cmd? Thanks in advance to everyone!

EDIT: I managed to get my files back by adding a new CDROM device in the VM with a live xubuntu iso. Then from Windows recovery shit reboot into BIOS and select that device to boot from (in my case CDROM 3), then navigate to the Users/thenameoftheuser folder and backup on a USB or something all the data you need. I’ll try now to fix the windows installation without fearing the loss of my data… Lesson learned, never trust windows neither inside a VM, always better to keep important data in a separate disk (like shared memory) so that in case of VM failure they are safe in a different place
thanks to everyone!!! marking this as solved as my data are safe now, I’ll update if I’ll achieve to fix windows (perhaps by reinstalling)

  • 0x4E4F@infosec.pub
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    It may be just file corruption. Try running chdsk.exe /f C: in the command prompt. If that doesn’t work, try dism.exe /online /cleanup-image /restorehealth. Keep your virtual NIC online for the second command, it may try to download updates from MS if local files are corrupt and the WinSxS backups are corrupt as well.

    • tubbadu@lemmy.kde.socialOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thanks for the answer! The first command says chdks.exe is not recognized as an internal oe external command, and the second commands says Error: 87 cleanup-image option is unknown

      • 0x4E4F@infosec.pub
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Sorry, chkdsk.exe /f C:… it was late, I was tired 🤷.

        Error: 87 cleanup-image option is unknown

        Try it without the cleanup-image switch.

        • tubbadu@lemmy.kde.socialOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          It says “cannot open volume for direct access” :(

          Running the second command without cleanup-image flag says the same thing for restorehealth, and running without it too well, has no options after /online so fails

          Thank you very much for your time!

          • 0x4E4F@infosec.pub
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 year ago

            The prompt doesn’t run as admin. Try this command, should open up a second command prompt as admin: runas /username:{AdminUsername} cmd.