Hello everybody,

Recently one of my vm's had windows update and i accidentally shut down system via unraid manager before updates were installed correctly.
Now every time i turn on vm im presented with repair & trouble shoot screen but none of the options work.
Example "Repair startup", " Roll previous build" or cmd commands to uninstall last updates. Last should definitely help.

Previously i found forum post which suggest change boot order by editing xml but that seems wont work for me.

If boot order was under control i could boot into windows installation .iso and from there fix my problem (repair installation without losing settings/data)

Any ideas how to change boot order of vm?

Edited February 22, 20215 yr by GoogleGonnaSaveUs

Thank you community, your help helped me a lot
Watching ar .xml file and crying helped me the most.
So solution at this problem is :
1. STEP. watch at xml file i have

<disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disk2/Vdisks/CatBox/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-TOSHIBA_HDWK105_18GTPN92T'/>
      <target dev='hdd' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows_10_LTSB_2016_version_en-US.1607.14393.2312_updated_june_2018_x64.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>

 2. STEP. After crying a bit create boot order you want by placing <boot order = 'n' /> where n is your boot order number

<disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/disk2/Vdisks/CatBox/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='3'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-TOSHIBA_HDWK105_18GTPN92T'/>
      <target dev='hdd' bus='virtio'/>
      <boot order='2'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows_10_LTSB_2016_version_en-US.1607.14393.2312_updated_june_2018_x64.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>

3.STEP. Boot into windows, hit install and load driver from virtio-win-0.1.160-1.iso  \viostor\w10\amd64 (to help OS to see hard drives)
4.STEP. Find all disk attached to vm by typing in cmd "wmic logicaldisk get name"
5.STEP. Type dir [disk letter from list]: until you see windows directory. Change dir to this disk
6.STEP. Run command "chkdsk [disk letter from list where is your Windows]: /f /r"
7.STEP. Shut down system and change boot order as shown in 1 STEP
8.STEP. Hopefully boot into OS

Edited April 23, 20215 yr by GoogleGonnaSaveUs