Beginning with SCCM 1810, you can now repair an application directly from
Now, you can directly initiate a Repair action in Software Center. The good
- Upgrade to SCCM 1810
- Add a repair command line to your application
- Check the Repair option in your application deployments
If you haven’t
Add SCCM repair command line
The first thing you need to do to have the SCCM application repair option is to add your repair command line in your application.
- In the SCCM Console
- Select the desired application, select the deployment type and go to the Properties
- In the Program tab, specify the command to repair the application in the new box
You’ll have to find the silent switch for repairing your application as for the installation switches.
If you have an MSI, it will look like this :
https://www.advancedinstaller.com/user-guide/msiexec.html
Add the repair option in the SCCM Deployment
Once the application has a repair command line, we can add the option in the deployment
- In the SCCM Console
- Create a new deployment for your application
- In the General tab, select your software and collection
- In the content tab, ensure that your application is distributed, click Next
- In the Deployment S
ettings tab, select Allow end users to attempt to repair this application
- In the Scheduling tab, select the desired schedule
- In the User Experience tab, select the desired options
- In the Alerts tab, select the Alerts options
In the Completion tab, you can see the repair option has been enabled
Test SCCM Repair Application on Client
Let’s see the results on an SCCM client
- Launch the Software Center
- On our test client, 7zip has already been installed
- Click on the application, a new Repair button is available
- Once initiated, the repair command line is launched.
- You can see the repair results in the AppEnforce log file.
A small but awesome new feature !
11 Comments on “Repair Application from Software Center using SCCM 1810+”
Don’t make excuses for failure, just find a way for success
Dolu Hasar tamiri sistemleri ve Sunroof tamiri
A Yelp study shows that if someone had a good customer service experience
Will the app still repair for users who have limited (no) rights to the local ccmcache folder?
So if an .MSI needs to write files to the user profile %AppData%\Roaming\appname will they repair achieve this function?
Is it possible to remotely run the repair command on behalf of the user? for example – I do not want to ability for users to repair their own applications, however want to give this permission to 1st Line Support who have limited access to SCCM.
I don ‘t seem to be able to create new deployments with powershell to include this feature. Anyone knows how to create/modify an app deployment that includes this parameter?
Start-CMApplicationDeployment or Set-CMApplicationDeployment or New-CMApplicationDeployment don’t seem to have this parameter…
Discovered a bit of a bug with the repair. If you run a batch file script, then the end user (non-admin) has the ability to Ctrl+C out of it and end up with an elevated command prompt. Surely MS could have included the option to run REPAIR as hidden as well as the installation/uninstall?
Do you also know the Powershell command / parameter for the Repair Option? Thank you
What about that C2R Office installer, whats the magic /switch to repair that one?
This info worked for me:
https://blogs.technet.microsoft.com/odsupport/2014/08/12/office-click-to-run-command-lines-to-automate-a-quick-and-online-repair-in-office-2013/
Command is:
“C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe” scenario=Repair platform=x86 culture=en-us forceappshutdown=True RepairType=QuickRepair DisplayLevel=False
Worked for my 2016 C2R deployment
Pingback: Blog: Repair Application from Software Center using SCCM 1810+ | SCCM Tips