KACE Product Support Question

Using KBEM, adding PowerShell results in non-booting KBE, that's smaller than without Powershell

08/17/2017 584 views
I'm using the KBE Media Manipulator (KBEM), v., to create a KACE Boot Environment (KBE) from a recently downloaded-from-Microsoft Creators Edition of Windows 10 Enterprise. If I leave all the KBEM settings at their default (except for what has to change - name, IP address, Samba share) and create the KBE, the result is a KBE that boots and works, and which has a size in the Source Media window (K2000 / Library / Source Media) of 351.3 MB.

However, if I go into the menus (Configure / Modify KBE Tools...) and select to "Add Powershell" (which autoselects "Add .net 4"), and change nothing else (except to add a " w/ Powershell" to the name), and create the KBE, the result is a KBE of size 264.5 MB (smaller than without Powershell), which fails to boot. It gets to a command window and runs "wpeinit", and then just stops at the command prompt (X:\Windows\System32\>"). At this point I can run command-line commands, but the boot process has stopped. There also is nothing except a "Modules" directory in the \Windows\System32\WindowsPowershell\v1.0 directory.

What's up?



1 Comment   [ + ] Show comment


  • Very strange, but I can tell you this!

    We have been using a KBE created with the Manipulator and is working fine!, And I just realized that the file size is 265MB, less than any other KBEs.

    We use it for Bitlocker stuff and is working fine, but I wonder why the filesize is less than normal KBEs...

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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