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.3

Describe the bug

I deployed an application with PSADT using the new Interactive feature not having to utilize ServiceUI. Amazing by the way. On a few systems, not all, I see this error

[Pre-Install] :: Exception calling "TestEffectiveAccess" with "3" argument(s): "The specified domain either does not exist or could not be contacted"

`<![LOG[[Pre-Install] :: Exception calling "TestEffectiveAccess" with "3" argument(s): "The specified domain either does not exist or could not be contacted"
Error Record:

 
Message : Exception calling "TestEffectiveAccess" with "3" argument(s): "The specified domain either does not exist or could not be contacted"
InnerException : System.ComponentModel.Win32Exception (0x80004005): The specified domain either does not exist or could not be contacted
                           at PSADT.LibraryInterfaces.AdvApi32.AuthzInitializeContextFromSid(AUTHZ_CONTEXT_FLAGS Flags, SafeHandle UserSid, SafeHandle hAuthzResourceManager, Nullable`1 pExpirationTime, LUID Identifier, IntPtr DynamicGroupArgs, AuthzFreeContextSafeHandle& phAuthzClientContext) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:line 655
                           at PSADT.FileSystem.FileSystemUtilities.GetEffectiveAccess(String path, SecurityIdentifier sid, FileSystemRights desiredAccessMask) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\FileSystem\FileSystemUtilities.cs:line 116
                           at CallSite.Target(Closure , CallSite , Type , Object , Object , Object )
 
FullyQualifiedErrorId : Win32Exception,Show-ADTInstallationWelcome
ScriptStackTrace : at Private:Set-ADTClientServerProcessPermissions, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 2076
                        at Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 1192
                        at Show-ADTWelcomePrompt, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19200
                        at Show-ADTInstallationWelcome, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19510
                        at Install-ADTDeployment, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1: line 138
                        at , C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1: line 346
                        at , : line 1
 
PositionMessage : At C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1:138 char:5
                        + Show-ADTInstallationWelcome @saiwParams
                        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
]LOG]!><time="11:03:45.193-300" date="8-27-2025" component="Show-ADTInstallationWelcome" context="NT AUTHORITY\SYSTEM" type="3" thread="10816" file="C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">
<![LOG[[Pre-Install] :: An unhandled error within [Invoke-AppDeployToolkit.ps1] has occurred.
Error Record:

 
Message : Exception calling "TestEffectiveAccess" with "3" argument(s): "The specified domain either does not exist or could not be contacted"
InnerException : System.ComponentModel.Win32Exception (0x80004005): The specified domain either does not exist or could not be contacted
                           at PSADT.LibraryInterfaces.AdvApi32.AuthzInitializeContextFromSid(AUTHZ_CONTEXT_FLAGS Flags, SafeHandle UserSid, SafeHandle hAuthzResourceManager, Nullable1 pExpirationTime, LUID Identifier, IntPtr DynamicGroupArgs, AuthzFreeContextSafeHandle& phAuthzClientContext) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\LibraryInterfaces\AdvApi32.cs:line 655                            at PSADT.FileSystem.FileSystemUtilities.GetEffectiveAccess(String path, SecurityIdentifier sid, FileSystemRights desiredAccessMask) in D:\a\PSAppDeployToolkit\PSAppDeployToolkit\src\PSADT\PSADT\FileSystem\FileSystemUtilities.cs:line 116                            at CallSite.Target(Closure , CallSite , Type , Object , Object , Object )   FullyQualifiedErrorId : Win32Exception,Show-ADTInstallationWelcome ScriptStackTrace : at Private:Set-ADTClientServerProcessPermissions, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 2076                         at Private:Invoke-ADTClientServerOperation, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 1192                         at Show-ADTWelcomePrompt, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19200                         at Show-ADTInstallationWelcome<Process>, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19510                         at Install-ADTDeployment, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1: line 138                         at <ScriptBlock>, C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1: line 346                         at <ScriptBlock>, <No file>: line 1   PositionMessage : At C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1:138 char:5                         + Show-ADTInstallationWelcome @saiwParams                         + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ]LOG]!><time="11:03:45.266-300" date="8-27-2025" component="Invoke-AppDeployToolkit.ps1" context="NT AUTHORITY\SYSTEM" type="3" thread="10816" file="C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\Invoke-AppDeployToolkit.ps1"> <![LOG[[Finalization] :: [Sight&Sound_Portal_2025.1.8_x64_EN_01] install completed in [1.4126967] seconds with exit code [60001].]LOG]!><time="11:03:45.304-300" date="8-27-2025" component="Close-ADTSession" context="NT AUTHORITY\SYSTEM" type="3" thread="10816" file="C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1"> <![LOG[-------------------------------------------------------------------------------]LOG]!><time="11:03:45.308-300" date="8-27-2025" component="Close-ADTSession" context="NT AUTHORITY\SYSTEM" type="1" thread="10816" file="C:\Windows\IMECache\26defbe9-751f-4602-b943-e4f23f9159e1_1\PSAppDeployToolkit\PSAppDeployToolkit.psm1">

I was first trying in v4.1.1. I found a closed but report on the issue, #1649. I redeployed with the latest version but still experiencing it in the latest.

Any assistance would be greatly appreciated. Thanks for all the awesome work!!

Steps to reproduce

1. Packaged app into a .intunewin file
2. Deployed to Intune
3. Install command - Invoke-AppDeployToolkit.exe

Environment data

Command ran on the system experiencing the issue.  Device is Entra joined only, and new Win11 24H2 install.  I'm logged in as the local LAPS admin user, and I see the .NET error.   Would that be causing this issue?

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           : en-US
OsMuiLanguages       : {en-US}
KeyboardLayout       : en-US
TimeZone             : (UTC-05:00) Eastern Time (US & Canada)
HyperVisorPresent    : True
CsPartOfDomain       : False
CsPCSystemType       : Desktop

dotnet : The term 'dotnet' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:270
+ ... 'HyperVisorPresent','CsPartOfDomain','CsPCSystemType'); dotnet --info
+                                                             ~~~~~~
    + CategoryInfo          : ObjectNotFound: (dotnet:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException