Fixed: Importing Windows 10 drivers in ConfigMgr 2012 fails with “Driver is not applicable to any supported platforms. Code 0x80070661”


FIXWith the release of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2, Windows 10 drivers can now be successfully imported into the DriverCatalog.log file for operating system deployment. 

Prior to the release of CU1 and Windows 10, OSD would not import drivers marked for Win10 and errors resembling the following would be logged in the DriverCatalog.log file:

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

This problem was due to the way version number recognition was performed prior to the CU1 update.

For the latest information regarding Cumulative Update 1 as well as all the details regarding the fixes and updates included, please see the following:

3074857 Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

ConfigMgr 2012 R2


Comments (7)
  1. Cory - Columbia Heights says:

    I have installed the hotfix described above, and verified through the registry and the "About Configuration Manager" that the new console version is correct (5.0.8239.1203). However, I am still running into this problem where I cannot import Windows 10
    drivers – the same message of "The selected driver is not applicable to any supported platforms," and checking the DriverCatalog.log file does not give any additional information. I have been able to add the Windows 10 ADK, got the boot image for Windows 10
    added, and the OS image for Windows 10… but now I am stuck with not being able to image through SCCM because it fails due to a lack of drivers. Has anybody else run into the same problem after updating to CU1? Or has anybody had it actually work, so they
    can now import Windows 10 drivers when they couldn’t before CU1?

  2. Michael Frederiksmose says:

    I am also on SCCM 2012 R2 CU1 (5.0.8239.1203).
    I also hstill have this problem.

    Driver is not applicable to any supported platforms. Code 0x80070661

  3. psel says:

    I have the same issue, CU1 is installed but still errors during import.

  4. Damon Johns says:

    I also have the same problem as Cory – I have applied CU1 but I'm still unable to import Windows 10 drivers. In this case a Surface Pro 3 driver source.

  5. Steve@UI says:

    Running into same problem since installing CU1. Manage 3 SCCM sites and all doing the same thing. The DriverCatalog.log used to show errors related to the message "The selected driver is not applicable to any supported platforms" but after installing CU1,
    the error still occurs in the import wizard but nothing in the DriverCatalog.log.

  6. Herman van Drie says:

    Cory, it's due to your parent OS where the Site Server is running on is still on a down-level OS, ie 2008 R2.
    See here:

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

  7. Beli says:

    Hi, Same here
    Running Server 2012 – Site server, SCCM 2012 R2 CU1.
    Still getting same error for Surface Pro 3 driver import.
    Please help!

Comments are closed.

Skip to main content