Unable to install drivers

[SteveO-Silicon]

We've been building a variety of windows server images (2016, 2019, 2022) for the past couple of years, but suddenly running into issues when it comes to injecting the drivers.

2016 builds fine, but 2019 and 2022 have started failing with the errors below.

We've tried various versions of virtio-win all downloaded from here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads

virtio-win-0.1.190.iso
virtio-win-0.1.229.iso
virtio-win-0.1.240.iso
virtio-win-0.1.248.iso

relevant configuration:
[drivers]

The path to the ISO file containing the VirtIO drivers.

virtio_iso_path=e:\catalyst\drivers\virtio-win-0.1.248.iso

The location where the VirtIO drivers are found.

For example, the location of a mounted VirtIO ISO. VirtIO versions supported >=0.1.6.x

virtio_base_path=""

The location where additional drivers that are needed for the image are located.

drivers_path=""

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Applying image
[==========================100.0%==========================]
The operation completed successfully.
13/03/2024 9:47:12 AM - Create BCDBoot Config for Windows Server 2022 SERVERSTANDARD
13/03/2024 9:47:15 AM - Resetting BCD boot border
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.
13/03/2024 9:47:16 AM - BCDBoot config has been created.
13/03/2024 9:47:16 AM - Adding Virtual IO Drivers from ISO: e:\catalyst\drivers\virtio-win-0.1.248.iso...
13/03/2024 9:47:16 AM - Using backed up ISO for safe dismount.
13/03/2024 9:47:19 AM - Adding drivers from G:
13/03/2024 9:47:19 AM - Adding Virtual IO Drivers: G:...
13/03/2024 9:47:19 AM - Getting Virtual IO Drivers: G:...
13/03/2024 9:47:19 AM - Finished to get IO Drivers.
13/03/2024 9:47:19 AM - Adding drivers from "G:\balloon\2k19\AMD64" to image "F:"
WARNING: Dism failed to add drivers from: G:\balloon\2k19\AMD64
WARNING: Dism failed to add drivers from: G:\balloon\2k19\AMD64
WARNING: Dism failed to add drivers from: G:\balloon\2k19\AMD64
13/03/2024 9:47:24 AM - Dism failed to add drivers from: G:\balloon\2k19\AMD64
Dism failed to add drivers from: G:\balloon\2k19\AMD64
At E:\catalyst\windows-openstack-imaging-tools\WinImageBuilder.psm1:641 char:13

•         throw "Dism failed to add drivers from: $driversPath"
  

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (Dism failed to ...loon\2k19\AMD64:String) [], RuntimeException
  • FullyQualifiedErrorId : Dism failed to add drivers from: G:\balloon\2k19\AMD64

[ader1990]

Hello, sometimes it is worth to try a full Windows update on the host and a reboot.

Can you please provide the host OS version, to try to reproduce this problem?

Thank you,
Adrian.

[SteveO-Silicon]

Win 10 22H2 is the build machine, fully updated except for KB5034441 which has known issues.
No change after applying updates and restarting unfortunately, trying multiple versions of the iso.

[ader1990]

Hello @SteveO-Silicon, I could not reproduce the issues you are seeing on none of our environments. Have you found a workaround or a fix to your issue?

Thank you.

[SteveO-Silicon]

This has been intermittent, but the last couple of monthly refreshes to our images have worked fine, not sure why. Can probably close this out for now, and we’ll revisit if it starts failing again. Thanks, Steve Steve Ofsoski Chief Information Officer Silicon Systems Ltd P: +64 4 499 4999 M: +64 21 775 965 E: ***@***.*** W: silicon.co.nz This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. From: Adrian Vladu ***@***.***> Sent: Wednesday, May 15, 2024 3:51 AM To: cloudbase/windows-imaging-tools ***@***.***> Cc: Steve Ofsoski ***@***.***>; Mention ***@***.***> Subject: Re: [cloudbase/windows-imaging-tools] Unable to install drivers (Issue #390) Hello @SteveO-Silicon<https://github.com/SteveO-Silicon>, I could not reproduce the issues you are seeing on none of our environments. Have you found a workaround or a fix to your issue? Thank you. — Reply to this email directly, view it on GitHub<#390 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BG5FPFH7IORVAUGUMLZUKZDZCIXG3AVCNFSM6AAAAABETBQ2OKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGU4DAMRYGA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>