Windows 10 x32 can't find drivers on the virtio iso

Apr 27, 2023
3
1
3
Hi,

I'm trying to install Windows 10 x32 on proxmox. I've added the virtio iso as a second cdrom. When I search the virtio cd for hard drive drivers under viostor I get this error from Windows "No device drivers were found. Make sure that the installation media contains the correct drivers, then click OK"

I'm not sure what's going wrong. I don't get this error installing a VM under unraid.

Hoping someone can help!

Thanks!
 
Hi,

First of all, here is a link to the proxmox windows 10 best practices [1] in case you haven't seen it yet.

Secondly, I am guessing there is a specific reason you are choosing windows 10 x32 instead of x64? Otherwise download a new iso from Microsoft [2]. You should be able to install 32bit programs on x64 windows no problem.

If you do indeed need windows x32 for some reason, I am guessing you need to change your cpu to a 32 bit cpu (486, qemu32, kvm32). As far as i can tell, there are no 32 bit drivers in the "viostor" folder, I am guessing all the 32 bit drivers are in the "i386" folder. But as a fair warning regarding all this, I couldn't find a windows 10 x32 iso, only x64, so I can only guess.

Hope this helps


[1]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices
[2]: https://www.microsoft.com/en-us/software-download/windows10ISO
 
  • Like
Reactions: Omethe
Hi,

First of all, here is a link to the proxmox windows 10 best practices [1] in case you haven't seen it yet.

Thank you, I've looked at that document.

Secondly, I am guessing there is a specific reason you are choosing windows 10 x32 instead of x64? Otherwise download a new iso from Microsoft [2]. You should be able to install 32bit programs on x64 windows no problem.

I need to run some 16 bit software natively so unfortunately as far as I'm aware I have to use a 32 bit version of windows.

If you do indeed need windows x32 for some reason, I am guessing you need to change your cpu to a 32 bit cpu (486, qemu32, kvm32). As far as i can tell, there are no 32 bit drivers in the "viostor" folder, I am guessing all the 32 bit drivers are in the "i386" folder. But as a fair warning regarding all this, I couldn't find a windows 10 x32 iso, only x64, so I can only guess.

When you run the Windows Media Creation Tool it allows you to select between a 32 bit and 64 bit architecture. Under Win10 in viostor there is an x86 folder which I believe are 32 bit drivers.

Hope this helps

Thank you :)
 
So, I've created a windows 32 bit iso, which I had to do in a windows vm to run the media creation tool because microsoft doesn't offer a 32bit iso on their website. But hey, I got there eventually.

I've managed to get a working install of w10 32b: I got it to run with the kvm64 as well as my host processor, however not with 486, qemu32 or kvm32, so disregard what I said above.

For the harddrive, I got it to work with IDE but not SCSI; I didn't need to install any virtio drivers for the disk to be recognized, seems the needed drivers were preinstalled. And then I just installed the NetKVM and Balloon drivers (you were right, the x86 drivers were correct:) ).

From there, everything as usual. Hope it works for you
 
  • Like
Reactions: Omethe
So, I've created a windows 32 bit iso, which I had to do in a windows vm to run the media creation tool because microsoft doesn't offer a 32bit iso on their website. But hey, I got there eventually.

I've managed to get a working install of w10 32b: I got it to run with the kvm64 as well as my host processor, however not with 486, qemu32 or kvm32, so disregard what I said above.

For the harddrive, I got it to work with IDE but not SCSI; I didn't need to install any virtio drivers for the disk to be recognized, seems the needed drivers were preinstalled. And then I just installed the NetKVM and Balloon drivers (you were right, the x86 drivers were correct:) ).

From there, everything as usual. Hope it works for you
Thanks! I managed to get my hands on another 32b iso and all worked fine with host for my cpu. It's all up and running now :)
 
  • Like
Reactions: noel.