Every since I have upgraded the K2000 to the newest version.  I have been having problems uploading a new KBE.  Let me tell you what I have tried.  I am using K2000 Media Manager 9.9.9 that comes directly from the K2000 at http://k2000/media_manager.  I know the samba share password is right, (I set it again just to be sure). x64 in Media Manager is selected btw.  AIK path points to the right location Hostname is right.  I feel like everything is right.  Once all this is set, I "Start Upload" and it goes through the whole thing where it uploaded drivers or what have you. It eventually gives the most generic ERROR message.  It is a message that says Error, the form box says Error, and there is an OK button with no other description.  I have tried deleting driver feeds and reinstalling and just this morning I uploaded the newest driver pack (KBE_driver_pack_3.zip) and extracted to the proper folders.  I don't know what else to do other than post the question here.  All this has happened after updating the K2000 to the latest and greatest...which isn't so great so far.  Thanks.

Edit.  I watched the progess window, it does get to the "saving .wim" portion of it then gets to the "unmounting" right after that and then produces the error message

Answer Summary:
5 Comments   [ + ] Show Comments


  • I do not. I've never used it. Maybe I need to read about it. Is that my problem?
  • Ok tried to follow the error again. It comes after saving the WIM and right after the UNMOUNTING part...something flashed really fast and then the error comes.
  • I installed the KBE Manipulator, let it update to that new version you mentioned. I also watched the outdated video but I get the jist of it. The video shows K2000 Media Manager automatically starting. That never happened for me. Maybe in the newer version it is build in. Anyway, the KBE appears to upload just fine...it said it did anyway. I did a PXE boot, and the KBE shows up in the menu options...I choose it and I get "Loading memdisk...: Could not find ramdisk image 0023.iso". Suspicious, I looked at the K2000 under Library >> Source Media. The KBE is there but it is only 72 kb. The other KBEs listed are around 200 MB. Any ideas?
    • can you post the log file in your appdata temp area. v3.7 now creates one
  • Jason,
    Make sure you are following this KB when creating a KBE:

    • Thanks cerrins for the reply. Today I have installed an entirely fresh Windows 7 SP1 OS. The only programs installed are:

      K2000 Media Manager
      KBE Manipulator
      Microsoft .NET Framework (K2000 prompted it needed it on install)
      Microsoft C++ 2008 Redistributable x64 & x86
      Windows AIK

      When following the instructions the "Error" message still happens when uploading a KBE using K2000 Media Manager (downloaded that fresh from the K2000).

      To recap, I have build many KBEs int he past...all have worked flawless. I have never been able to build one since I have upgraded to this newer version of K2000. I am at my wits end and don't know what else to do.
  • I am having the same issue with the K2000 Media Manager. I have not been successful in getting it to work since upgrading to 3.7. I've completely removed and downloaded the K2000 Media Manager again and still receive this error message.
Please log in to comment

Community Chosen Answer

This is an error that occurred in an older version of KBEM.  The latest version is, try downloading and then updating to that version.

Answered 01/22/2015 by: cserrins
Red Belt

  • I just verified my version and I am on v Any ideas?
    • Can you email or post the log in %temp% called kbem_log.
    • Can you delete the log, then run again. When you get the error message, don't click ok. Go get the log and post it so we can see where in the script the error is happening.
      • I don't receive the error in the first post since I have been using the KBE Manipulator for everything. If I were happen to JUST use the K2000 Media Manager (old way before I just discovered the KBE Manipulator) the first error message would appear. It appears by looking at the log that the KBE Manipulator uses the K2000 Media Manager during the process of making the KBE. Using the KBE Manipulator, the process finishes until completeion, says the KBE uploaded successfully, but when I go to PXE boot on the client and choose the newly created KBE, the message says (really fast and then returns to choosing the KBE you want to pick) I get "Loading memdisk...: Could not find ramdisk image 00*.iso". Suspicious, I looked at the K2000 under Library >> Source Media. The KBE is there but it is only 72 kb. The other KBEs listed are around 200 MB. Here is the log pre clicking OK to the message that it was uploaded successfully: http://pastebin.com/GPZcSES0
      • If anyone possibly knows why the KBE Manipulator appears to upload the KBE correctly but when I try and PXE boot I get get "Loading memdisk...: Could not find ramdisk image 00*.iso" and why the file size for that KBE only ends up being 72kb Library >> Source Media when all other KBEs are ~200MB please let me know. I'd love to get these computers out today :/
    • Jason,
      It is confusing since you posted under this question the assumption was you were getting this error.
      What are you trying to accomplish with KBEM, can you give step by step?
      • I was getting and still getting the error when using the K2000 Media Manager. I was asked under the "Comments" section above from SMal.tmcc implying I should use the KBE Manipulator...since that comment I have been trying to use that. When using the KBE Manipulator, the issues that you, cserrins, and I have been discussing are dealing with KBE Manipulator. I hope that helps and sorry for being confusing.
Please log in to comment


This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

Answer this question or Comment on this question for clarity