HP MIK Tool Manage Driver ConfigMgr

[Vid3al]

When we use the HP tool to import the drivers of a computer model, the procedure often hangs as follows:

https://whp-hou9.cold.extweb.hp.com/pub/caps-softpaq/cmit/HP_CIK.html

----------------------------------------------------------------------------------------------------
2019/10/17 14:51:04.821 :: Existing driver object found.
2019/10/17 14:51:05.705 :: Adding driver to driver category HP Probook 6x0 G5 Windows 10 x64 Driver Pack
2019/10/17 14:51:06.689 :: Adding \\Drivers\SCCM\Driver_Packages\sp95056\PB_6x0_G5\wt64_1809\other\intel\P00TU0-B2V\src\INF\CannonLake-LPSystemNorthpeak.inf to SCCM.
2019/10/17 14:51:08.912 :: Existing driver object found.
2019/10/17 14:51:09.643 :: Adding driver to driver category HP Probook 6x0 G5 Windows 10 x64 Driver Pack
2019/10/17 14:51:10.473 :: Adding \\Drivers\SCCM\Driver_Packages\sp95056\PB_6x0_G5\wt64_1809\other\intel\P00TU0-B2V\src\INF\Baytrail-ISystem.inf to SCCM.
2019/10/17 14:51:12.486 :: Failed to create or retrieve driver object.
2019/10/17 14:51:12.487 :: Error - unable to create driver object: \\Drivers\SCCM\Driver_Packages\sp95056\PB_6x0_G5\wt64_1809\other\intel\P00TU0-B2V\src\INF\Baytrail-ISystem.inf
2019/10/17 14:51:13.128 :: Action import downloaded driver pack done.
------------------------------------------------------------------------------------------

in the sccm console, we searched the driver list for the file "Baytrail-ISystem.inf", and for each match we checked whether it was used in a package or in a boot image. we deleted those that were not used by packages or boot images.

but the problem still persists.

the one above is an example. proplema we have every time we have to package a new computer model.

-The problem is caused by the version 3.0.10.1 of the HP tool that does not appear to be supported by the SCCM version 1906 ?

-HP, not up-to-date and will no longer update tool to work with SCCM ?

https://social.technet.microsoft.com/Forums/en-US/83e80e6e-dcca-470e-b663-6ae1111a0ea4/hp-mik-tool-m...

-has anyone ever had this same anomaly? how did it solve? what does it depend on?

Thank you for your support.