KACE Product Support Question

Failing to create a Custom KBE (Kace SDA)

10/14/2019 601 views

i just upgraded from 6 to 7 in the SDA, but i have problems creating KBEs with the new media manager (the one that is merged with the KBE manipulator), the process stops in the "uploading drivers" step, after the powershell step, no error just stops.

from the VM im using i have access to the samba share

i dont have AV or firewall in the VM

if i use the older version of Media Manager i still can create KBEs but i cant create Kustom KBE

Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

The problem was that the windows 10 i was using was in spanish. the new Media Manager looks like only works on English Windows 10 
Answered 10/25/2019 by: acid8k
Yellow Belt

Community Chosen Answer


Check the media manager logs in your temp directory.  See if you see a command configure error in it when it stops. There is a bug that has been reported that if you command configure installed it will error looking for the hapi directory and fail like you described.

Answered 10/14/2019 by: SMal.tmcc
Red Belt

  • this is the error log

    [14-10-2019 15:27:35]: Exception creating KBE: System.UnauthorizedAccessException: Acceso denegado a la ruta de acceso 'C:\Users\KBE\AppData\Local\Temp\wcpdc35h.dhq\mount\windows\system32\winpe.jpg'.
    en System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    en System.IO.File.InternalDelete(String path, Boolean checkHost)
    en System.IO.File.Delete(String path)
    en kmediamanagerwin.frmMediaManager.StartWinPEBuild(Object sender, EventArgs e)
    • Is the user "KBE" an admin on this machine?
      • yep
      • that error is when the MM is trying to add the pe background to the boot env build in your temp directory and cannot. If you have checked change background under advanced option uncheck it and try again. Also can you clean out the temp directory and all sub-directories, so no artifacts from the last failed build exist yet.

All Answers


I would recommend reading the new Media Manager Logs at:


The file should give you some hints, also do a NET USE in cmd, delete any cached connection to the SDA and attempt to create the KBE again.

Answered 10/14/2019 by: Channeler
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ