For those that had not seen, v4.1.8 was released yesterday:
Thanks to the PSADT team, I think those MSI / MSP improvements will help me 
4 Likes
I assume this new version will appear in the PowerShellGallery after some "Microsoft time" has passed 
Currently still showing v4.1.7:
PSAppDeployToolkit already in latest version: 4.1.7 - Release date: 10/21/2025 12:25:39
Have you encountered the silent deployment issue I have? If the app it isnt running, it switches to silent automatically which is what I dont want.
replied in other thread (4.1.8 Running in silent mode when logged on - #2 by Adrian_Scott)
1 Like
Using 4.1.7, I had to add the conditional script below to work in Task Sequence and Software Center using "Invoke-AppDeployToolkit.exe -DeploymentType Install" in SCCM without -DeployMode.
In the new 4.1.8, is this still necessary or has it been addressed? as in previous versions (e.g. 3.9.3) where it was not needed but worked by just running "Deploy-Application.exe" Install (or Uninstall).
if ($env:_SMSTSInTaskSequence -eq "true" -or $env:_SMSTSLaunchMode -ne "SMS") {
$adtSession.NoProcessDetection = $true # running within an active Task Sequence (OSD, PXE, media, etc.)
}
else {
$adtSession.NoProcessDetection = $false # running in the Software Center
}
What issue were you trying to solve with this?
without a conditional script, installing via Software Center with "Invoke-AppDeployToolkit.exe -DeploymentType Install" set in SCCM, seems to work but no prompt message will appear (close running processes, deferral, etc.). The installation on Task sequence is also successful.
Using "Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Interactive", the installation fails via Task sequence. It succeeds in Software Center and the prompt message appears.
That sounds like it's working as it should. In its default run mode without NoProcessDetection = $false specified, it'll default to silent if there's processes to close specified that aren't running.
Specifying Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Interactive says that you're explicitly wanting interactive mode no matter what, which is likely why you're receiving a failure. Is this an in-Windows task sequence, or during OSD?
You're not the first person to mention such a scenario. A lot of people thought PSADT had some kind of automagic to make such a setup work (silent in a TS, interactive via software centre). The reality is that it didn't, it just happened to test whether the PowerShell process was interactive (it is via software centre, but isn't via a TS). The problem is that PSADT doesn't need the process to be interactive anymore with our new client/server process. This is what makes it work via Intune without ServiceUI, etc.
Someone's raised [Feature] A cmdlet that returns if the process was run as available or required · Issue #1946 · PSAppDeployToolkit/PSAppDeployToolkit · GitHub which could be a good way to handle this, the problem is that short of setting up my own lab, I don't have access to ConfigMgr to develop such a solution and test it. We'll see what we can do for 4.2.0 though.
1 Like