How to add the Windows HDD controller drivers [SATA, SCSI, VirtIO - whatever] to the Win10 .iso file?

J

jmar83

Active Member
Nov 26, 2015
87
0
26
41
CH
www.cannabislegal.xyz
Hi there

a.) I used the Windows USB Stick installer tool from Microsoft - then i used the option to save a .iso file instead of writing an USB stick

b.) Then, i uploaded that .iso file to a webserver via USB

c.) Then i downloaded that .iso file von https location via "wget" on Proxmox and saved it on /usr/lib/vz/.... (the default location for .iso installer images)

d.) Then i saw that i need some additional [virtual] hdd/ssd controller drivers

QUESTION: How to add that drivers to the .iso file WITHOUT to destroy the boot sector / ability to boot on that .iso file? I don't have good experiences with editing bootable .iso files (at least in the past!!) - because it often will "destroy" the invisible (-> visible not as a file) boot sector...

Thank you very much for your feedbacks.
 
Maybe another way to reach my goal in a more simple way: How to add a 2nd virtual CD/DVD-ROM to a Proxmox VM? Then i can select the drivers from the 2nd drive at the Windows 10 setup...
 
Well, just add it...
1637240678786.png
 
It worked like a charm - with some special * settings: Firstly, the machine was frozen at 82% installation progress. After 15 min., i stopped it.

After a few minutes of thinking, i decided to change some HDD/SSD/CD/DVD controller settings.

HDD/SSD: VirtIO SCSI -> VirtIO SCSI single
CD/DVD: IDE -> SATA

Then, the problem was gone.

* I don't know what the reason is. Maybe that behavior is due to the bullseye-backports kernel i upgraded to - instead of original proxmox kernel. The original Proxmox kernel was not compatible to our HP ProLiant ML360 Gen 9 server... over the night, all mountpoints were gone.

(Now, with the "5.14.0-0.bpo.2-amd64" bullseye-backports kernel from debian.org, the VM host works since almost one week without any problems. Maybe a "hack", but it seems at least to work ;-))

And, after the installation, the RedHat VirtIO Network Adapter made a lil bit of stress - Code 56 in Windows device mangers. Then i saw one device more with warning symbol (due to missing driver) and Google told me (by device and manfactor id) that's a "Balloon" device.

After installing the drivers for that "Balloon" device, i was able to re-install the RedHat VirtIO Network Adapter without any problems.

(If there are any other users with same or similar issues... )
 
You must log in or register to reply here.
Top Bottom