I work with Matt and the driver import will now show the drivers after restarting WMI. Hopefully it is not a temp fix but we have a meeting with you MS PFE and will bring it up with him. Also, it was any drivers and not just Win10.
Michael Schultz Client Systems Engineering Information Systems Providence Health & Services [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Atkinson, Matt T Sent: Monday, December 07, 2015 8:43 AM To: [email protected] Subject: RE: [mssms] Driver import failing Mike, Did you ever figure this out? We are seeing a similar issue after our update to SP1 CU2 this weekend. When we try to import the folder of drivers (Windows 10 VMWare drivers), the list is empty and we get the same error about OSDDriverCatalog.dll in the adminui log file. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, December 02, 2015 4:42 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing Bump, still hoping to find the cure. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, December 1, 2015 10:45 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing Tried that, still no luck. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Monday, November 30, 2015 5:48 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing Try restarting WMI service. You said you’re on an older version, not latest release/CU where there are some reports of similar (I think that’s the same error, need to double-check), and restarting WMI service typically clears it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Monday, November 30, 2015 10:16 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing OK, found this in the SMSProv.log. Closest thing I can find is the OSDDriverCatalog.dll file is possibly corrupt? *~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspdriverci.cpp(683) : Could not load OSDDriverCatalog.dll~*~* SMS Provider 11/30/2015 9:14:19 AM 9168 (0x23D0) *~*~Could not load OSDDriverCatalog.dll ~*~* SMS Provider 11/30/2015 9:14:19 AM 9168 (0x23D0) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Tuesday, November 24, 2015 10:38 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing I renamed all the subfolders to remove the .inf extension, same error as before. :( From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Joe Sestrich Sent: Monday, November 23, 2015 5:10 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Driver import failing Known to me, I don't know about anyone else. I didn't google it to find out. :) I think I just renamed the folders to get around it. Shouldn't matter, right? They get imported to a different path anyway. Sent from my iPhone On Nov 23, 2015, at 7:56 PM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: Interesting. The CAB I have does indeed have multiple subfolders with a .inf extension. Is this a known issue? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Joe Sestrich Sent: Monday, November 23, 2015 3:53 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Driver import failing I remember having an error once, because there were subfolders named *.inf, might check that Sent from my iPhone On Nov 23, 2015, at 3:38 PM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: Bump. To summarize my answers to earlier questions: Server is 2012 R2 No recent activity in DriverCatalog.log We have other Win 8.1 drivers working Using 7-Zip to extract drivers From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Thursday, November 19, 2015 11:21 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Driver import failing 7-Zip From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Thursday, November 19, 2015 10:48 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Driver import failing How are you extracting the CAB? 7zip or something similar? ----------------------------------------------- Adam Juelich Pulaski Community School District<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.pulaskischools.org&data=01%7c01%7caaron.czechowski%40microsoft.com%7c5ec7800ebb694127a91308d2f9b2951f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=1nIYypqIOK0SLwoAe7S7xZ4I3OhvYDOkZewJPSxSyqU%3d> Client Management Specialist 920-822-6075 On Thu, Nov 19, 2015 at 11:26 AM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: Hey folks, The last couple of times I’ve tried to import drivers from a Dell CAB, every one errors out. It goes through really fast. Any ideas? <image001.png> Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357<tel:530.898.4357> [email protected]<mailto:[email protected]> ________________________________ The Pulaski Community School District does not discriminate on the basis of any characteristic protected under State or Federal law. ________________________________ This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. ________________________________ This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
