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
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.
This issue is applicable to Window 7 OS:
*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...
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)
6) I have installed Microsoft Windows 7 operating system. In the device manager I can see a yellow bang and the device id is shown as ACPI\MSFT0101. What driver am I missing?
A: With the introduction of TPM 2.0 Microsoft has released a hotfix, to support the new TPM modules for, Microsoft Windows 7 OS variants. The ACPI recognizes this device as ACPI\MSFT0101. The KB article and hotfix is available as of this writing at the below link http://support.microsoft.com/en-us/kb/2920188
7) How to get native NVMe support for Windows 7?
A: If your platform supports NVMe for PCIe and the operating system is Microsoft Windows 7, it will need a hotfix to provide native support for NVMe for PCIe.
Below URL provides the advisory...
However installing this KB can also present a BSOD. Microsoft has provided a fix for this issue. Please refer below URL for the hotfix, for the STOP error (if you might see one) after installing KB2990941
8) Some Win10 drivers don't import correctly into SCCM 2012 SP2 or SCCM 2012 R2 SP1?
A: There is known issue for Windows 10 Driver Import in SCCM 2012 SP2\R2SP1. To resolve this, you must apply the KB: KB3074857
9) Is there anything special I need to do to prepare for Windows 10?
A: Yes, to properly prepare your systems for Windows 10, update the platform BIOS with latest update. The system components below are not supported with Windows 10, updating to latest BIOS will not show these devices in device manager
10) Some drivers are missing from the Win10 cab. Where do I get them?
A: Some drivers are only available through Windows Update and some are yet to be released and will be included in a future cab.
11) I am using Microsoft Windows 7 x64 operating system. One of the driver updates gets installed but there is a yellow exclamation mark seen on device manager. In another case the same driver is not installed at all and the logs complain a digital signature issue. Is this possible that driver cabs contain drivers that are not digitally signed?
A: Drivers are tested for being digitally signed well before they are made available to dell.com/support. They again go under rigorous testing before they are included in the driver cab. There are so many reasons why the system would complain that drivers are not signed. Ensure that the operating system’s certificate enrollment policy is not switched off. If you are connected to a domain then the enrollment pulls certificate information from the domain controller if configured so. There are this and many other settings to ensure the system "understands" the digital signature.
There is a new scenario that is being seen recently as Microsoft has released a security update for windows 7 x64 systems around March. Basically Windows 7 systems use SHA-1 as hash algorithm for digital signatures. This hashing algorithm is now considered less secure and hence they have provided a security update for allowing Windows 7 x64 systems to use SHA-2 that is available by default in later systems (Windows 8 and above). Some Hardware Vendors have considered changing the digital signature algorithm used for their drivers, where for Windows 7 drivers they are using SHA-2 as default hashing algorithm. Hence if you try to install these drivers in a Windows 7 x64 system they will fail.
Please check the problem system to see if KB3033929 has been pushed. If not, this might fix the issue. Relevant links are below...
12) Why is there an exclamation mark present on the device manager, for Intel 8260 Bluetooth device , after installation?
A: The latest versions of Bluetooth drivers provided for Intel 8260 Bluetooth modules may present an exclamation mark on device manager after install. This is because the driver tries to update the firmware and while doing so it looks for some related files in C:\ drive specifically. We are working with Intel on the bug-fix and we expect to bundle the fix in our upcoming driver cabs. Meanwhile, the work around is to force deployment of the Operating system to C:\ drive.
SCCM users can refer the below link to force installation of the Operating System to C:\ drive.
For others who already have an OS deployed to a drive other than C:\ the below command could help
subst c: <actual drive:>
e.g.) subst c: d:\
Above command would make all references made to c:\program files\Intel, in an application, get redirected to d:\program files\Intel
13) Why is the Intel Phi co-processor driver not included in T7610/R7610/T7910/R7910 driver cabs?
A: Advanced workstations - T7610/R7610/T7910/R7910 provide support for Intel Phi co-processor card. However we do not provide factory Install or driver cab support for these drivers. Drivers won't be included in driver cabs for Windows 7, Windows 8, Windows 8.1 and Windows 10 operating systems. Inclusion of the drivers have presented BSODs in the past. Also to actually put this device to use one will have to install the entire MPSS software stack provide by Intel. MPSS should also install the necessary drivers required for this device to function. This driver is also available from dell.com/support for the respective products.
14) My driver installation fails. The error in setup log suggests it has timed out. What would be the cause?
A. There are two cases of timeout one that is due to delayed activity of the co-installer supplied with the driver and second due to driver signature checking related activity. For the former, we would usually provide you with a better solution in the subsequent release of our cab. For the latter, Microsoft has already documented this fact. Please refer to below KB article.
15) Why is the driver cab missing Intel USB 3.0 switch component in the USB 3.0 driver?
Answer: Windows 7 USB driver stack is built to support USB 2.0 only. However USB 3.0 option was provided to vendors. Hence the entire USB 3.0 stack including support for innate USB 2.0 stack is provided by the vendor of the device through the driver they provide. Therefore for Windows 7 it was required that a switch be made from USB 2.0 to USB 3.0 as there was no direct support for USB 3.0. This is achieved by the iusbhcs.sys component provided in the Intel driver package. However it is also a requirement that this driver be installed only via “setup.exe” application or a similar driver installation program. This is against the INF-installation method that is supported by SCCM/MDT or even DPInst and such utilities. We have observed BSODs in case the “HCS” was included and installed via the INF file. Hence we do not pack this component. To achieve full USB 3.0 functionality one would still want to run the setup.exe application that DELL provides via the drivers available in support.dell.com (of the format Self-extractable installer executable – DUP).
16. Why does MDT have issues importing Driver Packs?
Unable to import Broadcom Control vault driver to MDT. While importing – user gets a “Length cannot be less than zero; Parameter name: length” error
The latest Control Vault drivers are packaged with both driver and firmware together. And there is a file named “current_version” in the firmware folder without a file extension. MDT does not recognize files without extensions hence this driver import fails.
Broadcom is planning a driver update for addressing this issue. Meanwhile Control Vault applications can be installed as part of Task sequence.
17. Why Dell Command Integration Suit is failing to import some INF files from Display Link Dock Driver?
It is a known issue with Dell Command Integration Suit which will be fixed in next release. As a work around, import the failed drivers manually to Configuration Manger Console and add to the Driver Packages. Kindly refer below URL to import Drivers manually.
18. Why ‘Apply Driver Package’ task is failing with Windows7 OS while installing one of the Drivers with ADK 1607?
The issue is currently under investigation by Microsoft. The problem seems to be caused by DISM trying to load the registry of the offline OS when it has not finishing unloading the registry from a previous driver install registry load. This issue primarily happens on faster PCs with SSD drives, mainly SSD NVME drives, but can occur on any PC. For workarounds please refer to below link.