KB Manipulator is hanging during the 'Mapping K2000' process. K2000 Media Manager runs fine from the same machine and successfully builds my KBE. However, KB Manipulator will not create my KBE. If anyone has seen this before and has a solution that would be great!  I am running it on a Windows 7 VM, Iv'e tried reinstalling both Media manager and KB Manipulator with no success of fixing this issue.
Answer Summary:
4 Comments   [ + ] Show Comments


  • I'm also having the same issue, since it prompted me to update KBE manipulator. Same this, but I've tried multiple machines as well. No Z drive mapped anywhere.
  • Good to know, maybe I'll try to roll back to an older version of KBM.
    • Older version mapped drive fine but had an error regarding the user\xxx\appdata\temp\2\build directory.
  • FYI, I found KBM to work fine on a Windows 10 Box
  • I am also having issues where the KBE Manipulator it just sits on mapping drive. version is

    I have tried on a windows 7 and windows 10 machines both with PE3 and PE10 tools with no joy.
    • Bobbinson, see below and try what I did, it might work for you as well.
Please log in to comment

Answer Chosen by the Author

I am also having the same issue. Has anyone else ran into this issue, and resolved it?
Answered 05/26/2016 by: acox
White Belt

  • Did you ever find a solution for this?
  • I was able to fudge things to get it to work. I noticed that KBE Manipulator was running an application called get_network_drive.exe from the following directory: "C:\Users\USERNAME\AppData\Local\Temp\2\kbe_man". While the program was Hung on mapping drive, I reran the application as administrator and this seemed to pull it from the holding pattern it was in. Somewhat of a hokey solution but it worked for me twice.
  • I am hoping they come out with an Update soon to fix this... anyone listening.... anyone?
Please log in to comment


They way I fixed the issue was to use the Manipulator on a vanilla VM which was not joined to the domain.

I believe a GPO was causing issues on our domain and this fixed it.
Answered 08/19/2016 by: bobbinson
Senior Yellow Belt

Please log in to comment
Hi All,

I also have the same issue.
By reading different posts on similar topics concerning KBEM issues, I found a workarround :
- run a CMD as administrator (same account than used to run KBEM) ;
- browse to the "%Temp%\kbe_man" folder : "cd %temp%\kbe_man" ;
- then run get_network_drive.exe.

The status windows messge should change from "Mapping K2000" to "Copying..."
Answered 10/25/2016 by: fcaignard
White Belt

  • Thanks, Already posted that one.
Please log in to comment
Make sure you don't already have a drive mapped to z:. The KBE Manipulator maps the K2000 share on that drive and it will fail if there is already a drive mapped. 
Answered 03/29/2016 by: chucksteel
Red Belt

  • Thanks Chuck, but that is not the issue. No existing mapped drives. This problem is strange because the Media Manager has no issue and I believe KBM uses the media manager.
Please log in to comment
Answer this question or Comment on this question for clarity