Keep third party apps updated/patched using the power of Chocolately combined with user interaction from the PowerShell App Deployment Toolkit and ServiceUI, deployed through Intune.


Third party application patching (Adobe Reader for example) with Intune standalone is no mean feat without ConfigMgr Co-Management. Reporting (inventory) in Intune is still limited and there is no third party catalog import ability (CAB files) like in ConfigMgr, so usually custom solutions are needed if embarking on a modern desktop implementation. However, there are some 3rd party solutions now available if you want a non-Microsoft based solution.

In this short post, I wanted to show you how I kept applications updated and patched with the Chocolatey Nuget package manager (Free version).

Note: If you use the Business edition (paid) or better, then you can also manage and update applications installed outside of Chocolatey - so ones that the IT folk with local admin have installed manually!

These are the core components in use in this solution:


You can use the free version for this, but using the Business edition is preferable, as you can take apps installed outside of Chocolatey back under the choco management and therefore patch them - this is a really great feature of Chocolatey in my opinion.


To set the scene, this is the environment the Chocolatey patching will work well in:

  • As we’re using the free version of Chocolatey in this example, you will have already setup many apps to be installed through Chocolatey, publishing them as available in the Company Portal using Intune.
  • Apps are made available and use a Chocolatey PowerShell script to always install the latest version - this means the detection method (custom script detection) will still work, even if the apps are updated and the deployment is set to required.
  • These apps will now be out of date as they are not automatically updating and/or the users don’t have local admin rights if they are installed in the system context.

Intune app install scripts

An example of PowerShell scripts I used to install apps using Chocoately, deployed through Intune. Note: These are not the scripts used for patching the existing apps:

Getting Started

So now you want to patch/update all of your apps using Chocolatey, through Intune.


Grab a copy of the latest PSADT and lets start to edit the Deploy-Application.ps1, or you can grab my ready made copy and skip this PSADT section.


In the PRE-INSTALLATION section, we’ll add a check to see if Chocolatey is installed and install if it’s not. At the time, Win32 dependencies weren’t available in Intune.

[string]$installPhase = 'Pre-Installation'
# Check if Chocolatey is installed and if not, install it.
If ( get-command -Name choco.exe -ErrorAction SilentlyContinue ){
  $ChocoExe = "choco.exe"
} elseif (test-path -Path (Join-Path -path $Env:ALLUSERSPROFILE -ChildPath "Chocolatey\bin\choco.exe")) {
  $ChocoExe = Join-Path -path $Env:ALLUSERSPROFILE -ChildPath "Chocolatey\bin\choco.exe"
} else {
  try {
    Write-Log -Message "Starting to install chocolatey...." -Severity 1 -Source $deployAppScriptFriendlyName
    Invoke-Expression ((New-Object -TypeName net.webclient).DownloadString('')) -ErrorAction Stop
    choco feature enable -n allowGlobalConfirmation
    $ChocoExe = Join-Path -path $Env:ALLUSERSPROFILE -ChildPath "Chocolatey\bin\choco.exe"
  catch {
    Write-Log -Message "Failed to install Chocolatey" -Severity 3 -Source $deployAppScriptFriendlyName
    Throw "Failed to install Chocolatey"

Now for the key component, the check for the outdated apps. Choco will scan the existing installations (in the free version, only the apps that were previously installed with Choco).

Once we have a list of outdated applications that can be updated through choco, throw a default PSADT popup with a pre-populated list of common apps that should be closed:


Optionally allow the user to defer:


and then the list of apps to be updated:


# Check if any packages actually need updating
$OutdatedList = & $ChocoExe outdated --limit-output
If(($OutdatedList -gt 0)-and(-not($OutdatedList -like "*Error*"))){

  Write-Log -Message "Chocolatey packages needing updates: [$($OutdatedList.Count)]" -Severity 1 -Source $deployAppScriptFriendlyName

  ## Show Welcome Message, close Internet Explorer if required, allow up to 3 deferrals, verify there is enough disk space to complete the install, and persist the prompt
  Show-InstallationWelcome -CloseApps 'Outlook=Microsoft Outlook,winword=Microsoft Office Word,excel=Microsoft Office Excel,VISIO=Visio,ONENOTE=OneNote,POWERPNT=Microsoft PowerPoint,MSPUB=Microsoft Publisher,AcroRd32=Adobe Reader' -AllowDefer -DeferTimes 3 -CheckDiskSpace -PersistPrompt -BlockExecution
  # 'Outlook=Microsoft Outlook,winword=Microsoft Office Word,excel=Microsoft Office Excel,VISIO=Visio,ONENOTE=OneNote,POWERPNT=Microsoft PowerPoint,MSPUB=Microsoft Publisher,AcroRd32=Adobe Reader'
  ## Show Progress Message (with the default message)
            $ListFormatted = $OutdatedList | % { `
                    [pscustomobject]@{ `
                        Name = ($_ -split '\|')[0]; `
                        NewVersion = ($_ -split '\|')[2] `
                    } `
            Show-InstallationProgress -StatusMessage "Installation in progress...`n$($ListFormatted | % {"`n$($_.Name), $($_.NewVersion)"})"


This code is actually a continuation of the above, so you’ll need the whole lot otherwise the braces {} won’t equate.

Here we are initiating the upgrade of all the outdated apps and finally displaying a message with either the succesfully installed or app that failed to upgrade:


## <Perform Installation tasks here>
If ($ChocoExe){
  Write-Log -Message "Starting Choco installs..." -Severity 1 -Source $deployAppScriptFriendlyName		
  Execute-Process -Path $ChocoExe -Parameters 'upgrade all --confirm'
          #Show-InstallationProgress -StatusMessage "Some apps attempted install..."

  start-sleep 5
  $FailedList = & $ChocoExe outdated --limit-output
  Write-Log -Message "Failed apps: [$($FailedList.Count)]" -Severity 1 -Source $deployAppScriptFriendlyName		
  If($FailedList -gt 0){
              $FailedListFormatted = $FailedList | % { `
                  [pscustomobject]@{ `
                      Name = ($_ -split '\|')[0]; `
                      CurrentVersion = ($_ -split '\|')[1]; `
                  } `
              Show-InstallationPrompt -Message "The follow apps could not be updated: `n$($FailedListFormatted | % {"`n$($_.Name), $($_.CurrentVersion)"}) `n`nThe installation will retry again later." -ButtonRightText 'OK' -Icon Warning -NoWait
          } else {
              Show-InstallationPrompt -Message "Apps succesfully updated: `n$($ListFormatted | % {"`n$($_.Name), $($_.NewVersion)"})" -ButtonRightText 'OK' -Icon Information -NoWait


} else {

  Write-Log -Message "No Chocolatey packages determined as needing to be updated" -Severity 2 -Source $deployAppScriptFriendlyName



There are a few moving parts to this so lets have an explanation of the remaining files (that can be found in the download link at the bottom of this post).

  • Install.cmd - calls the Deploy-Application.exe using the ServiceUI.exe (Part of the Microsoft Deployment Toolkit (MDT)). This should be in the same folder as the PSADT.
  • ServiceUI.exe - called by above Install.cmd
  • ChocoPackageUpdates-ScheduledTask.ps1 - creates a local scheduled task to run monthly or quaterly, and copies the PSADT folder contents locally. The task calls the Install.cmd when it’s run.
  • Detection-Rule-Monthly.ps1 and Detection-Rule-Quarterly.ps1 - Don’t deploy these to the endpoints as they are the scripts that I used for the detection method in Intune - they detect if the Scheduled Task exists.


In this solution, we have one Azure AD Group for monthly updates (IT/Dev/Test machines), and another for quarterly updates (Rest of the business) - you can of course expand this to be more granular using more Scheduled Tasks.

The app contents is detailed above. Create it with your IntuneWinAppUtil.exe wrapper.

Deploy the monthly servicing app to the Azure AD group with your pilot machines using install cmdline:

powershell.exe ChocoPackageUpdates-ScheduledTask.ps1 -Release Monthly

And the quarterly servicing:

powershell.exe ChocoPackageUpdates-ScheduledTask.ps1 -Release Quarterly

Scripts Download

All the files/scripts used are available for download on my Github repo.