Importing Windows ADK install into DS is taking a long time


Article ID: 197553


Updated On:


Deployment Solution


When the customer clicked the link for "Click here to import Windows ADK",  the process just hung for several hours/days.  I noticed the DriverDBMgr64.exe process launches and just continually runs.

He rebooted the SMP, and now when he goes there he sees the hourglass shown, however the link is not active to click.  In addition, DriverDBMgr64.exe is not running a process.
I know about and I have already confirmed that INSTALLED=False is set for both [WINPE10_X86] and [WINPE10_X64] in the prebootos.ini file.




DS 8.5


This is not about the driver manager. WinPE import is performed by bootwizard. Hourglass is shown either bootwizard is running, or winPE import task exists. If it fails - it will be activated by daily schedule or you can force it by selecting any preboot image rebuild (there is at least la in image available).  
If you want to execute it manually, you can try to run the following command:
bootwiz.exe -install -q -os WinPE10 -x86
bootwiz.exe -install -q -os WinPE10 -x64
You can try to invoke it by task and check NS and bootwiz logs.
There is a BootWiz.log (e.g. at "C:\Program Files\Altiris\Deployment\Logs\Bootwiz.log") containing command lines that BootWiz was called with like these:
2020/08/18 12:57:37 I:      Command line: '"C:\Program Files\Altiris\Deployment\BDC\bootwiz\bootwiz.exe"  -install -q -os WinPE5x -x86 "C:\Program Files (x86)\Windows Kits\8.1"'
2020/08/18 12:58:40 I:      Command line: '"C:\Program Files\Altiris\Deployment\BDC\bootwiz\bootwiz.exe"  -install -q -os WinPE5x -x64 "C:\Program Files (x86)\Windows Kits\8.1"'

Also, if BootWiz cannot import WinPE (ADK), then some error message should be logged there.