KACE Product Support Question

Cabinet Maker - makecab.exe

07/28/2016 4971 views
I have users who are seeing a makecab.exe popup window


It seems like it coincides with the deployment of patches through Dell Kace to the client.

I would like to confirm if this is a by-product of the Dell Kace patch deployment, and is there any way to get it so this window does not pop up, and if it needs to run, can we keep it minimized or running in the background without the user knowing?
5 Comments   [ + ] Show comments


  • I have the same problem when I try to use the K1000 to patch. I see dozens of those CbsPersist windows on my test workstation.
  • Getting the same thing, but only on one domain. We have two KACE appliances and two domains with some overlap. I'm only seeing these makecab windows pop up on one of our domains. Very weird, hope someone finds a solution! They can just be minimized, but I don't want users to freak out.
  • It seems like I am not the only one... has anyone else seen this and have been able to work around this?
  • We just saw this as well in our org. Install agent, detect and deploy patches, 15 CbsPersis windows for log compression/decompression. I understand that this is part of th enormal deployment process, I'm just confused why we're seeing the windows. I don't see any other info in the forums - any update from anyone who has opened a ticket on this?
  • I have the same problem. On my Win8 and Win10 machines the deployment works without issues, but on the Win7 machine I get 4 of those windows, until each reaches 100%, then I get 4 new ones. My CPU is running at 100% while this is happening and I see about 30 "makecab.exe" and "conhost.exe" processes in the taskmanager... Anyone heard of a solution?

Community Chosen Answer

Christian1616 is best answer on this, I think (I'm not sure how to mark on this thread though!!). Thank you Christian! 

What I found was some old/bad logs in the ...\cbs folder mentioned on the image we were using when this was happening. Best guess is that Windows Update was running on a source image, we interrupted it to sysprep and upload the image, and it had a bad log cache which caused issues and prevented the normal wrapup procedure of the log files. For us, the solution was to use a new image that had an un-corrupted cache. However, we were able to workaround affected machines in the field by cleaning this cache out. Basically, you stop the update service, delete affected files or backup softwaredist folder to .old, start the service again.

This article helped some, and contains the script we modified to recify the issue in the field:
Answered 03/14/2017 by: fcoetech
Senior White Belt

All Answers

I wrote to the support about this issue and was told, the problem is probably caused by the OS and you would experience the same issues with any other patching appliance. 
You can check "C:\Windows\logs\cbs" for big log files and delete or move them (on a normally funcitoning system there should only be small logs). However, you should check your system anyway (starting with sfc /scannow). 
The support supposed that the cmd boxes appear, because some logs (which are allways created while patching) are too big and have to be "log rotated" (=archived ?) first.

Answered 02/06/2017 by: Christian1616
White 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