Windows 10 Driver Applicability SMS Provider Error

[Rexlis]

Hello,

 

After importing drivers to create a driver package, I checked the Applicability tab under properties and found that Windows 10 was unchecked. When I went to add checkboxes (Since my image is Windows 10) I received "The SMS Provider reported an error." This only happens if I check the boxes for Windows 10, all other OS checkboxes work just fine. When I choose the first option "This driver can be run on any platform" it lets me apply the changes but when I initiated the Task Sequence on the computer it would download the drivers and for a brief moment go to installing drivers and then skip onto the next step. Once the OS booted up I checked device manager and there are missing drivers. Any help would be greatly appreciated.

 

Note: I upgraded SCCM last month to:

 

System Center 2012 R2 Configuration Manager SP1

Console Version: 5.0.8239.1000

Site Version: 5.00.8239.1000

 

 

The Error Message Details

 

ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

Description = "The digest is not valid";

ErrorCode = 1078462235;

File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspconfigurationitem.cpp";

Line = 2142;

Operation = "PutInstance";

ParameterInfo = "";

ProviderName = "ExtnProv";

StatusCode = 2147749889;

};

-------------------------------

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException

The SMS Provider reported an error.

Stack Trace:

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()

at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.ConsoleDcmConnection.Microsoft.ConfigurationManagement.DesiredConfigurationManagement.IDcmStoreConnection.UpdateExistingItem(ConfigurationItem item, Object existingItem)

at Microsoft.ConfigurationManagement.DesiredConfigurationManagement.ConfigurationItem.Persist(Object existingStoreItem)

at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.DcmObjectWrapper.Microsoft.ConfigurationManagement.ManagementProvider.IResultObject.Put()

at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock)

at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger)

-------------------------------

System.Management.ManagementException

Generic failure

Stack Trace:

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()

at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.ConsoleDcmConnection.Microsoft.ConfigurationManagement.DesiredConfigurationManagement.IDcmStoreConnection.UpdateExistingItem(ConfigurationItem item, Object existingItem)

at Microsoft.ConfigurationManagement.DesiredConfigurationManagement.ConfigurationItem.Persist(Object existingStoreItem)

at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.DcmObjectWrapper.Microsoft.ConfigurationManagement.ManagementProvider.IResultObject.Put()

at Microsoft.ConfigurationManagement.AdminConsole.SmsDialogData.Put(Boolean retainLock)

at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.Put(ActionTrigger trigger)

-------------------------------

 

[jphiffer]

Were you able to find a resolution to this issue? I noticed the same thing this morning when trying to add Windows 10 as an applicable OS.

 

ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

Description = "The digest is not valid";

ErrorCode = 1078462235;

File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspconfigurationitem.cpp";

Line = 2142;

Operation = "PutInstance";

ParameterInfo = "";

ProviderName = "ExtnProv";

StatusCode = 2147749889;

};

[Rexlis]

Not yet unfortunately... I have been having to create custom image captures for each model of PC i have in my environment.

[Rexlis]

What I plan to do is just migrate SCCM and SQL database to a new Windows Server 2012 box and see if that resolves the issue since I'm currently on 2008 R2. I have read that it could be the new windows 10 driver's signatures are not recognized by the server. I have seen online some hotfix patches but when I try to go to the download page, it says it no longer exists. I will update you if it works out.

[Rexlis]

I have resolved the issue. You will need to upgrade SCCM to at least Version 1511.

 

This was my previous build:

Console Version: 5.0.8239.1000

Site Version: 5.00.8239.1000

Now my current build is:

Console Version: 5.0.8325.1000

Site Version: 5.00.8325.1000

https://blogs.technet.microsoft.com/configmgrdogs/2014/02/07/configmgr-2012-version-numbers/

 

It's a really straighforward process on upgrading. I could not find a guide on windows-noob so I had to go this link just to help me out. https://www.systemcenterdudes.com/sccm-1511-upgrade/