This may already be addressed somewhere, but I figured it out the hard way. After building a new KBE for USB with KBE Manipulator 3.7, then downloading it to my Windows 7 SP1 workstation, running install.exe from the Windows gui creates a blank USB key. It works if you open a CMD prompt as admin, change to the kbe directory and run install.exe from there.
Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment


It is already addressed.  Look at the readme.txt located in the downloaded directory that contains the install.exe

Answered 03/10/2015 by: SMal.tmcc
Red Belt

  • Fair enough. When did this change? I was able to use the gui a couple of months ago, although I'm not sure what version of the manipulator I had then.
    • Yea I complained when they first made the change. It broke when they hid the cmd window. It was during 3.6 this changed. I created an exe with AutoIT that lets me click again. "Run(@ComSpec & " /c " & 'install.exe', "", @SW_HIDE)". The change is in error but I wish they fix it. It is a file that is on the KBOX that gets injected into the files during the build with either MM or the KBEM.
      • OK. Did you complain through Uservoice? If so, point me to it and I'll add my vote.
      • No I complained to one of Kace's Sr Eng and they passed it along to the person responsible for that install.
      • looks like it is fixed with 3.7sp1 RC. I did an KBEM upload yesterday and just created a usb boot from it. downloaded, unziped and was able to double click on install.exe. so looks like it will be fixed when the SP1 release becomes available to the public
Please log in to comment
Answer this question or Comment on this question for clarity