-->

This forum is for all HP users not just professionals (there is a separate forum for IS professionals, actually.) If it is a 'plug-and-play' device, it is responding with valid PnP information. Thanks for clearing, it is a plug and play device, but from user's perspective, a disappearing drive is not working normally. When I attempt to import drivers into my driver database I get the following errors: server SCCMData drivers driverDownloads Dell Latitude E7270 NetworkDriverKJTXRWN3220.2.0.0A00 production Windows10-x64 E1R65x64.inf is not applicable to any supported platforms. First make sure you have the above posted modifications in your.inf to your driver, then copy this driver onto your USB key and boot into WinPE. Go to the commandprompt and find the driveletter for your thumbdrive where the driver is located. Type drvload x: driver driver.inf (where X: is the path to the driver).

This article fixes an issue in which you can't import drivers into Configuration Manager.

Original product version: Microsoft System Center 2012 Configuration Manager, Microsoft System Center 2012 R2 Configuration Manager
Original KB number: 3025419 Skycomputereurope driver download for windows.

Symptoms

Consider the following scenario:

An administrator tries to import drivers into Configuration Manager.
The site server is running Windows Server 2008 R2.
The drivers are signed.

In this scenario, you may receive the following error message:

Error: Some driver(s) cannot be imported successfully. See following details.

Error: Failed to import the following drivers:

<Driver> - The selected driver is not applicable to any supported platforms.

When you view the Configuration Manager logs, you see the following errors:

DriverCatalog.log

<UNC_Path_To_Driver><Driver>.inf is not applicable to any supported platforms.
Driver is not applicable to any supported platforms. Code 0x80070661

SMSAdminUI.log

System.Management.ManagementExceptionrnGeneric failure rn at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)rnManagementException details:
instance of SMS_ExtendedStatus
{
Description = 'Driver is not applicable to any supported platforms.';
ErrorCode = 1633;
File = 'e:nts_sccm_releasesmssiteserversdk_providersmsprovsspdriverci.cpp';
Line = 712;
Operation = 'ExecMethod';
ParameterInfo = 'SMS_Driver';
ProviderName = 'WinMgmt';
StatusCode = 2147749889;
};

SMSProv.log

~*~*~e:nts_sccm_releasesmssiteserversdk_providersmsprovsspdriverci.cpp(712) : Driver is not applicable to any supported platforms.~*~*~
~*~*~Driver is not applicable to any supported platforms. ~*~*~

When you view the Setupapi.app.log file in the C:Windowsinf directory, you see the following error:

>>> [SetupVerifyInfFile - <UNC_Path_To_Driver><Driver>.inf]
>>> Section start <Date> <Time>
cmd: C:Windowssystem32wbemwmiprvse.exe -Embedding
! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
! sig: Verifying file against specific (valid) catalog failed! (0xe0000244)
! sig: Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
<<< Section end <Date> <Time>
<<< [Exit status: FAILURE(0xe0000244)]

Cause

Some drivers are signed by a newer signing method that's not recognized or natively supported by Windows Server 2008 R2. Therefore, these drivers cannot be imported into Configuration Manager if the site server is Windows Server 2008 R2.

Resolution

To resolve the problem, install one or both of the following hotfixes on the site server that's experiencing the problem:

2837108 You cannot import a Windows 8 signed driver on a Windows Server 2008 R2-based WDS server
2921916 The 'Untrusted publisher' dialog box appears when you install a driver in Windows 7 or Windows Server 2008 R2

Note

Hotfix 2837108 will resolve the issue even if WDS is not installed on the site server.
These hotfixes will add the necessary support to Windows Server 2008 R2 to natively recognize the newer signing methods.

To fully fix the problem, restart the site server after you install hotfix 2837108 or hotfix 2921916. Do this even if the installation process does not prompt you to restart.

After you install hotfix 2837108 or hotfix 2921916 and then restart the server, any affected driver that's already in the Configuration Manager console will have to be removed and then reimported.

More information

Surface Pro 3 drivers are an example of drivers that exhibit this problem. Because Surface Pro 3 drivers are signed by the newer signing method, they are affected by this issue. You may be able to import them into Configuration Manager when the site server is running Windows Server 2008 R2, but they will be displayed as unsigned until either hotfix 2837108 or hotfix 2921916 is installed on the site server.

If you are able to import the drivers but they are displayed as unsigned, see Signed drivers are displayed as unsigned in Configuration Manager.

'The selected driver is not applicable to any supported platforms.'

Wait, what? We are on SCCM 2012 R2 CU3 (CU4 any day!) so we should not get something like this. Did I somehow get some secret Windows 10 drivers somehow? Lots of mis-written INF files? This is strange.

In my last post I was talking about one time driver injection. We've moved past that as we liked the Toshiba device and decided to buy a large number of them so they need to be setup in SCCM. Initially, a Toshiba INF driver was mis-written to state it supported 64-Bit when the DLL it called for were 32-Bit only. BSOD's all around. After fixing that I still had to address this supported platform problem. While trying to import drivers we would get this error about several of them, mostly NIC drivers not being imported due to being unsupported . In the case of the Toshiba, the physical NIC did not import, however the WiFi driver imported, so after sysprep the Toshiba started imaging over the wireless interface. That was fun, I don't recommend that.

Drivers Not Applicable Meaning

Looking at the INFs they were written in normal Intel fashion and even making some modifications to strip down to Windows 8.1 did nothing. Digging through the SCCM logs was not a ton of help either. AdminUI.Log, DriverCatalog.Log, SMSAdmin.Log, Setupapi.app.log, you name it. All just said the same thing, driver not applicable. Those actually gave an error code of 0x80070661. Drivers Not Applicable

Turns out the issue is due to our Site Server being on 2008 R2. Specifically with the OS. The signing in these drivers is using a newer method thats not native in 2008 R2. Microsoft released KB3025419 which states to install KB2837108 and KB2921916 to update the OS to support the newer signing method in ConfigMgr. Coincidentally both this KB and the Toshiba device came out at the same time. After applying the hotfix and restarting (not required but the KB states to do anyway) we are now able to import these newer signed drivers and image the Toshibas up successfully and quickly.

Drivers Not Applicable To Be

-Kevin