How to Uninstall or Remove SCCM ConfigMgr client using CCMClean exe

Since SMS 2003 days, we’re using CCMClean.exe to uninstall or remove the client components. Removing/Uninstalling ConfigMgr 2007 or 2012 clients using CCMClean.exe is not supported by Microsoft. “Not supported by Microsoft” !! So, what does that mean ? Well, it’s not tested (extensively) and certified by Microsoft for the products ConfigMgr 2007/2012. However, it may or may not work. In my experience, the CCMClean.exe is able to successfully remove/uninstall ConfigMgr/SCCM 2007 and 2012 client components. Smile More details below……

Download – CCMClean.exe (Download SMS 2003 toolkit and run it to install all the files – go to the installation directory, it includes CCMClean.exe )

We can run the CCMClean.exe on remote machines using PSEXEC.exe. You should have administrative privileges on that remote machine.


The command line parameters which can be used with CCMClean.exe.

Try and check out using “CCMClean.exe /?”

Silent install –> ccmclean.exe /q


I’ve tested CCMClean.exe on SCCM / ConfigMgr 2012 client and it did work perfectly !!!

a) Verify the CCMClean.log file to get more details

Log file location = “C:\Users\administrator\appdata\local\temp” OR %temp%


b) Check the event log for some more details or confirmation


c) CCM registry entry has been REMOVED


d) SMS Agent Host service has been REMOVED


e) WMI namespaces (root\ccm and root\cimv2\SMS) have been REMOVED


About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: CM2012, ConfigMgr (SCCM), Configmgr2012, SCCM, SCCM 2012, Tools


  1. Michiel Overweel says:

    Why bother if “ccmsetup.exe /uninstall” does the job as well, and *is* supported?

  2. Prabhat Joshi says:

    I agree with Anoop on this , ccmclean is more effective and cleans the WMI and registry traces from the machine .

  3. I had removed sccm client though ccmclean.exe in sccm 2007 updated client as found it worked.

  4. Young Pae says:

    Thanks for this. BTW, ccmsetup.exe /forceinstall is added for SCCM 2012 SP1. Do you think /forceinstall is strong enough so that we don’t have to run ccmclean.exe, reboot then try re-install?

  5. hi Pae,
    you dont have to run ccmelean.exe,with SP1, existing client will be uninstalled and then a new client will be installed.

  6. TGH says:

    I would NEVER use ccmsetup.exe /uninstall – never clears out everything fully, CCMClean is by a long distance the best tool for this job.

  7. Harry says:

    I am new to SCCM .I have uninstall the client .Can you please help me to install the client again on server .

  8. Raman Katoch says:

    I am getting error messages after running the “ccmclean.exe /Client” , error1. “failed to connect to namespace root\ccm\softwareMeteringAgent(80070422) , error2. “failed to open to WMI namespace ‘\\.\root\ccm\SoftwareMeterringAgent’ (80070422) , error3. Failed to run command line “”C:\windows\ccmsetup\ccmsetup.exe” /uninstall” (740)

    Though i have already Run Ccmsetup.exe /uinstall , i have SCCM2012 environment… but ccmsetup.log showing me following lines:
    “Unable to delete file C:\WINDOWS\ccmsetup\ccmsetup.exe (0x80070005). Continuing.
    Failed to clean ccmsetup files for uninstallation.
    Task ‘Configuration Manager Client Upgrade Task’ does not exist
    CcmSetup is exiting with return code 0”

    so i thought it may not uninstalled in a proper way then i came across your article.

  9. Raman Katoch says:

    Thanks Anoop for your quick response, Appreciate it !!!

  10. Richard Davies says:

    Hi Anoop, I am trying to fix a problem with the MP and BITS Server Extension on my site server and after several deinstall/reinstall cycles of BITS, MP and client I’m now just desperate enough to try uninstalling the client with ccmclean.exe rather than the ‘supported’ methods. Is there any issue with running it on an SCCM 2012 site server, with the /client switch?



  11. Chad says:

    Worked like a change. Thank you.

  12. Tom says:

    Thank you, this worked like a charm. I had a machine that ccmsetup.exe (2007) /uninstall did nothing, manually removed the client but the 2012 install always failed. Ran this few times for gave some errors first time, then tried the 2012 install and boom! Took 2 days of work and so simple solution in the end.

  13. Stian says:

    Hi! I had to uninstall a lot of configmgr clients, and they still appear as installed in the configmgr console. I’ve confirmed that they are uninstalled 🙂
    Is there any way I can force a “cleaning” of the repository so that they appear as uninstalled?

  14. Shashank Bhatt says:

    Hi Anoop,

    Could you please give me the command line to uninstall client remotely through ccmclean.exe via psexec

  15. Javed says:

    Hi Anoop,

    We are facing a unique issue with windows 8 systems. We have SCCM 2012 SP1 installed in the organization.

    Whren we push SCCM client on windows 8 systems, after a few minutes / hours the SCCM client uninstalls automatically.

    Have checked the ccmsetup.log and it shows that the command ccmsetup.exe /uninstall has been initiated.

    The issue is that we have not initiated any uninstall command on the client neither manually nor from the console.

    This issue is happenning on all WIndows 8.1 systems.
    Don’t know what the issue is ? Can you please help ?


  16. Anoop says:

    JD ! – Have you checked the Group Policies and Event logs that may give you some more idea to troubleshoot ! Regards

    • Javed says:

      Hi Anoop,

      Thanks for the reply, I have checked the Group Policies & Event logs, nothing over there.

      During trouble shooting i discovered that in our SCCM environment we have SCCM SP1 CU4. But all the clients were at version 5.00.7804.1000 whereas they should be 5.00.7804.1500. Also client version 5.00.7804.1000 is not supported on Windows 8.1.

      So I deployed 5.00.7804.1500 on couple of Windows 8.1 systems but still the client gets uninstalled.

      When I check the ccmsetup.log the commandline used is “\\\client$\ccmsetup.exe /uninstall”

      As a workaround I have removed the share client$ . Can you tell me if this share is required or not and will there be any adverse affect of removing it ?

      Keeping it under observation.


      • Anoop says:

        I’m sure that Client$ share something specific to your environment. Where is this Client$ share located ? Is it in SCCM server or SCCM Client machine?


  17. Javed says:

    The commandline used is “\\sccmservername\client$\ccmsetup.exe /uninstall”

    • Javed says:

      The folder that was shared as client$ is “D:\Program Files\Microsoft Configuration Manager\inboxes\Client ” . It is on the SCCM primary server. Do we have a client folder at this location and is it shared by default ?


      • Anoop says:

        No. If I’m not wrong. This is a custom share, which somebody must have created. Also there could be some packages or applications running from SCCM console.

  18. Wayne says:

    Hi I keep getting this on install of sccm I can’t see the client installed anywhere. “You cannot install the management point on a computer with an earlier version of the Configuration Manager client installed. Upgrade the client to the current version, remove the client, or select a different computer for the management point installation, and then try again”

    2007 is installed on another server this is a fresh primary site 2012 install it allows me to carry on the install but then there’s no MP

  19. Dr Jones says:

    is there any way to uninstall the client from SCCM? and there is a image that on my network that has been deployed by sccm and its wiping the PC one by one when clients click on it is there any way to stop this from happening?

  20. Vinoop says:

    Hi Anoop,
    I have a scenario, where I am trying to Setup a client push installation on laptops with SCCM 2012 R2.
    We have a old domain with SCCM 2007 and once the laptops are moved to new domain, I am trying to push the client to it,.
    Please could you let me know the procedure to remove the old client and install the new one.
    I trying forcefully removing it, and it didn’t work.
    Is there any automated way of doing it, or should I create a script and using it with the push client installation?
    please help.


  21. ourson_malin says:

    For me, this tool does’t work because, he try to delete ccmsetup folder in c:\windows\system32 but my folder is in c:\windows

  22. Willie says:

    Hello, Anoop.

    I know this is an old thread, but I continually run into the following message while running CCMClean.exe to uninstall CM12 SP1 clients:

    Installation succeeded. Windows Installer has requested a reboot.

    I feel it is absurd that the OS requests this, as no administrator or technician has time nor desire to contact a user and request that they interrupt their current session just for a reinstall of the CCM client (likewise, no user wants to do it – nor should they have to do it). SCCM 2007 was never like this, from what I recall.

    I’ve tried shutting down both the SMS Agent Host Service and the CmRcService prior to the uninstall, but it’s usually the same result. Is anyone aware of what, exactly, the Windows Installer needs a reboot for to complete the uninstallation and whether or not there are any workarounds? I’ve seen it move files into the Windows temporary directory for deletion, but it should just be able to delete it anyways because CCMExec should not longer be active and utilizing the files in question, so I’m at a loss. If another service or process is using those files, then I’d love to know what it is so I can kill that process in my uninstaller script prior to executing CCMClean.

    Thanks in advance!

  23. TixTix says:

    Hi Willie,
    I am also interested about your question to Annop,
    I hope he will answer ! 🙂
    Have a nice day.

  24. Ranjan says:

    Hi Anoop .. In our SCCM 2012 environment We have VDI machines .. In daily basis we found 20-30 machine’s SCCM client corruption issue .. Therefore we use following manual steps for each VDI machines one by one which takes couple of hours … How can we go for an Automation kind of batch file or script to do this job on schedule basis by providing the VDI corrupted client machine name from Primary Server instead of these manual steps.. Thanks

    Now Mannnula steps are here ….

    SCCM Client remediation steps:

    1. Check ccmsetup logs for installation failure errors. etc : Failed with error code XXX
    2. If the installation is failed performed clean uninstallation and reinstallation


    1. Run c:\windows\ccmsetup\ccmsetup.exe /uninstall – monitor ccmsetup.log
    2. Run ccmclean.exe and wait for the process to complete ( process monitor)
    3. Rename CCMSetup,CCM,CCMCache folders in c:\windows
    4. Make sure C:\windows\SMSCFG.ini is deleted, if not rename it
    5. Make sure no task scheduler named Configuration manager under Microsoft task scheduler , if exist delete it ( delete the task in it before deleting the folder)
    6. Make sure registry key HKLM\Software\Microsoft – CCM & CCM setup is no more – if not rename them


    1. Copy all the setup files (CM2012Client$) to local drive from ( c:\temp) \\MFCSCCMPKL02 \CM2012Client$\
    2. Run the command as – cscript.exe c:\temp\CM2012Client$\SCCM-ClientInstall.vbs /RunLocal:true
    3. Monitor the c$\Windows\ccmsetup\Logs – ccmsetup.log for error code 0
    4. While the setup is running, monitor task manager – CCMSetup to CCMExec – meaning setup is success and its moving to contacting the SCCM server for further assignments

    4. For WMI errors try to rebuild the WMI repository
    1. Stop the Windows Management Instrumentation service
    2. Rename repository folder in c$\Windows\System32\wbem to repository.OLD
    3. Restart the Windows Management Instrumentation service
    4. Monitor new folder called repository will be created on the same location

    5. If the installation log already success then

    1. Check the SMSHost service status, it should be on automatic and running
    3. Also rename C:\windows\SMSCFG.ini and restart the SMSHost service
    4. Check whether new SMSCFG.ini created on the same location

    Common log files to check during troubleshooting


    1. CCMSetup.log (c$\Windows\ccmsetup\Logs) – to monitor the successfull SCCM client installation
    2. client.msi.log (c$\Windows\ccmsetup\Logs) – Records setup tasks performed by client.msi. Can be used to troubleshoot client installation or removal problems

    If installation is success:

    3. ClientLocation.log (c$\Windows\CCM\Log) – to check whether the machine contacting the SCCM management point
    4. ClientIDManagerStartup.log (c$\Windows\CCM\Log) – to check whether the client has valid certificate created to contact SCCM server(s)
    5. ccmeval.log (c$\Windows\CCM\Log) – Client evaluation logs

Leave a Comment and Contact Anoop