none
SCCM 2012 R2 SP1 - Driverpack bug? RRS feed

  • Question

  • Hello,

    we've recently installed SP1 for SCCM 2012 R2 and now I had to create a new Driverpack for HP Z440 Workstation. So I downloaded all current drivers for this Model and Import them like always to SCCM.

    First I noticed that it took ages to "Validate Driver Information". But I allready read about that so no big deal just wait. After this was finished I saw the new Import wizzard which now Lists the driver by .INF (see screenshot). I also noticed that there are many INFs for Realtek HD Audio

    I continued importing the drivers and assigned them to a new driverpack. The import process also took ages. After it has finisehd I had a look at the Driverpack and couldn't belive how huge the Driverpack is, so I also had a closer look at the driversource.

    The Driversource is about 550MB, so thats normal for one Computermodel
    The Driverpack after import has about 20GB!!!!

    SCCM creates for each .INF file a new Folder in the folder of the Driverpack and copys the whole content of the driver to it.

    Example: The sourcefolder of the Realtek HD Audio driver is about 305MB and includes over 60 .INF files. After the Import this is about 19GB. For each .INF SCCM creates a new Folder in the Driverpackfolder and copys the complete source (305MB) to it. So I have 305MB more then 60 times in my Driverpack.

    Anyone experience the same?

    Wednesday, June 17, 2015 1:41 PM

Answers

  • The fix is finally out!

    FIX: Driver package size increases in System Center 2012 Configuration Manager Service Pack 2

    https://support.microsoft.com/en-us/kb/3084586

    When you add new drivers to a driver package by using the Import New Driver wizard, the driver package files are larger than you expect.

    The content for the driver package may be duplicated multiple times. This causes the package file to be significantly larger than the package in the original source location.

    Additionally, the process to import the new drivers by using the Import New Driver wizard may take much more time than you expect.


    Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer

    Wednesday, August 12, 2015 7:22 PM

All replies

  • I've seen the same but have no explanation but do have a thread open with the product group. Will post any updates I get.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, June 17, 2015 2:37 PM
  • Meanwhile I opened a Case at Microsoft Support regarding this Problem. 

    still in process

    Also I’ve created a entry at Microsoft Connect

    https://connect.microsoft.com/ConfigurationManagervnext/Feedback/Details/1445504

    Please vote to receive more attention from Microsoft

    Tuesday, July 7, 2015 9:34 AM
  • Hi NimoEBE

    Can you give me the casenumber from Microsoft.

    I have the same problem here at my customer...And near me sit a Microsoft PFE who will be able to check the case....

    Thanks...

    Wednesday, July 8, 2015 9:18 AM
  • Hi tnau01

    the Incident number / Support ID: 115070112900387

    current Status: Microsoft said they will test it with the same audio driver I used to recerate the issue.

    Wednesday, July 8, 2015 11:34 AM
  • Any updates? :)

    http://www.blogmynog.com

    Thursday, July 9, 2015 1:40 AM
  • Hi All

    Do we have any updates on this issue

    Thx in Advance

    Regards

    Johan

    Thursday, July 9, 2015 2:30 PM
  • One idea I am getting ready to test as a workaround is creating a standard "Package" for the drivers, and running a DISM command to inject them and leave the drivers (for now) out of the driver store/driver package.

    The command will look something like this:

    X:\WIndows\System32\Dism.exe /image:C:\ /Add-Driver /Driver:(PATH) /recurse

    About to run through a test on this.  Certainly not ideal but could be viable workaround while we wait for a hotfix.

    Thursday, July 9, 2015 3:30 PM
  • I also just upped the connect report and asking my client to open a Premier case as well.

    Hoping for a quick turnaround on a hotfix.


    Thursday, July 9, 2015 3:40 PM
  • Straight from Aaron Czechowski:

    FYI, we’ve reproduced and identified the issue. I’m talking with sustained engineering about getting into a future CU, but nothing committed yet. Continuing to work through support is your best course of action right now.


    Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer

    Thursday, July 9, 2015 5:57 PM
  • Thx for the info Daniel
    Thursday, July 9, 2015 6:18 PM
  • For what its worth, I have successfully tested a workaround by creating a traditional package out of a driver set rather than importing them into the driver store, then executing a Run Command Line step in my task sequence with a query for Model in the options tab of course:

    The command is: Dism.exe /image:D:\ /Add-Driver /Driver:. /recurse



    Thursday, July 9, 2015 9:41 PM
  • It looks like Tech Preview 2 might resolve the WIN10 driver bug!

    https://technet.microsoft.com/library/dn965439.aspx?f=255&MSPPError=-2147217396

    • Improvements have been made to the process for importing drivers, including active feedback on several user interface screens, and when importing Windows 10 applicable drivers


    Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer

    Thursday, July 9, 2015 11:05 PM
  • Hallo Nimo

    Vielen Dank für die Casenummer. Leider sieht es ja noch nicht so gut aus....Bin mal gespannt was die Produktgruppe dazu sagt...

    Tuesday, July 14, 2015 7:52 AM
  • The BUG states a Status of Resolved....so I wonder how long before we see a hotfix publicly released?!?!?

    David Baur

    Wednesday, July 22, 2015 10:28 PM
  • Fingers crossed
    Thursday, July 23, 2015 1:41 PM
  • would love them to roll out an update to fix this issue. DISM workaround is ok tho.

    HughMc

    Thursday, July 30, 2015 5:35 AM
  • I published a decent work-around a couple of weeks ago:

    http://blog.configmgrftw.com/the-trouble-with-tribbles-i-mean-drivers/


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, July 30, 2015 2:25 PM
  • Thanks Jason, that works well too.

    HughMc

    Monday, August 3, 2015 11:53 PM
  • CU1 just released today: http://blogs.technet.com/b/configmgrteam/archive/2015/08/04/now-available_3a00_-cu1-for-configmgr-2012-r2-sp1-configmgr-2012-sp2.aspx

    <u5:p> </u5:p>

    From https://support.microsoft.com/en-us/kb/3074857

    <u5:p> </u5:p>

    Issues that are fixed

    Operating system deployment

    •          Windows 10 drivers do not import. Errors that resemble the following are logged in the DriverCatalog.log file:<u5:p></u5:p>

    Initializing driver digest from '\\server\Windows10-x64\{Windows10-driver}.inf'\\server\Windows10-x64\{Windows10-driver}.inf is not applicable to any supported platforms.Driver is not applicable to any supported platforms. Code 0x80070661


    Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer

    Tuesday, August 4, 2015 4:12 PM
  • Unfortunately, that's not the issue being addressed in this thread. It doesn't look like CU1 contains a fix for this issue. :-(

    Jason | http://blog.configmgrftw.com | @jasonsandys


    Tuesday, August 4, 2015 4:27 PM
  • seeing the same issue with the HP z640 windows 8.1 drivers. goes from 697MB source folder to 26.1 GB with 72 unique Realtek sound drivers clocking in at 359MB each!!  We just updated to 2012 r2 sp1 a couple weeks ago. 

    It also refuses to inject the RAID controller driver into the boot image saying it's unsigned even though it shows as signed in the console.  after selecting update DPs it checks if it's finalized, tries to inject the driver and fails.  It has no problem with the network driver, just the RAID controller.  Dism log says use /forceunsigned but there's no option to do that in sccm.  I was able to import the driver manually using /forceunsigned but it still doesn't load during PXE so the TS fails when it can't apply the OS to a non-existant drive. 

    Workaround was to go in the BIOS on each machine and change SATA and sSATA mode from RAID to AHCI.

    so the current answer is open a case with our TAM and wait? Will try Jason's PS and console combo in the meantime.

    Thursday, August 6, 2015 2:20 PM
  • I had a similar issue with the Realtek drivers for the HP Probook 11g1.  My solution was to import all of the drivers into SCCM, but did NOT add them all to a driver package.  I then selected the first driver in the list and added only that driver to my driver package.  It created one instance of that ~300MB folder containing all of the driver files, and correctly installed the sound driver in my task sequence.  This reduced my driver package size for this laptop from 36GB down to 1.3GB.
    Thursday, August 6, 2015 3:32 PM
  • New comment at Microsoft Connect. --> Have to wait for CU2 :-/ maybe post CU2 fix.

    https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1445504/driver-import-bug

    Friday, August 7, 2015 4:46 AM
  • I've heard to keep an eye out for a between-CU hotfix soon, KB3084586

    the connect link above doesn't work for me, says page could not be found.

    Friday, August 7, 2015 1:46 PM
  • Deleted
    Friday, August 7, 2015 3:16 PM
  • The fix is finally out!

    FIX: Driver package size increases in System Center 2012 Configuration Manager Service Pack 2

    https://support.microsoft.com/en-us/kb/3084586

    When you add new drivers to a driver package by using the Import New Driver wizard, the driver package files are larger than you expect.

    The content for the driver package may be duplicated multiple times. This causes the package file to be significantly larger than the package in the original source location.

    Additionally, the process to import the new drivers by using the Import New Driver wizard may take much more time than you expect.


    Daniel Ratliff | http://www.PotentEngineer.com | @PotentEngineer

    Wednesday, August 12, 2015 7:22 PM
  • Hi All

    Finally

    We have a CAS - PRI environment do we need to install this update on the CAS and PRI also or is only the CAS enough

    thx in advance

    regards

    Johan 

    Thursday, August 13, 2015 7:53 AM
  • Johan, looks to be an Admin Console update only so I would imagine it needs to be installed on any machines that have the Admin Console installed.
    Thursday, August 13, 2015 11:42 AM
  • Anyone else still seeing drastic import times? Especially on 'Validating file permissions and getting driver attributes'. I am now at over 40 minutes importing 300mb worth of drivers.

    The package size did drop though, which is the important part.

    Thursday, August 13, 2015 8:45 PM
  • Hi William

    Thanks

    I Think you are right and that the update is applicable on all systems with the admin console , but I find it strange that this is not mentioned in the KB article

    it is also still not mentioned in the "Microsoft system center configuration manger team blog"

    Regards

    Johan

    Friday, August 14, 2015 7:53 AM
  • Mike, can you try importing with Powershell and see if the issue persists?  Maybe this hotfix was a stop gap to prevent bloat but maybe not addressing all the issues with this bug.  Curious to see if others are seeing the same.
    Friday, August 14, 2015 1:35 PM
  • You're right that its not mentioned, and while you shouldn't necessarily be expected to have to look at the files changed by the hotfix to discern where to install the hotfix, if you do look there it's pretty clear that the consoles need to be updated. Also, the fact that the hotfix installer creates (or at least prompts you if you want it to create) a package to update the console is another clue here.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, August 14, 2015 2:28 PM
  • Where is your import source is relation to the site server and the SMSProvider? Are they remote or local? If remote, then that's the source of your slowness and not much that ConfigMgr can do to speed it up.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, August 14, 2015 2:29 PM
  • We are using a DFS namespace for the path, but it resides locally on the site server.  I'll attempt the PowerShell import next week just curious if others saw this as well. 
    Friday, August 14, 2015 6:16 PM
  • Well, that's actually two levels of indirection on a process that opens and closes a lot of files. Just for comparison, you should compare the time for the same package on a local UNC.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, August 14, 2015 6:44 PM
  • Just an update

    We installed the update on the CAS and Primairy sites and also on computers with the configuration manager console installed.

    We imported 300 MB on drivers (source), the driver package created was the same size , before the update the driver package was about 1,2 GB with the same drivers imported. 

    Second  the step  'Validating file permissions and getting driver attributes" is indeed slow it was in our environment for the 300 MB about 7 minutes

    Hope this will help someone

    Regards

    Johan

    Monday, August 17, 2015 4:07 PM
  • So after a powershell import it still took about 35-40 minutes to finish, so both methods took about the same amount of time. 

    I also tried a local UNC path and got the same results.

    Monday, August 17, 2015 6:50 PM
  • Microsoft has released a Hotfix for this now

    https://support.microsoft.com/en-us/kb/3084586


    David Baur

    • Proposed as answer by David Baur Jr Wednesday, August 19, 2015 4:04 AM
    Wednesday, August 19, 2015 4:04 AM
  • Microsoft has released a Hotfix for this now

    https://support.microsoft.com/en-us/kb/3084586



    That was already mentioned by Daniel one week ago (see above).

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, August 19, 2015 5:51 AM
    Moderator
  • and by me 5 days before that :)

    anyhow glad it was addressed relatively quickly

    Thursday, August 27, 2015 1:05 PM
  • I am also facing the same issue,

    I imported 1.82GB drivers (source), the driver package created was the 51.1GB

    Driver Package issue

    Do I need to install the hotfix or do we have any other alternative as a quick fix?

    Please suggest.


    Lokesh899

    Wednesday, December 23, 2015 7:26 PM
  • The quick fix is to install the hotfix and then remove/reimport the drivers.

    The longer term fix is to proactively keep ConfigMgr up to date. This fix was included in Cumulative Update 2 released at the beginning of last month.

    I hope that helps,

     

    Nash


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Wednesday, December 23, 2015 9:07 PM