The new driver with windows 10 version(see driver inf section heading below) is not compatible with SCCM 2012 SP2 and so all these windows 10 drivers are failing to imported to sccm driver catalog. See the DriverCatalog.log.

SCCM Version: SCCM 2012 R2 SP1 (5.0.8239.1000)

ADK Version : ADK for Windows 10 (10.0.10114)

OS version: Windows Server 2012 (6.2.9200)

Driver INF Section

<![LOG[Driver is not applicable to any supported platforms. Code 0x80070661]LOG]!><time="13:03:11.210-330" date="05-26-2015" component="DriverCatalog" context="" type="3" thread="1328" file="osddrivercatalog.cpp:844">

Please help if anyone has any information on this issue.

Version 6.4 was used earlier in the beta process...

Now the version is 10.x

That might me why you see this.

Not 100% sure if 10.x driver are supported in SP2 or you have to wait for vNext. I'll ask and get back to you.

Thanks for the information. By the way there should be a patch not only for SCCM 2012 SP2 but all previous version will be required.

Is there any ETA provided on this.

I got the exact same results from the new AMD Windows 10 drivers, and I hear other folks have similar issues too.

Here are the errors I got:

Windows 10 Driver Import Fails in ConfigMgr 2012 R2 SP1
http://deploymentresearch.com/Research/Post/486/Windows-10-Driver-Import-Fails-in-ConfigMgr-2012-R2-SP1

/

I've submitted a bug report on connect:
https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1375201

Update: Microsoft has confirmed that this is a kno

The only current import workaround is to modify the driver, and sign it your self (you need to buy a certificate). I would wait until the fix from Microsoft is provided.

If you need to install a driver during the task sequence right now, you can just put them in a normal package, and call dism during the task sequence to stage them in the drivers store (during the WinPE phase).

But again, I would wait recommending until the fix from Microsoft is released which shouldn't take long.

/ Johan

I've applied CU1 to my 2012 R2 SP1 SCCM instance however I still can't import Windows 10 drivers. Can anyone else confirm this behavior? Note that I've applied the hotfix KB3084586 to correct the large driver package issue.

Environment is running on a fully patched Server 2008 R2 environment.

I'm attempting to import the drivers on the Primary and confirmed that the console is the updated version. Occurring across multiple models as well.

Seeing these errors in the drivercatalog.log (Driver is not applicable to any supported platforms, Code 0x80070661)

Cheers

Damon

• Edited by Damon A. Johns 2 hours 51 minutes ago

I've applied CU1 to my 2012 R2 SP1 SCCM instance however I still can't import Windows 10 drivers. Can anyone else confirm this behavior? Note that I've applied the hotfix KB3084586 to correct the large driver package issue.

Environment is running on a fully patched Server 2008 R2 environment.

I'm attempting to import the drivers on the Primary and confirmed that the console is the updated version. Occurring across multiple models as well.

Seeing these errors in the drivercatalog.log (Driver is not applicable to any supported platforms, Code 0x80070661)

Cheers

Damon

• Edited by Damon A. Johns Friday, August 21, 2015 4:59 AM

Where are you running the console? On the 2008R2 based site server? If so, try on a Win 8.1 (or Win10 even) client. Some driver import issues in the past (to my knowledge) had to do the OS version of the console.

Bingo Torsten! 

Applying KB2837108 and KB2921916 then restarting the Primary Site Server has fixed the issue.

Thanks and really appreciated.

I had attempted to import the drivers from my Windows 10 PC running a patched console install already Jason but thanks also for responding.

Cheers

Damon