[Documentation] Look at creating an AppLocker/WDAC integration article, or at least one just pertaining to Assigned Access.

[The-Paddy]

Prerequisites

• Ensure you write a short, descriptive title after [Bug] above.
• Make sure to search for any existing issues before filing a new one.
• Verify you are able to reproduce the issue with the latest released version

PSAppDeployToolkit version

4.1.0-rc1

Describe the bug

We're using Assigned Access to configure a device for multi app kiosk mode.
When running Start-ADTMsiProcess to install a MSI it automatically tries to run Update-ADTDesktop after the installation. Update-ADTDesktop fails and the script terminates, the MSI however was installed correctly. On the next installation try, it detects that the MSI is already installed, skips Start-ADTMsiProcess and doesn't crash.

After having a quick look at the source, could this have to do with refreshing the desktop and env vars in user context?

I tried using $ErrorActionPreference = "SilentlyContinue" to skip over the error, but wasn't successfull.

Applocker (which is automatically configured by assigned access) logs, that it blocked PSADT.CLIENTSERVER.CLIENT.EXE

This log was from a MSI uninstall. but its the same issue. Sorry for the German error messages :/ If necessary I'll try to switch the computer to English

<![LOG[[Pre-Install] :: Executing [C:\Windows\system32\msiexec.exe /x "{b66b8a46-664b-4ca1-8388-8c74c25fc620}" REBOOT=ReallySuppress /QN /L*V "C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\TeamViewerHost_15.0.8397.0_Uninstall.log"]...]LOG]!><time="14:00:46.302+60" date="7-16-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Execution completed successfully with exit code [0].]LOG]!><time="14:00:48.766+60" date="7-16-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="0" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Refreshing the Desktop and the Windows Explorer environment process block.]LOG]!><time="14:00:48.777+60" date="7-16-2025" component="Update-ADTDesktop" context="NT-AUTORITÄT\SYSTEM" type="1" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Instantiating user client/server process.]LOG]!><time="14:00:48.913+60" date="7-16-2025" component="Invoke-ADTClientServerOperation" context="NT-AUTORITÄT\SYSTEM" type="1" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Failed to refresh the Desktop and the Windows Explorer environment process block.
Error Record:
-------------
 
Message               : Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
InnerException        : System.ComponentModel.Win32Exception (0x80004005): Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten
                           bei PSADT.LibraryInterfaces.AdvApi32.CreateProcessAsUser(SafeHandle hToken, String lpApplicationName, String lpCommandLine, Nullable`1 lpProcessAttributes, Nullable`1 lpThreadAttributes, BOOL bInheritHandles, PROCESS_CREATION_FLAGS dwCreationFlags, SafeEnvironmentBlockHandle lpEnvironment, String lpCurrentDirectory, STARTUPINFOW& lpStartupInfo, PROCESS_INFORMATION& lpProcessInformation) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:Zeile 282.
                           bei PSADT.ProcessManagement.ProcessManager.LaunchAsync(ProcessLaunchInfo launchInfo) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 190.
                           bei PSADT.ClientServer.ServerInstance.Open() in D:\Repos\PSAppDeployToolkit\src\PSADT\PSADT.ClientServer.Server\ServerInstance.cs:Zeile 67.
                           bei CallSite.Target(Closure , CallSite , Object )
 
FullyQualifiedErrorId : Win32Exception,Update-ADTDesktop
ScriptStackTrace      : bei Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 1096
                        bei Update-ADTDesktop<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23745
                        bei Start-ADTMsiProcess<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 20019
                        bei Uninstall-ADTApplication<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23512
                        bei Install-ADTDeployment, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 140
                        bei <ScriptBlock>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 327
                        bei <ScriptBlock>, <Keine Datei>: Zeile 1
 
PositionMessage       : In C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1:20019 Zeichen:17
                        +                 & $Script:CommandTable.'Update-ADTDesktop'
                        +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="14:00:49.046+60" date="7-16-2025" component="Update-ADTDesktop" context="NT-AUTORITÄT\SYSTEM" type="3" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
Error Record:
-------------
 
Message               : Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
InnerException        : System.ComponentModel.Win32Exception (0x80004005): Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten
                           bei PSADT.LibraryInterfaces.AdvApi32.CreateProcessAsUser(SafeHandle hToken, String lpApplicationName, String lpCommandLine, Nullable`1 lpProcessAttributes, Nullable`1 lpThreadAttributes, BOOL bInheritHandles, PROCESS_CREATION_FLAGS dwCreationFlags, SafeEnvironmentBlockHandle lpEnvironment, String lpCurrentDirectory, STARTUPINFOW& lpStartupInfo, PROCESS_INFORMATION& lpProcessInformation) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:Zeile 282.
                           bei PSADT.ProcessManagement.ProcessManager.LaunchAsync(ProcessLaunchInfo launchInfo) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 190.
                           bei PSADT.ClientServer.ServerInstance.Open() in D:\Repos\PSAppDeployToolkit\src\PSADT\PSADT.ClientServer.Server\ServerInstance.cs:Zeile 67.
                           bei CallSite.Target(Closure , CallSite , Object )
 
FullyQualifiedErrorId : Win32Exception,Uninstall-ADTApplication
ScriptStackTrace      : bei Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 1096
                        bei Update-ADTDesktop<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23745
                        bei Start-ADTMsiProcess<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 20019
                        bei Uninstall-ADTApplication<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23512
                        bei Install-ADTDeployment, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 140
                        bei <ScriptBlock>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 327
                        bei <ScriptBlock>, <Keine Datei>: Zeile 1
 
PositionMessage       : In C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1:140 Zeichen:9
                        +         Uninstall-ADTApplication -InstalledApplication $oldTeamViewer ...
                        +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="14:00:49.078+60" date="7-16-2025" component="Uninstall-ADTApplication" context="NT-AUTORITÄT\SYSTEM" type="3" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: An unhandled error within [Invoke-AppDeployToolkit.ps1] has occurred.
Error Record:
-------------
 
Message               : Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
InnerException        : System.ComponentModel.Win32Exception (0x80004005): Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten
                           bei PSADT.LibraryInterfaces.AdvApi32.CreateProcessAsUser(SafeHandle hToken, String lpApplicationName, String lpCommandLine, Nullable`1 lpProcessAttributes, Nullable`1 lpThreadAttributes, BOOL bInheritHandles, PROCESS_CREATION_FLAGS dwCreationFlags, SafeEnvironmentBlockHandle lpEnvironment, String lpCurrentDirectory, STARTUPINFOW& lpStartupInfo, PROCESS_INFORMATION& lpProcessInformation) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:Zeile 282.
                           bei PSADT.ProcessManagement.ProcessManager.LaunchAsync(ProcessLaunchInfo launchInfo) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 190.
                           bei PSADT.ClientServer.ServerInstance.Open() in D:\Repos\PSAppDeployToolkit\src\PSADT\PSADT.ClientServer.Server\ServerInstance.cs:Zeile 67.
                           bei CallSite.Target(Closure , CallSite , Object )
 
FullyQualifiedErrorId : Win32Exception,Uninstall-ADTApplication
ScriptStackTrace      : bei Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 1096
                        bei Update-ADTDesktop<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23745
                        bei Start-ADTMsiProcess<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 20019
                        bei Uninstall-ADTApplication<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23512
                        bei Install-ADTDeployment, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 140
                        bei <ScriptBlock>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1: Zeile 327
                        bei <ScriptBlock>, <Keine Datei>: Zeile 1
 
PositionMessage       : In C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1:140 Zeichen:9
                        +         Uninstall-ADTApplication -InstalledApplication $oldTeamViewer ...
                        +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="14:00:49.104+60" date="7-16-2025" component="Invoke-AppDeployToolkit.ps1" context="NT-AUTORITÄT\SYSTEM" type="3" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\Invoke-AppDeployToolkit.ps1">
<![LOG[[Finalization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] install completed in [4,3206155] seconds with exit code [60001].]LOG]!><time="14:00:49.121+60" date="7-16-2025" component="Close-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="3" thread="3640" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">

Steps to reproduce

1. Configure assigned access
2. Run Start-ADTMsiProcess
3. It installs the MSI and trys to run Update-ADTDesktop
4. Error and script stops

Environment data

OsName               : Microsoft Windows 11 Enterprise
OSDisplayVersion     : 24H2
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-Bit
WindowsVersion       : 2009
WindowsProductName   : Windows 10 Enterprise
WindowsBuildLabEx    : 26100.1.amd64fre.ge_release.240331-1435
OsLanguage           : de-DE
OsMuiLanguages       : {de-DE, en-US}
KeyboardLayout       : de-DE
TimeZone             : (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
HyperVisorPresent    : True
CsPartOfDomain       : True
CsPCSystemType       : Mobile


Host:
  Version:      9.0.7
  Architecture: x64
  Commit:       3c298d9f00
  RID:          win-x64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

[mjr4077au]

Can you please test with a post-RC1 build? They're all available here: https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/actions?query=branch%3Adevelop. There's been some fixes/improvements which might be of help here.

The error is interesting. It's an E_ACCESSDENIED error code, but the text mentions Group Policy? I wonder if there's something specific about kiosk mode that could be causing a block?

[mjr4077au]

@The-Paddy just reading more on this, the issue is likely going to be your allowed app list doesn't have PSADT.ClientServer.Client.exe and PSADT.ClientServer.Client.Launcher.exe within it. The client/server client runs as the user, and the Update-ADTDesktop stuff needs to happen on an active session, which is why it goes through the client/server setup.

[The-Paddy]

Can you please test with a post-RC1 build? They're all available here: https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/actions?query=branch%3Adevelop. There's been some fixes/improvements which might be of help here.

The error is interesting. It's an E_ACCESSDENIED error code, but the text mentions Group Policy? I wonder if there's something specific about kiosk mode that could be causing a block?

Hi @mjr4077au first of all thank you very much for the fast response! I updated my package to the newest PSADT dev version from the commit efa81a9

Unfortunately the issue persists:

<![LOG[-------------------------------------------------------------------------------]LOG]!><time="08:02:04.882+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] install started.]LOG]!><time="08:02:04.898+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] script version is [1.0.0].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] script date is [2025-07-16].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] script author is [user].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [Invoke-AppDeployToolkit.ps1] script version is [4.1.0].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following parameters were passed to [Invoke-AppDeployToolkit.ps1]: [-DeploymentType:'Install' -DeployMode:'Silent'].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module version is [4.1.0].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module imported in [1,7127615] seconds.]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module initialized in [1,3344096] seconds.]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module path is ['C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit'].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] config path is ['C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Config'].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] string path is ['C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Strings'].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] session mode is [Native].]LOG]!><time="08:02:04.914+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Computer Name is [UMPK-GM0AHSJA].]LOG]!><time="08:02:04.929+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current User is [NT-AUTORITÄT\SYSTEM].]LOG]!><time="08:02:04.929+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: OS Version is [Microsoft Windows 11 Business X64 10.0.26100.4351].]LOG]!><time="08:02:04.929+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: OS Type is [WorkStation].]LOG]!><time="08:02:04.929+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Hardware Platform is [Physical].]LOG]!><time="08:02:04.929+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current Culture is [de-DE], language is [DE] and UI language is [DE].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Host is [ConsoleHost] with version [5.1.26100.4202].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Version is [5.1.26100.4202 X64].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Process Path is [C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell CLR (.NET) version is [4.0.30319.42000].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following users are logged on to the system: [domain\user].]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Session information for all logged on users:
 
NTAccount             : domain\user
SID                   : S-1-12-1-2375750110-1335819931-3478429098-550950249
UserName              : user
DomainName            : domain
SessionId             : 1
SessionName           : Console
ConnectState          : WTSActive
IsCurrentSession      : False
IsConsoleSession      : True
IsActiveUserSession   : True
IsUserSession         : True
IsRdpSession          : False
IsLocalAdmin          : False
IsLocalAdminException : 
LogonTime             : 17.07.2025 07:56:08
IdleTime              : 155060.07:02:03.9178724
DisconnectTime        : 
ClientName            : 
ClientProtocolType    : Console
ClientDirectory       : 
ClientBuildNumber     :
]LOG]!><time="08:02:04.934+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current process is running under a system account [NT-AUTORITÄT\SYSTEM].]LOG]!><time="08:02:04.945+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following user is the console user [domain\user] (user with control of physical monitor, keyboard, and mouse).]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The active logged on user who will receive UI elements is [domain\user].]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The current execution context has a primary UI language of [de-DE].]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following locale was used to import UI messages from the strings.psd1 files: [de-DE].]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Unable to find COM object [Microsoft.SMS.TSEnvironment]. Therefore, script is not currently running from a SCCM Task Sequence.]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Device has completed the OOBE and toolkit is not running with an active ESP in progress.]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Session 0 detected but deployment mode was manually set to [Silent].]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: No processes were specified as requiring closure.]LOG]!><time="08:02:04.946+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Installation is running in [Silent] mode.]LOG]!><time="08:02:04.976+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Deployment type is [Install].]LOG]!><time="08:02:04.992+60" date="7-17-2025" component="Open-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Module [PSAppDeployToolkit.Extensions] imported successfully.]LOG]!><time="08:02:05.045+60" date="7-17-2025" component="PSAppDeployToolkit.Extensions.psm1" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit.Extensions\PSAppDeployToolkit.Extensions.psm1">
<![LOG[[Pre-Install] :: Checking if old TeamViewer Host is installed...]LOG]!><time="08:02:05.055+60" date="7-17-2025" component="Install-ADTDeployment" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1">
<![LOG[[Pre-Install] :: Getting information for installed applications matching the provided FilterScript...]LOG]!><time="08:02:05.071+60" date="7-17-2025" component="Get-ADTApplication" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Found no application based on the supplied FilterScript.]LOG]!><time="08:02:05.150+60" date="7-17-2025" component="Get-ADTApplication" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: No old TeamViewer Host found]LOG]!><time="08:02:05.150+60" date="7-17-2025" component="Install-ADTDeployment" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1">
<![LOG[[Install] :: Starting install with CUSTOMCONFIGID=$hidden]LOG]!><time="08:02:05.157+60" date="7-17-2025" component="Install-ADTDeployment" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1">
<![LOG[[Install] :: Executing MSI action [Install]...]LOG]!><time="08:02:05.181+60" date="7-17-2025" component="Start-ADTMsiProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Reading data from Windows Installer database file [C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Files\TeamViewer_Host.msi] in table [Property].]LOG]!><time="08:02:05.217+60" date="7-17-2025" component="Get-ADTMsiTableProperty" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Getting information for installed applications...]LOG]!><time="08:02:05.719+60" date="7-17-2025" component="Get-ADTApplication" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Found no application based on the supplied FilterScript.]LOG]!><time="08:02:05.735+60" date="7-17-2025" component="Get-ADTApplication" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Preparing to execute process [C:\Windows\system32\msiexec.exe]...]LOG]!><time="08:02:05.800+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Checking to see if mutex [Global\_MSIExecute] is available. Wait up to [10 minute(s)] for the mutex to become available.]LOG]!><time="08:02:05.821+60" date="7-17-2025" component="Test-ADTMutexAvailability" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Mutex [Global\_MSIExecute] is available for an exclusive lock.]LOG]!><time="08:02:05.823+60" date="7-17-2025" component="Test-ADTMutexAvailability" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: CreateNoWindow not specified, StdOut/StdErr streams will not be available.]LOG]!><time="08:02:06.841+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Working Directory is [C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Files].]LOG]!><time="08:02:06.852+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Executing [C:\Windows\system32\msiexec.exe (Parameters Hidden)]...]LOG]!><time="08:02:06.854+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Executed [C:\Windows\system32\msiexec.exe (Parameters Hidden)], awaiting completion...]LOG]!><time="08:02:06.897+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Execution completed successfully with exit code [0].]LOG]!><time="08:02:11.074+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="0" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: StdOut Output from Execution: N/A]LOG]!><time="08:02:11.083+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: StdErr Output from Execution: N/A]LOG]!><time="08:02:11.083+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Interleaved Output from Execution: N/A]LOG]!><time="08:02:11.083+60" date="7-17-2025" component="Start-ADTProcess" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Refreshing the Desktop and the Windows Explorer environment process block.]LOG]!><time="08:02:11.099+60" date="7-17-2025" component="Update-ADTDesktop" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Instantiating user client/server process.]LOG]!><time="08:02:11.242+60" date="7-17-2025" component="Invoke-ADTClientServerOperation" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: Failed to refresh the Desktop and the Windows Explorer environment process block.
Error Record:
-------------
 
Message               : Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
InnerException        : System.ComponentModel.Win32Exception (0x80004005): Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten
                           bei PSADT.LibraryInterfaces.AdvApi32.CreateProcessAsUser(SafeHandle hToken, String lpApplicationName, String lpCommandLine, Nullable`1 lpProcessAttributes, Nullable`1 lpThreadAttributes, BOOL bInheritHandles, PROCESS_CREATION_FLAGS dwCreationFlags, SafeEnvironmentBlockHandle lpEnvironment, String lpCurrentDirectory, STARTUPINFOW& lpStartupInfo, PROCESS_INFORMATION& lpProcessInformation) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:Zeile 279.
                           bei PSADT.ProcessManagement.ProcessManager.CreateProcessUsingToken(SafeFileHandle hPrimaryToken, String commandLine, Boolean usingAnonymousHandles, PROCESS_CREATION_FLAGS creationFlags, SafeEnvironmentBlockHandle lpEnvironment, String workingDirectory, STARTUPINFOW& startupInfo, PROCESS_INFORMATION& pi) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 733.
                           bei PSADT.ProcessManagement.ProcessManager.LaunchAsync(ProcessLaunchInfo launchInfo) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 207.
                           bei PSADT.ClientServer.ServerInstance.Open() in C:\Repos\PSAppDeployToolkit\src\PSADT\PSADT.ClientServer.Server\ServerInstance.cs:Zeile 67.
                           bei CallSite.Target(Closure , CallSite , Object )
 
FullyQualifiedErrorId : Win32Exception,Update-ADTDesktop
ScriptStackTrace      : bei Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 1124
                        bei Update-ADTDesktop<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23966
                        bei Start-ADTMsiProcess<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 20079
                        bei Install-ADTDeployment, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1: Zeile 168
                        bei <ScriptBlock>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1: Zeile 328
                        bei <ScriptBlock>, <Keine Datei>: Zeile 1
 
PositionMessage       : In C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1:20079 Zeichen:17
                        +                 & $Script:CommandTable.'Update-ADTDesktop'
                        +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="08:02:11.422+60" date="7-17-2025" component="Update-ADTDesktop" context="NT-AUTORITÄT\SYSTEM" type="3" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Install] :: An unhandled error within [Invoke-AppDeployToolkit.ps1] has occurred.
Error Record:
-------------
 
Message               : Ausnahme beim Aufrufen von "Open" mit 0 Argument(en):  "Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten"
InnerException        : System.ComponentModel.Win32Exception (0x80004005): Dieses Programm wurde durch eine Gruppenrichtlinie geblockt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten
                           bei PSADT.LibraryInterfaces.AdvApi32.CreateProcessAsUser(SafeHandle hToken, String lpApplicationName, String lpCommandLine, Nullable`1 lpProcessAttributes, Nullable`1 lpThreadAttributes, BOOL bInheritHandles, PROCESS_CREATION_FLAGS dwCreationFlags, SafeEnvironmentBlockHandle lpEnvironment, String lpCurrentDirectory, STARTUPINFOW& lpStartupInfo, PROCESS_INFORMATION& lpProcessInformation) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:Zeile 279.
                           bei PSADT.ProcessManagement.ProcessManager.CreateProcessUsingToken(SafeFileHandle hPrimaryToken, String commandLine, Boolean usingAnonymousHandles, PROCESS_CREATION_FLAGS creationFlags, SafeEnvironmentBlockHandle lpEnvironment, String workingDirectory, STARTUPINFOW& startupInfo, PROCESS_INFORMATION& pi) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 733.
                           bei PSADT.ProcessManagement.ProcessManager.LaunchAsync(ProcessLaunchInfo launchInfo) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\ProcessManagement\ProcessManager.cs:Zeile 207.
                           bei PSADT.ClientServer.ServerInstance.Open() in C:\Repos\PSAppDeployToolkit\src\PSADT\PSADT.ClientServer.Server\ServerInstance.cs:Zeile 67.
                           bei CallSite.Target(Closure , CallSite , Object )
 
FullyQualifiedErrorId : Win32Exception,Start-ADTMsiProcess
ScriptStackTrace      : bei Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 1124
                        bei Update-ADTDesktop<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 23966
                        bei Start-ADTMsiProcess<Process>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1: Zeile 20079
                        bei Install-ADTDeployment, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1: Zeile 168
                        bei <ScriptBlock>, C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1: Zeile 328
                        bei <ScriptBlock>, <Keine Datei>: Zeile 1
 
PositionMessage       : In C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1:168 Zeichen:5
                        +     Start-ADTMsiProcess -Action "Install" -FilePath "TeamViewer_Host. ...
                        +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="08:02:11.461+60" date="7-17-2025" component="Invoke-AppDeployToolkit.ps1" context="NT-AUTORITÄT\SYSTEM" type="3" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\Invoke-AppDeployToolkit.ps1">
<![LOG[[Finalization] :: [TeamViewer_TeamViewerHost_15.67.5.0_x64_EN_01] install completed in [6,592573] seconds with exit code [60001].]LOG]!><time="08:02:11.477+60" date="7-17-2025" component="Close-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="3" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[-------------------------------------------------------------------------------]LOG]!><time="08:02:11.477+60" date="7-17-2025" component="Close-ADTSession" context="NT-AUTORITÄT\SYSTEM" type="1" thread="8024" file="C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\PSAppDeployToolkit\PSAppDeployToolkit.psm1">

@The-Paddy just reading more on this, the issue is likely going to be your allowed app list doesn't have PSADT.ClientServer.Client.exe and PSADT.ClientServer.Client.Launcher.exe within it. The client/server client runs as the user, and the Update-ADTDesktop stuff needs to happen on an active session, which is why it goes through the client/server setup.

Okay thank you - that's what I expected (and that matches with the AppLocker log). Until now I was quite unsuccessful trying to implement additional AppLocker rules in combination with the automatic ones from assigned access.
My current understanding (documentation) is that you can only use paths in the assigned access XML, but the paths where Intune downloads the packages are dynamic... (C:\Windows\IMECache\a3fd3a20-32e3-46a8-97e7-9a10012eff24_4\)

[mjr4077au]

Thanks for testing. It was past midnight when I responded to you and it didn't click until my second message that this was an AppLocker thing that was being reported.

Regarding the extra rules, maybe we can work together to try and get a ruleset going that works in conjunction with Assigned Access for you. The IMECache path is dynamic, but AppLocker does allow path wildcards so C:\Windows\IMECache\*\PSAppDeployToolkit\lib\*.exe should work. You could also trust Patch My PC's certificate that's used to sign off the executables. You can use the convenience-provided public key in the root of the module folder.

[The-Paddy]

I tried adding <App DesktopAppPath="%windir%\IMECache\*\PSAppDeployToolkit\lib\*.exe" /> to my assigned access XML but that does nothing and afterwards I can't find it in the generated AppLocker config (C:\Windows\System32\AppLocker\MDM\LoooongID\AppLocker\ApplicationLaunchRestrictions\AssignedAccess_MultiApp\Exe\Policy)

I also tried configuring the Intune agent as Managed Installer (manually via the XML, not for the whole tenant) but could get it to deploy via Intune (error code: -2016345596 / 0x87d10204)

<?xml version="1.0"?>
<AppLockerPolicy Version="1">
    <RuleCollection Type="Dll" EnforcementMode="AuditOnly">
        <FilePathRule Id="86f235ad-3f7b-4121-bc95-ea8bde3a5db5" Name="Dummy Rule" Description="" UserOrGroupSid="S-1-1-0" Action="Deny">
            <Conditions>
                <FilePathCondition Path="%OSDRIVE%\ThisWillBeBlocked.dll" />
            </Conditions>
        </FilePathRule>
        <RuleCollectionExtensions>
            <ThresholdExtensions>
                <Services EnforcementMode="Enabled" />
            </ThresholdExtensions>
            <RedstoneExtensions>
                <SystemApps Allow="Enabled" />
            </RedstoneExtensions>
        </RuleCollectionExtensions>
    </RuleCollection>

    <RuleCollection Type="Exe" EnforcementMode="AuditOnly">
        <FilePathRule Id="9420c496-046d-45ab-bd0e-455b2649e41e" Name="Dummy Rule" Description="" UserOrGroupSid="S-1-1-0" Action="Deny">
            <Conditions>
                <FilePathCondition Path="%OSDRIVE%\ThisWillBeBlocked.exe" />
            </Conditions>
        </FilePathRule>
        <RuleCollectionExtensions>
            <ThresholdExtensions>
                <Services EnforcementMode="Enabled" />
            </ThresholdExtensions>
            <RedstoneExtensions>
                <SystemApps Allow="Enabled" />
            </RedstoneExtensions>
        </RuleCollectionExtensions>
    </RuleCollection>

    <RuleCollection Type="ManagedInstaller" EnforcementMode="AuditOnly">
        <FilePublisherRule Id="3cf97403-1b4a-4492-8e70-98436cf78983" Name="MICROSOFT.MANAGEMENT.SERVICES.INTUNEWINDOWSAGENT.EXE version 1.37.200.8 exactly in MICROSOFT INTUNE from O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US" Description="2" UserOrGroupSid="S-1-1-0" Action="Allow">
            <Conditions>
                <FilePublisherCondition PublisherName="O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US" ProductName="*" BinaryName="MICROSOFT.MANAGEMENT.SERVICES.INTUNEWINDOWSAGENT.EXE">
                    <BinaryVersionRange LowSection="1.37.200.8" HighSection="*" />
                </FilePublisherCondition>
            </Conditions>
        </FilePublisherRule>
    </RuleCollection>
</AppLockerPolicy>

On one deployment the script continued after one Update-ADTDesktop but still stopped after the second one (I have no idea why)...
Im beginning to run out of ideas, tomorrow I'll try allowlisting the PSADT executables directly via AppLocker.

Any chance to skip the Update-ADTDesktop after the Start-ADTMsiProcess?

[mjr4077au]

Hi @The-Paddy, just checking in with you to see how you've gone with the AppLocker stuff?

Any chance to skip the Update-ADTDesktop after the Start-ADTMsiProcess?

The problem with skipping over it is that it's just sweeping the underlying issue under the carpet. It might resolve your issue today, but what happens tomorrow when you require an interactive deployment with deferrals or apps to close and AppLocker gets in the way?

[The-Paddy]

Hi @mjr4077au,
I tried some things but couldn't solve it yet :(

I tried a explicit AppLocker allow policy for the PSADT Exes. That was successfully deploy but didn't change anything on the client. AppLocker logs one allow and one deny event. I think the auto generated AppLocker rules from assigned access trump my allow rule.
OMA-URI ./Vendor/MSFT/AppLocker/ApplicationLaunchRestrictions/apps/EXE/Policy

<RuleCollection Type="Exe" EnforcementMode="AuditOnly">
  <FilePublisherRule Id="ac9ed572-cca0-450b-ab07-a468a0fe9b85"
    Name="Signiert von O=PATCH MY PC, LLC, L=CASTLE ROCK, S=COLORADO, C=US"
    Description=""
    UserOrGroupSid="S-1-1-0" Action="Allow">
    <Conditions>
      <FilePublisherCondition
        PublisherName="O=PATCH MY PC, LLC, L=CASTLE ROCK, S=COLORADO, C=US"
        ProductName="*" BinaryName="*">
        <BinaryVersionRange LowSection="*" HighSection="*" />
      </FilePublisherCondition>
    </Conditions>
  </FilePublisherRule>
</RuleCollection>

I tried editing the assigned access XML, so there's only one wildcard in the path, but that also didn't change anything
<App DesktopAppPath="%windir%\IMECache\*" />

Currently I'm thinking about hardcoding the paths to the PSADT Exes in the assigned access XML. The Intune AppID in the path is always the same... or not using PSADT for this deployment.

The problem with skipping over it is that it's just sweeping the underlying issue under the carpet. It might resolve your issue today, but what happens tomorrow when you require an interactive deployment with deferrals or apps to close and AppLocker gets in the way?

I think the problem is the way assigned access handels the generation of AppLocker rules and not AppLocker per se... (I'm definitely not a AppLocker expert, so I'm really not sure)

[mjr4077au]

I'm sufficiently good with AppLocker so I'll try to help where I can, but I've not played with Assigned Access and I won't have time to set up a lab for this for some time.

I think the next step would be to dump out the AppLocker rules that Assigned Access sets up and evaluate what it denies so we can do something a bit more targeted.

If you'd like to discuss and review this with a bit more privacy, I can be reached on Discord using the same username I use here.

[The-Paddy]

I guess the files in C:\Windows\System32\AppLocker would be a good start?

I added you on Discord

[mjr4077au]

I've added -NoDesktopRefresh to Start-ADTMsiProcess via PSAppDeployToolkit/PSAppDeployToolkit@b0d89ee. It obviously doesn't address the underlying AppLocker issue, but it greases the wheels for this particular issue. We'll capitalise on this issue so that maybe we can have an AppLocker integration article, or at least an article on what specialised setup's needed to have your own AppLocker rules alongside Assigned Access.

Updated build with this commit is currently baking: https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/actions/runs/16372847722. Give it ~10-15 minutes.