V4.1.5 Show-ADTInstallationPrompt Pre-test Runas Admin problems

I know I'm annoying, since it works fine via SCCM Agent or Intune Agent, I would just be grateful if there was a solution, as this makes the pre-check easier and worked before 4.1.3

I can't always test all the important options when you make improvements so quickly, sorry
I stopped testing it under SCCM in 4.1.2 and later, as I had to use Intune primarily.

  • With 4.1.3, without -AppProcessesToClose, I was able to test it without errors.
  • With 4.1.4, I didn't have Show-ADTInstallationPrompt, but -AppProcessesToClose worked without errors.
  • With 4.1.5, -AppProcessesToClose works via RunAS Admin.

I usually test beforehand using a normal user and run the installation via CMD as an administrator. The normal user is necessary because only they have the rights to add-ons if functional testing of the software is necessary.

  • With SCCM, I can live with it if I have to, as I can correct issues relatively quickly.
  • With Intune, it's always more time-consuming and requires patience until it's available (depending on the hairdryer, it takes 3-x hours).
  • Currently, I'm not allowed to test Autopilot Required yet.

It's the same in all versions:
nur Deutsch

if ($MyLanguage -like "de-DE" -or $currentUILanguage -like "de\*" )
{
$MyMessage="Bitte Outlook starten, Installation abgeschlossen"
}

nur French

if ($MyLanguage -like "fr-Fr" -or $currentUILanguage -like "fr\*" )
{
$MyMessage="Veuillez démarrer Outlook, installation terminée"
}

if ($MyLanguage -ne "de-DE" -and $MyLanguage -ne "fr-Fr" -and $currentUILanguage -ne "DE" -and $currentUILanguage -ne "Fr") {$MyMessage="noLanguage"}

if ($RunAsActiveUser) {if (!$adtSession.UseDefaultMsi) {Show-ADTInstallationPrompt -Message $MyMessage -ButtonRightText 'OK' -Icon Information -NoWait} }

I tried different things

$MyUser=$RunAsActiveUser.Username
V1 if ($MyUser) {if (!$adtSession.UseDefaultMsi) {Show-ADTInstallationPrompt -Message $MyMessage -ButtonRightText 'OK' -Icon Information -NoWait} }
V2 if ($MyUser) {Show-ADTInstallationPrompt -Message $MyMessage -ButtonRightText 'OK' -Icon Information -NoWait}
V3 Show-ADTInstallationPrompt -Message $MyMessage -ButtonRightText 'OK' -Icon Information -NoWait

always the same error

per RunAS Admin:

\[Post-Install\] :: The calling account \[xxx\\xxx\] is running interactively, but not as the logged on user and is missing the permission(s) \['SeAssignPrimaryTokenPrivilege'\] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations.	Get-ADTClientServerUser	10.09.2025 15:16:35	5144 (0x1418)
\[Post-Install\] :: Could not find a valid logged on user session for \[xxx\\xxx\].
Error Record:

Message               : Could not find a valid logged on user session for \[xxx\\xxx\].
 FullyQualifiedErrorId : NoActiveUserError,Start-ADTProcessAsUser
ScriptStackTrace      : bei Start-ADTProcessAsUser, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 22714
                        bei Private:Invoke-ADTClientServerOperation, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 1430
                        bei Show-ADTInstallationPrompt, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 18357
                        bei Install-ADTDeployment, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\Invoke-AppDeployToolkit.ps1: Zeile 382
                        bei , C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\Invoke-AppDeployToolkit.ps1: Zeile 576
                        bei , : Zeile 1
 TargetObject          : Value
                        -----
                        xxxx\\xxxx
 PositionMessage       : In C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1:1430 Zeichen:17
                        + ...             & $Script:CommandTable.'Start-ADTProcessAsUser' @sapauParsapauParsapauParsapauPar ...
                        +                 \~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~
Start-ADTProcessAsUser	10.09.2025 15:16:36	5144 (0x1418)
\[Post-Install\] :: An unhandled error within \[Invoke-AppDeployToolkit.ps1\] has occurred.
Error Record:

Message               : Could not find a valid logged on user session for \[xxx\\xxx\].
 FullyQualifiedErrorId : NoActiveUserError,Show-ADTInstallationPrompt
ScriptStackTrace      : bei Start-ADTProcessAsUser, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 22714
                        bei Private:Invoke-ADTClientServerOperation, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 1430
                        bei Show-ADTInstallationPrompt, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\PSAppDeployToolkit\\PSAppDeployToolkit.psm1: Zeile 18357
                        bei Install-ADTDeployment, C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\Invoke-AppDeployToolkit.ps1: Zeile 382
                        bei , C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\Invoke-AppDeployToolkit.ps1: Zeile 576
                        bei , : Zeile 1
 TargetObject          : Value
                       -----
                        xxx\\xxx
 PositionMessage       : In C:\\Temp\\101160-Harmonie-365x64 10.7.10006 EN 4.1.5\\Invoke-AppDeployToolkit.ps1:382 Zeichen:5
                        +     Show-ADTInstallationPrompt -Message $MyMessage -ButtonRightText ' ...
                        +     \~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~\~
Invoke-AppDeployToolkit.ps1	10.09.2025 15:16:36	5144 (0x1418)

You can only run a process as a user if that user is logged onto the device. Is the username you're passing to Start-ADTProcessAsUser that of a logged on user?

It's supposed to be a per-machine installation. I'm logged in normally and running it as an administrator via cmd. This is a preliminary test before I integrate it into SCCM or Intune and have it installed via agent. This worked fine up to 4.0.6. I couldn't run it this way with 4.1.4 and 4.1.5.

Can you please provide the full log file so it can be interrogated? Based on what I'm seeing, its just not possible for your problem to occur.

Take these two lines of the codebase: PSAppDeployToolkit/src/PSAppDeployToolkit/Private/Get-ADTClientServerUser.ps1 at 9c023f11b6a1b6454409b6c3f0a0122baaa48d94 · PSAppDeployToolkit/PSAppDeployToolkit · GitHub. We can see that it prints the "is running interactively, but not as the logged on user and is missing the permission(s)" warning, then immediately returns an object for use with client/server operations.

As such, I just cannot see how you're receiving an error like "Could not find a valid logged on user session for [xxx\xxx]."

I will rebuild and simplify it, but under Runas it always runs into an error with Show-ADTInstallationPrompt so I cover both SCCM/Intune
As already mentioned, with SCCM Agent/Intune Agent, version PSADT 4.1.5 worked without errors

what i do:

  • login as normal User
  • cmd runas client Admin
  • change to Folder and install

maybe I don't understand you correctly, your two lines don't like it

Write-ADTLogEntry -Message "The calling account \[$(\[PSADT.AccountManagement.AccountUtilities\]::CallerUsername)\] is running interactively, but not as the logged on user and is missing the permission(s) \['$(\[System.String\]::Join("', '", $missingPermissions))'\] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations." -Severity Warning
return \[PSADT.AccountManagement.AccountUtilities\]::CallerRunAsActiveUser

Install\] :: Installation	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: Intune OS Language : DE	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: Intune User Language : DE	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: SCCM c_Sprache : de-De	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: angemelderter User: UserName	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: RunAsActiveUser { NTAccount = DomainName\\UserName, SID = S-1-5-21-1324208-841832012-1246845465-17577, UserName = UserName, DomainName = DomainName, SessionId = 2 }	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: UseDefaultMsi: PSADT.Module.DeploymentSession.UseDefaultMsi	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: ================	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: Bitte Outlook starten, Installation abgeschlossen	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)
\[Post-Install\] :: ================	Install-ADTDeployment	15.09.2025 16:01:19	6860 (0x1ACC)

then error

Script only for Show-ADTInstallationPrompt - better than an explanation

##================================================
## MARK: Post-Install
##================================================
$MyOSLanguage='Intune OS Language : ' + $currentLanguage
Write-ADTLogEntry -Message $MyOSLanguage
$MyOSLanguage='Intune User Language : '+ $currentUILanguage
Write-ADTLogEntry -Message $MyOSLanguage
Write-ADTLogEntry -Message "SCCM c_Sprache : $MyLanguage"
$MyUser=$RunAsActiveUser.Username
Write-ADTLogEntry -Message "angemelderter User: $MyUser"
Write-ADTLogEntry -Message $RunAsActiveUser
Write-ADTLogEntry -Message "UseDefaultMsi: $adtSession.UseDefaultMsi"

    # Sprachmeldungen in einer Hashtable definieren
    $Messages = @{
        "de" = "Bitte Outlook starten, Installation abgeschlossen"
        "fr" = "Veuillez démarrer Outlook, installation terminée"
        "en" = "Please start Outlook, installation completed"
    }

    # Sprache ermitteln (MyLanguage bevorzugt, sonst currentUILanguage)
    $Lang = $MyLanguage
    if (-not $Lang) { $Lang = $currentUILanguage }

    # Sprachcode auf die ersten zwei Zeichen reduzieren
    $LangCode = $Lang.Substring(0,2).ToLower()

    # Nachricht auswählen (Fallback auf Englisch, falls Sprache nicht definiert)
    $MyMessage = $Messages[$LangCode]
    Write-ADTLogEntry -Message '================'
    Write-ADTLogEntry -Message $Messages[$LangCode]
    Write-ADTLogEntry -Message '================'
    if (-not $MyMessage) { $MyMessage = $Messages["en"] }

if ($RunAsActiveUser) {if (!$adtSession.UseDefaultMsi) {Show-ADTInstallationPrompt -Message $Messages\[$LangCode\] -ButtonRightText 'OK' -Icon Information -NoWait} }

We used to do the same thing for pre-SCCM testing, whilst logged-on as a standard non-admin user and using "run-as administrator" to kick-off the kit via an Install.cmd or Uninstall.cmd file. A while back we switched to using PSEXEC in this process so that it always runs with the SYSTEM account, which is a better test as this is the account that SCCM/Intune would be using (for system-based installs).

In 4.1.3 I noticed that if I were to run-as-administrator so the script runs with my Administrator account and I did NOT use psexec then PSADT would complete successfully though would warn me with messages like:

[2025-09-15T16:21:55.7879977+01:00] [Pre-Install] [Get-ADTClientServerUser] [Warning] :: The calling account [MYDOMAIN\myAdminAccount] is running interactively, but not as the logged on user and is missing the permission(s) ['SeAssignPrimaryTokenPrivilege'] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations.

In 4.1.4 and 4.1.5 however, it gives me some of those warnings as above as usual, but when it reaches the point of showing a balloon tip, it errors:
(Sorry, using a screenshot as I couldn't get is to display nicely!)

So this behaviour seems to have started in 4.1.4 and if it weren't for this post, I may not have noticed and it isn't an issue for us as always use PSEXEC/System Account for testing etc.

p.s. I should add @mjr4077au, you fixed something regarding balloon tips in 4.1.4, which works great! I have wondered if it's by design that you shouldn't be running the kit with just a local-admin account (whilst logged on as a standard user), and you should always use the SYSTEM account when doing "manual" tests (unless is a per-user non-admin installation, and that's different).
4.1.3 - Show-ADTBalloonTip - The client process returned an exception / Access Denied - The Toolkit / General Discussion - PSAppDeployToolkit Community

Hopefully I've understood the point of the author's post, with regards to using run-as administrator.

This is why I was saying above that I need to see your full log file. Perhaps you can DM it to me if you're concerned about attaching it in a public forum.


My problem here is I only have a few pieces of the puzzle. Without seeing the full log file, I don't know what users it found logged onto the device, among other crucial bits of information.

The point I was trying to make with the two lines was that to receive the "is running interactively, but not as the logged on user and is missing the permission(s)" warning, it means that the toolkit knows and understands you're running the toolkit interactively as another user (an admin user in this instance) from another session (the logged on, non-admin session) and is warning you that since the admin account does not have the required privileges to impersonate another user, it'll run the client/server action (the UI element) as the calling admin user. This part is failing for you, but it also cannot fail either.


This screenshot shows I'm logged on as "existingenduser" but am running an elevated prompt as "mjr40", my admin account. I receive the same yellow warning message, but we can see the UI is running as myself, and we can see it's running in dark mode as my mjr40 account is set to dark mode, whereas "existingenduser" is in light mode.

Please provide the full log file when you have a moment and hopefully we can diagnose further what's going on for your unique situation.

Agreed completely that this is a better test. You can also test by using the Task Scheduler to run a task on demand. Its important to note that even with psexec.exe, you no longer need the -i argument as the client/server process means the SYSTEM-running process no longer requires interactivity.

I can't replicate this either when I perform my own testing.


It's possible you could receive this if MyAdminAccount just so happened to log off Windows at the precisely right moment to trigger it. It'd be pretty unlucky to have the client/server stuff detect that there's a valid user, then within milliseconds, the user is logged off completely. Receiving your full log file would be great here also to better understand what's going on.

So just to clarify, are you suggesting the above issue regarding Show-ADTBalloonTip is no longer occurring? As mentioned above as well, I do feel testing your admin-requiring packages as SYSTEM is a more proper and robust way to test, however we do permit testing with an elevated command prompt, however you'll receive the warning you've already received which will recommend testing as SYSTEM as you've now moved towards.

Thanks, I urgently need to package something first. I'll get back to you later.

How am I supposed to send you the complete log file? I'm not allowed to send an attachment.

@That-Annoying-Guy can users DM attachments to other users or is that restricted?

No matter what, I'm not allowed to. I can't give you a log. I'd also give you the script.

directly or to that

Soooo, just change the extension and I'll rename it back?

try sending it directly to you

Script Invoke-AppDeployToolkit.ps1.png
You don't need to make any adjustments in config.psd1
other Log LogPath = 'C:\Logfiles\Software'
other msi InstallParams = 'ALLUSERS=1 REBOOT=ReallySuppress REBOOTPROMPT=Suppress ROOTDRIVE=C:\ /QN'
deactivate the rows in the area
MARK: Pre-Install
Uninstall-ADTApplication -Name $MyRemove -ApplicationType 'MSI'
MARK: Install
Start-ADTMsiProcess -Action 'Install' -FilePath $MyMSIFile

the logs
RunAs Adminstrator: V5 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log.png
IntuneAgent 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log.png
SCCMAgent-Staging 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log.png (provisioning Mode)
SCCMAgent-underUser 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log.png

doesn't work, no matter how

@Toni Can you please try copying the text from your log file and pasting it here between two lines of ```? (or use the Preformatted text button </> on the toolbar above):
image

Hi Adrian

I sent it directly to Mitch Script and log files
greeting
toni

Yes, that's correct. Show-ADTBalloonTip fails if I were to run the script with "run as administrator" whilst my standard user account is signed in. It was fine in 4.1.3 though that version had the worse problem that balloon tips wouldn't display (and would error) when the script was run with the SYSTEM account. But as you fixed that issue from 4.1.4, I'm happy. If it could work for an admin-account that would be good too, but for it's not essential.

Here is the full log (with all the usual names changed etc)

<![LOG[-------------------------------------------------------------------------------]LOG]!><time="16:07:14.877+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [MicrosoftOrca4.0.6001.0000x86R1] install started.]LOG]!><time="16:07:14.877+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [MicrosoftOrca4.0.6001.0000x86R1] script version is [1.0.0].]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [MicrosoftOrca4.0.6001.0000x86R1] script date is [2025-08-20].]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [Invoke-AppDeployToolkit.ps1] script version is [4.1.3.1].]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following parameters were passed to [Invoke-AppDeployToolkit.ps1]: [-DeploymentType:'Install'].]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module version is [4.1.5].]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module imported in [2.9315346] seconds.]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module initialized in [2.6166257] seconds.]LOG]!><time="16:07:14.881+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] module path is ['C:\Temp\PSADT\PSAppDeployToolkit'].]LOG]!><time="16:07:14.896+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] config path is ['C:\Temp\PSADT\Config'].]LOG]!><time="16:07:14.896+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] string path is ['C:\Temp\PSADT\Strings'].]LOG]!><time="16:07:14.896+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: [PSAppDeployToolkit] session mode is [Native].]LOG]!><time="16:07:14.896+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Computer Name is [mycomputer.mydomain.com].]LOG]!><time="16:07:14.904+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current User is [MYDOMAIN\myAdminAcccount].]LOG]!><time="16:07:14.904+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: OS Version is [Microsoft Windows 11 Enterprise X64 10.0.26100.4946].]LOG]!><time="16:07:14.904+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: OS Type is [WorkStation].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Hardware Platform is [Physical].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current Culture is [en-GB], language is [EN] and UI language is [EN].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Host is [ConsoleHost] with version [5.1.26100.4768].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Version is [5.1.26100.4768 X64].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell Process Path is [C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe].]LOG]!><time="16:07:14.912+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: PowerShell CLR (.NET) version is [4.0.30319.42000].]LOG]!><time="16:07:14.923+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following users are logged on to the system: [MYDOMAIN\myStandardUserAccount].]LOG]!><time="16:07:14.923+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Session information for all logged on users:
 
NTAccount             : MYDOMAIN\myStandardUserAccount
SID                   : S-1-5-21-329068152-884357618-682003330-55107
UserName              : myStandardUserAccount
DomainName            : MYDOMAIN
SessionId             : 2
SessionName           : RDP-Tcp#0
ConnectState          : WTSActive
IsCurrentSession      : True
IsConsoleSession      : False
IsActiveUserSession   : True
IsValidUserSession    : True
IsUserSession         : True
IsRdpSession          : True
IsLocalAdmin          : False
IsLocalAdminException : 
LogonTime             : 15/09/2025 09:04:58
IdleTime              : 00:00:03.3739120
DisconnectTime        : 
ClientName            : MY_COMPUTER_NAME
ClientProtocolType    : RDP
ClientDirectory       : C:\WINDOWS\system32\mstscax.dll
ClientBuildNumber     : 26100
]LOG]!><time="16:07:14.928+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Current process is running with user account [MYDOMAIN\myAdminAcccount] under logged on user session for [MYDOMAIN\myStandardUserAccount].]LOG]!><time="16:07:14.928+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: There is no console user logged on (user with control of physical monitor, keyboard, and mouse).]LOG]!><time="16:07:14.928+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The active logged on user who will receive UI elements is [MYDOMAIN\myStandardUserAccount].]LOG]!><time="16:07:14.932+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The current execution context has a primary UI language of [en-US].]LOG]!><time="16:07:14.935+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The following locale was used to import UI messages from the strings.psd1 files: [en-GB].]LOG]!><time="16:07:14.939+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\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="16:07:14.943+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Device has completed the OOBE and toolkit is not running with an active ESP in progress.]LOG]!><time="16:07:14.948+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Session 0 not detected, toolkit running as non-SYSTEM user account.]LOG]!><time="16:07:14.948+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: The processes ['Orca'] were specified as requiring closure but toolkit is configured to not adjust deployment mode.]LOG]!><time="16:07:14.948+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Installation is running in [Interactive] mode.]LOG]!><time="16:07:14.948+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Deployment type is [Install].]LOG]!><time="16:07:14.958+0" date="9-16-2025" component="Open-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Initialization] :: Module [PSAppDeployToolkit.Extensions] imported successfully.]LOG]!><time="16:07:15.015+0" date="9-16-2025" component="PSAppDeployToolkit.Extensions.psm1" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit.Extensions\PSAppDeployToolkit.Extensions.psm1">
<![LOG[[Initialization] :: Module [PSAppDeployToolkit.Extensions] imported successfully.]LOG]!><time="16:07:15.023+0" date="9-16-2025" component="PSAppDeployToolkit.Extensions.psm1" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit.Extensions\PSAppDeployToolkit.Extensions.psm1">
<![LOG[[Pre-Install] :: Checking for running processes: ['Orca']]LOG]!><time="16:07:15.032+0" date="9-16-2025" component="Get-ADTRunningProcesses" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Specified processes are not running.]LOG]!><time="16:07:15.039+0" date="9-16-2025" component="Get-ADTRunningProcesses" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Getting information for installed applications matching the provided FilterScript...]LOG]!><time="16:07:15.055+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Found installed application [Microsoft Orca 4.0.6001.0000 x86 R1] version [4.0.6001.0000].]LOG]!><time="16:07:15.129+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Skipped 2 entries while searching, because they were considered Microsoft updates.]LOG]!><time="16:07:15.147+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Getting information for installed applications...]LOG]!><time="16:07:15.166+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Found installed application [Microsoft Orca 4.0.6001.0000 x86 R1] version [4.0.6001.0000].]LOG]!><time="16:07:15.230+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Skipped 2 entries while searching, because they were considered Microsoft updates.]LOG]!><time="16:07:15.252+0" date="9-16-2025" component="Get-ADTApplication" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: The existing app version is the same or higher.]LOG]!><time="16:07:15.252+0" date="9-16-2025" component="Get-AppVersionComparison" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit.Extensions\PSAppDeployToolkit.Extensions.psm1">
<![LOG[[Pre-Install] :: The calling account [MYDOMAIN\myAdminAcccount] is running interactively, but not as the logged on user and is missing the permission(s) ['SeAssignPrimaryTokenPrivilege'] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations.]LOG]!><time="16:07:15.279+0" date="9-16-2025" component="Get-ADTClientServerUser" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Checking for running processes: ['Orca']]LOG]!><time="16:07:15.281+0" date="9-16-2025" component="Get-ADTRunningProcesses" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Specified processes are not running.]LOG]!><time="16:07:15.293+0" date="9-16-2025" component="Get-ADTRunningProcesses" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Checking whether the device's microphone is in use...]LOG]!><time="16:07:15.320+0" date="9-16-2025" component="Test-ADTMicrophoneInUse" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: The device's microphone is currently not in use.]LOG]!><time="16:07:15.325+0" date="9-16-2025" component="Test-ADTMicrophoneInUse" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Checking whether any logged on users are in presentation mode...]LOG]!><time="16:07:15.333+0" date="9-16-2025" component="Get-ADTPresentationSettingsEnabledUsers" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Registry key [Microsoft.PowerShell.Core\Registry::HKEY_USERS\S-1-5-21-329068152-884357618-682003330-55107\Software\Microsoft\MobilePC\AdaptableSettings\Activity] does not exist. Return $null.]LOG]!><time="16:07:15.625+0" date="9-16-2025" component="Get-ADTRegistryKey" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Registry key [Microsoft.PowerShell.Core\Registry::HKEY_USERS\S-1-5-21-738721992-2219620323-492918194-1396\Software\Microsoft\MobilePC\AdaptableSettings\Activity] does not exist. Return $null.]LOG]!><time="16:07:15.882+0" date="9-16-2025" component="Get-ADTRegistryKey" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: There are no logged on users in presentation mode.]LOG]!><time="16:07:15.973+0" date="9-16-2025" component="Get-ADTPresentationSettingsEnabledUsers" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Checking if PowerPoint is in either fullscreen slideshow mode or presentation mode...]LOG]!><time="16:07:15.998+0" date="9-16-2025" component="Test-ADTPowerPoint" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: The calling account [MYDOMAIN\myAdminAcccount] is running interactively, but not as the logged on user and is missing the permission(s) ['SeAssignPrimaryTokenPrivilege'] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations.]LOG]!><time="16:07:16.007+0" date="9-16-2025" component="Get-ADTClientServerUser" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: PowerPoint application is not running.]LOG]!><time="16:07:16.018+0" date="9-16-2025" component="Test-ADTPowerPoint" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: PowerPoint is running in fullscreen mode [False].]LOG]!><time="16:07:16.021+0" date="9-16-2025" component="Test-ADTPowerPoint" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: The calling account [MYDOMAIN\myAdminAcccount] is running interactively, but not as the logged on user and is missing the permission(s) ['SeAssignPrimaryTokenPrivilege'] necessary to create a process as another user. The client/server process will be created as the calling account, however PSAppDeployToolkit's client/server process is designed to operate directly as a logged on user. As such, it is recommended to either log on directly to Windows using this account you're testing with, assign this account the missing permissions, or test via the SYSTEM account just as ConfigMgr or Intune uses for its operations.]LOG]!><time="16:07:16.037+0" date="9-16-2025" component="Get-ADTClientServerUser" context="MYDOMAIN\myAdminAcccount" type="2" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Displaying balloon tip notification with message [Update started.].]LOG]!><time="16:07:16.044+0" date="9-16-2025" component="Show-ADTBalloonTip" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Could not find a valid logged on user session for [MYDOMAIN\myAdminAcccount].
Error Record:
-------------
 
Message               : Could not find a valid logged on user session for [MYDOMAIN\myAdminAcccount].
 
FullyQualifiedErrorId : NoActiveUserError,Start-ADTProcessAsUser
ScriptStackTrace      : at Start-ADTProcessAsUser<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 22714
                        at Private:Invoke-ADTClientServerOperation, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 1435
                        at Show-ADTBalloonTip<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 17384
                        at Install-ADTDeployment, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 167
                        at <ScriptBlock>, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 370
                        at <ScriptBlock>, <No file>: line 1
 
TargetObject          : Value
                        -----
                        MYDOMAIN\myAdminAcccount
 
PositionMessage       : At C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1:1435 char:17
                        + ...             & $Script:CommandTable.'Start-ADTProcessAsUser' @sapauPar ...
                        +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="16:07:16.349+0" date="9-16-2025" component="Start-ADTProcessAsUser" context="MYDOMAIN\myAdminAcccount" type="3" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: Could not find a valid logged on user session for [MYDOMAIN\myAdminAcccount].
Error Record:
-------------
 
Message               : Could not find a valid logged on user session for [MYDOMAIN\myAdminAcccount].
 
FullyQualifiedErrorId : NoActiveUserError,Show-ADTBalloonTip
ScriptStackTrace      : at Start-ADTProcessAsUser<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 22714
                        at Private:Invoke-ADTClientServerOperation, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 1435
                        at Show-ADTBalloonTip<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 17384
                        at Install-ADTDeployment, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 167
                        at <ScriptBlock>, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 370
                        at <ScriptBlock>, <No file>: line 1
 
TargetObject          : Value
                        -----
                        MYDOMAIN\myAdminAcccount
 
PositionMessage       : At C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1:167 char:106
                        + ... gress @progressParams } else { Show-ADTBalloonTip @balloonTipParams }
                        +                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="16:07:16.380+0" date="9-16-2025" component="Show-ADTBalloonTip" context="MYDOMAIN\myAdminAcccount" type="3" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: An unhandled error within [Invoke-AppDeployToolkit.ps1] has occurred.
Error Record:
-------------
 
Message               : Could not find a valid logged on user session for [MYDOMAIN\myAdminAcccount].
 
FullyQualifiedErrorId : NoActiveUserError,Show-ADTBalloonTip
ScriptStackTrace      : at Start-ADTProcessAsUser<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 22714
                        at Private:Invoke-ADTClientServerOperation, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 1435
                        at Show-ADTBalloonTip<Process>, C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 17384
                        at Install-ADTDeployment, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 167
                        at <ScriptBlock>, C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1: line 370
                        at <ScriptBlock>, <No file>: line 1
 
TargetObject          : Value
                        -----
                        MYDOMAIN\myAdminAcccount
 
PositionMessage       : At C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1:167 char:106
                        + ... gress @progressParams } else { Show-ADTBalloonTip @balloonTipParams }
                        +                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="16:07:16.408+0" date="9-16-2025" component="Invoke-AppDeployToolkit.ps1" context="MYDOMAIN\myAdminAcccount" type="3" thread="968" file="C:\Temp\PSADT\Invoke-AppDeployToolkit.ps1">
<![LOG[[Finalization] :: [MicrosoftOrca4.0.6001.0000x86R1] install completed in [1.5426854] seconds with exit code [60001].]LOG]!><time="16:07:16.415+0" date="9-16-2025" component="Close-ADTSession" context="MYDOMAIN\myAdminAcccount" type="3" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[-------------------------------------------------------------------------------]LOG]!><time="16:07:16.415+0" date="9-16-2025" component="Close-ADTSession" context="MYDOMAIN\myAdminAcccount" type="1" thread="968" file="C:\Temp\PSADT\PSAppDeployToolkit\PSAppDeployToolkit.psm1">

As per the above-shared screenshot, I can't replicate this issue at all on my local device. I even added my non-admin test account to the local Remote Desktop Users group so I could RDP in with it to match your setup (my testing was while logged onto the console). Again, can't replicate.

Could I please ask that you post this issue on our GitHub page so we can track it, referencing this forum post in the process? We'll have to work our what's causing this but it may take some time.

@Toni and @paulh, could I actually please ask each of you to try this pre-4.1.6 release build: - Update two package versions in iNKORE sample project. · PSAppDeployToolkit/PSAppDeployToolkit@42683e9 · GitHub. I just realised this is what I've been testing with, and it contains improvements that may resolve this issue.

You should only need to download the module and replace your entire PSAppDeployToolkit folder with one from the zip file.

Hi Mitch

I'll try it, I'm almost there - feedback follows

No download - do I have to create a user on github?

greeting
toni

You'll need an account to download the file, yeah. It'd be good for you to have an account anyway as bug reports shouldn't ever be made here, they should be made on GitHub directly. The forums are just for discussions.