Tranquil IT Forum

Hello everyone,

After deploying via WADS, the driver package applied to the machine is not installed.
A .cab file corresponding to the selected package is present locally in c:\installdir\drivers, but the Device Manager indicates that none of these drivers have been installed.

I haven't found a WADS log file; does one exist? If so, how do I enable it?

Thank you in advance for any answers you can provide.

Hello,

the Windows installer expects to have INF files, I think.

In your case, try extracting the .cab file (with 7-Zip, for example).

Then, resend the driver bundle with the extracted folder.

That should work better.

The driver system in WADs uses this:

https://learn.microsoft.com/fr-fr/windo ... redentials.

So, the path given in the driver bundle will be given as it has this directive.

Okay, so the INF files are sent one by one locally to this folder?
I thought the package was sent to the client via this CAB archive, which is then extracted...
Thanks for the answer!
Locally, the log folder is empty; is there a way to enable logging for WADs?

sterobo wrote: ↑Jul 24, 2025 - 4:50 PM Okay, so the INF files are sent one by one locally to this folder?

They are all downloaded one by one into this folder, yes

sterobo wrote: ↑Jul 24, 2025 - 4:50 PM I thought the package was sent to the client via this cab archive which is then decompressed...
Thanks for the reply!

That said, this could be improved. We could decompress it before sending it to the Wapt server directly from the interface. I'll make a note of that.

In fact, the log data is retrieved via the status column in WADS.
The Windows installation logs are not uploaded; they remain in the standard Windows folder

Hi Steven,

actually, quite a few files are shared between the different models, so unzipping the driver packages allows for deduplication at the server level. Also, depending on the manufacturer, it's not uncommon to have to add the contents of several CAB/ZIP files to get everything needed for the machine.

Regards,

Denis

Thanks for the replies!
I completely agree about deduplication; I just saw the .cab file locally and assumed it worked that way.
It's a shame about the logs; the status field isn't very verbose.
Thanks again for your help.

Hi Steven,

regarding the logs, on the deployed machine you can right-click and choose "copy status history" and paste it into Notepad++. It's not very user-friendly, we'll look into improving that.

Denis