Windows 2022 Storage Controlllers

[NDVZB]

New to  essentials/mprpheus  and  trying to  install Windows 2022 on this platform,

Ive created the VM instance, ( ensured Attach VirtIO Drivers is enabled on the advanced options) and attached the Windows 2022 ISO

However on statup of the VM on the  WIndows Install its unable to find the controller drivers ( the virtio iso is mounted , and I can browse

to the relevant  drivers) but Windows does not pick the controller up.   Ive uploaded the latest set of windows drivers virtio-win-0.1.285

and mounted this - but the same issue -     am I missing somethign basic here? i would expect the scsi pass through drivers to be picked up 

[Manuel Boosch]

I've used 

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.271-1/virtio-win-0.1.271.iso

and it worked. did not try the latest driver yet. w2022 installation found the required driver directly when attaching ver 0.1.271. i have no screenshot what driver was shown during installation. but inside w2022 guest OS it looks like this afterwards:

[dccolpitts]

The Windows .iso image's boot.wim would not have the Virtio drivers in it by default (unless you manually mounted the boot.wim and injected with dism ahead of time).  You need to select "Load driver" at the disk page and pick the drivers in the UI, or you can hit SHIFT + F10, and use the following two commands to load the driver in WinPE

1. drvload PATH:\TO\WIN2022_VIRTIO_DRIVERS\amd64\2k22\vioscsi.inf
2. drvload PATH:\TO\WIN2022_VIRTIO_DRIVERS\amd64\2k22\viostor.inf

I don't remember the order you have to load them in right off the top of my head.

Then you should be able to see the drive.  Keep in mind that if you install Windows off that same .iso image, you may still need to inject the Virtio driver into Windows after the install before it boots for the first time (if you get a Stop 0x7b on first boot, then the drivers are not present).  My blog (here) explains how to do that for an existing VM you are going to migrate.  The steps are the same for a new VM too.  Use dism to inject the drivers into the image so it can boot.

dcc

[NDVZB]

agree Windows 2022 does not have the Virtio drivers in it by default -   by  ensuring Attach VirtIO Drivers is enabled on the advanced options, then a   CD drive with all the relvant driver gets picked up, however none of these appear to be picked  by windows  via the UI  when selecting load driver, " no new devices were found........." ( irresepctive  of which folder i point it to )

on winpe, vioscsi.inf loads successfully but viostor.inf errors with unable to unable to load viostor.inf driver 0x800070103 - which indicates the driver is already installed or an older version of the driver.

i may just try and slipstream the drivers into the  Windows ISO and see what happens

[dccolpitts]

Yeah - that's what I do by default anyways.  I always inject the VMware drivers, and now I also inject the Virtio drivers too in both boot.wim and install.wim on all new media once I download it from the volume licensing portal.

I assume you know how to mount the .wim and use dism to inject the drivers?  My experience is that about 3/4 of the time, unmounting fails because Windows Explorer hooks open files within the mount.  Usually when I build / update .wim files, I do it in a dedicated Windows VM and before I start the process, I do it all from a command prompt and before starting I use pskill64 to end Explorer (pskill64 explorer).  And then when I'm done, I just restart explorer with "explorer".

dcc

[NDVZB]

got there in the end

noticed in the library viritual images, that the Windows 2022 ISO  was uploaded, but the size was " unknown"

so I removed this, and re added it, and the size  of the ISO then appeared as it should

attached the  windows  iso once again into a blank VM , and hey presto  Windows was able to browse and find the relevant controller drivers from the attached virtio driver ISO  and the disk then become available for install