Driver Package empty so why does C:\Drivers have 120 folders in it?

[glen8]

Hi all,

 

Strange one....

 

I have purposly created an empty driver package to test out a theory. In my TS I only have apply driver package which is the empty one.

 

During the windows install I get the error 0x80004005 (this is why I am testing out my theory) which means the driver catalog is too big. Strange as the driver package is empty....anyway, pressing F8 and checking the C:\DRIVERS folder shows up 120 folders containing loads of drivers for various models of machines.

 

How can this be? where is it getting all those drivers from. Surely C:\DRIVERS should be empty.

 

Thanks!!

[jeaostro]

Hello

 

Isn't C:\drivers a vendor driver folder?

SCCM does not create a c:\drivers where it downloads all the drivers from the driver package buy default?

 

Does this also happen if you format the drive, then test the deployment? DO you use the auto apply driver step in the task?

 

Hi all,

 

Strange one....

 

I have purposly created an empty driver package to test out a theory. In my TS I only have apply driver package which is the empty one.

 

During the windows install I get the error 0x80004005 (this is why I am testing out my theory) which means the driver catalog is too big. Strange as the driver package is empty....anyway, pressing F8 and checking the C:\DRIVERS folder shows up 120 folders containing loads of drivers for various models of machines.

 

How can this be? where is it getting all those drivers from. Surely C:\DRIVERS should be empty.

 

Thanks!!