0) What is this FAQ about?
This FAQ is primarily about DELL COMMAND DEPLOY DRIVER PACK. It talks about issues a user might see with the driver packs and the reason why she/he would see that.
1) Why is the driver cab not having any Bluetooth drivers although the device supports it?
Bluetooth radio support comes with various devices and you would primarily see it with the WIFI cards. The Bluetooth driver isn’t included because they aren’t compatible with the INF-centric installation that is used by SCCM/MDT etc. Our driver cabs are primarily provided for automated deployment through software packages like SCCM/MDT …
2) I get a yellow bang on a Bluetooth device when I use this driver cab. What should I do?
Bluetooth drivers aren’t included in the driver cab for reasons said above. It is expected as of this writing that, with the currently available Operating Systems provided by Microsoft, an inbox driver (Generic Bluetooth Radio) will be installed for Bluetooth. There are inbox drivers for various Bluetooth profiles. However since you are seeing a yellow bang, you can look up for a Bluetooth driver package from support.dell.com. This package (DUP package) has to be installed manually. It shouldn’t be used by extracting the contents and then using the extracted contents (perhaps as part of a compressed file) for remote deployment.
3) Why do I not find “Thunderbolt” driver in the driver cab?
Thunderbolt drivers have similar issues as seen in Bluetooth drivers. They can’t be used in the SCCM environment or installed correctly using just the device manager. We are working with the IHV to fix this issue.
4) Why did my deployment of Windows 7 fails with the error message, "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation." OR I have components that didn't install drivers that are in my driver package?
example error in setuperr.log (from %windir%\Panther) shows the following failure information:
2013-08-29 13:09:40, Error CBS Startup: Failed to process advanced operation queue, startupPhase: 0. Primitives are still pending. [HRESULT = 0x80004005 - E_FAIL]
2013-08-29 13:09:40, Error CBS Startup: POQ has not been processed yet, aborting startup processing. Startup processing will be attempted again. [HRESULT = 0x80004004 - E_ABORT]
2013-08-29 13:09:40, Error [0x030149] CMI Callback_CBS_Do_OnlineInstall:Calling startup processing failed 0x80004004
2013-08-29 13:09:40, Error [0x030153] CMI Callback_CMI_ConfigInstall: CBS startup processing re-run failed.
A: You need the updated Kernel Mode Driver Framework (KMDF) 1.11 included in your base image
Reasons for failure:
- Windows 7 Operating system comes with KMDF 1.9 (Kernel Mode driver framework) as part of image. Any driver release which is built with newer version of KMDF requires reboot of system during the installation, this reboot is unexpected during OS Setup.
- If the Win7 image used contains any security update or patch affecting the KMDF components is used along with driver (which is built on newer version of KMDF) then deployment would fail. Example: KB2808735
Resolution:
Download and inject package (2685811) as part of the image preemptively. So that same image can be used for OSD. This will avoid the unexpected reboot during OSD.
Scope/Affected Drivers:
This issue is applicable to Window 7 OS:
- 1. If the Win7 cab includes any driver consisting of wdfcoinstaller01011.dll (initiates KMDF upgrade to 1.11).
- 2. If the image does not include any security updates or patches affecting KMDF components (example KB2808735) then OS deployment might not fail, but it will prompt for reboot when User logins for first time.
*List of devices Affected:
(i) ST Microelectronics Free Fall Data Protection (ii) Intel Smart Connect Technology
(iii) Intel Management Engine Interface (iv) Dell Touchpad
(v) Intel Dual Band Wireless AC7260 Bluetooth
5) I am getting a pop-up during the final stages of OS installation (via SCCM/MDT etc.). The error says the service couldn't start because msvcr100.dll is missing. However when I click "OK" it continues the installation. What has failed during installation?
A: msvcr100.dll is a run-time library version. This popup would appear if the OS being deployed doesn't have this runtime library. It is possible that one of the drivers being deployed relies on this DLL file. You can refer below links to understand the issue and get the fixes.
https://msdn.microsoft.com/en-us/library/ms235299%28v=vs.100%29.aspx (Talks about the redistributable versions that you may have to manually install)
At the time of this writing, the library can be downloaded using below links...
http://www.microsoft.com/en-in/download/details.aspx?id=5555
http://www.microsoft.com/en-in/download/details.aspx?id=13523
After installing the above, the missing driver can be installed by extracting it from the .cab file and pointing to the INF file. (with device manager)