NVDA don't install on domain machines

[Nedashki]

Brief summary

NVDA don't install on domain machines while all another softwares install without problems. After launch an install file there is a pop up window that says "Please wait while Setup is loading" and then nothing happens.

Steps to reproduce

Run installer file as admin

Actual behavior

NVDA don't install on domain machines while all another softwares install without problems. After launch an install file there is a pop up window that says "Please wait while Setup is loading" and then nothing happens.
The installer creates temp files and logs in %TEMP%. These files remain in the folder for a few seconds and then disappear, leaving the directory empty again. The installer does not proceed to the initial screen with the license agreement and installation type selection (the standard first NVDA installation window).
After this, the installation process hangs and then exits. Also installer starts the nvda_noUIAccess.exe --launcher but this process has no footsteps in any logs
The only log in event viewer is :

Expected behavior

Software installed

NVDA logs, crash dumps and other attachments

No response

NVDA type

installer/launcher copy

NVDA version

2025.3.3

Have you tried any other versions of NVDA? If so, please report their behaviors.

No response

Windows version

win11 24h2

Name and version of other software in use when reproducing the issue

No response

Other information about your system

No response

Does the issue still occur after restarting your computer?

I have restarted my computer and the issue still occurs

If NVDA add-ons are disabled, is your problem still occurring?

I have restarted NVDA with add-ons disabled and the issue still occurs

Does the issue still occur after you run the System Accessibility Repair Tool (COM Registration Fixing Tool in older versions) in NVDA's tools menu?

I have run the System Accessibility Repair Tool and the issue still occurs

[Nedashki]

Forgot to say, there is no any events/allerts in Defender cloud or Intune

[seanbudd]

Can you please extract the text from the log? Screenshots are not accessible to the majority of our community, and translating them is even harder

[SaschaCowley]

I suspect this is a group policy preventing execution of files outside of trusted locations

[Nedashki]

Here is Get-WinEvent -LogName "Security" log:

TimeCreated : 23.04.2026 9:36:23
Message : A new process has been created.

          Creator Subject:
          	Security ID:		S-1-5-21-789336058-1123561945-682003330-417322
          	Account Name:		
          	Account Domain:		
          	Logon ID:		0x378CF2DAD
          
          Target Subject:
          	Security ID:		S-1-0-0
          	Account Name:		-
          	Account Domain:		-
          	Logon ID:		0x0
          
          Process Information:
          	New Process ID:		0x4f6c
          	New Process Name:	C:\Windows\CCM\nsm199E.tmp\app\nvda_noUIAccess.exe
          	Token Elevation Type:	TokenElevationTypeFull (2)
          	Mandatory Label:		S-1-16-12288
          	Creator Process ID:	0x5068
          	Creator Process Name:	C:\Install\nvda_2025.3.3.exe
          	Process Command Line:	C:\Windows\CCM\nsm199E.tmp\app\nvda_noUIAccess.exe  --launcher
          
          Token Elevation Type indicates the type of token that was assigned to the new process in accordance with User Account Control policy.
          
          Type 1 is a full token with no privileges removed or groups disabled.  A full token is only used if User Account Control is disabled o
          r if the user is the built-in Administrator account or a service account.
          
          Type 2 is an elevated token with no privileges removed or groups disabled.  An elevated token is used when User Account Control is ena
          bled and the user chooses to start the program using Run as administrator.  An elevated token is also used when an application is conf
          igured to always require administrative privilege or to always require maximum privilege, and the user is a member of the Administrato
          rs group.
          
          Type 3 is a limited token with administrative privileges removed and administrative groups disabled.  The limited token is used when U
          ser Account Control is enabled, the application does not require administrative privilege, and the user does not choose to start the p
          rogram using Run as administrator.

TimeCreated : 23.04.2026 9:36:10
Message : A new process has been created.

          Creator Subject:
          	Security ID:		S-1-5-21-789336058-1123561945-682003330-417322
          	Account Name:		
          	Account Domain:		
          	Logon ID:		0x378CF2DAD
          
          Target Subject:
          	Security ID:		S-1-0-0
          	Account Name:		-
          	Account Domain:		-
          	Logon ID:		0x0
          
          Process Information:
          	New Process ID:		0x5068
          	New Process Name:	C:\Install\nvda_2025.3.3.exe
          	Token Elevation Type:	TokenElevationTypeFull (2)
          	Mandatory Label:		S-1-16-12288
          	Creator Process ID:	0x9768
          	Creator Process Name:	C:\Windows\System32\cmd.exe
          	Process Command Line:	nvda_2025.3.3.exe

[Nedashki]

I suspect this is a group policy preventing execution of files outside of trusted locations

I've already tried to start the setup from locations allowed by execution policies. The result is the same

[Nedashki]

Also adding extracted log from screenshot:
Event 1000, Application Error

General

Faulting application name: nvda_noUIAccess.exe, version: 2023.3.0.29780, time stamp: 0x6208d9c6
Faulting module name: ucrtbase.dll, version: 10.0.26100.7623, time stamp: 0xaa04994e
Exception code: 0xc0000409
Fault offset: 0x0002da51
Faulting process ID: 0x697C
Faulting application start time: 0x1DCB07D820E7C3E
Faulting application path: C:\Users\ADM_SU~1\AppData\Local\Temp\nsa4F22.tmp\app\nvda_noUIAccess.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 8b55be40-c887-4cc6-89d3-27aa2402f691
Faulting package full name:
Faulting package-relative application ID:

[XLTechie]

I noticed an odd thing. Your issue description says NVDA 2025.3.3, but your log says: Faulting application name: nvda_noUIAccess.exe, version: 2023.3.0.29780 Can you verify that you are trying with NVDA 2025.3.3, and not an old copy of the installer? nvda_noUIAccess.exe should not be indicating that version number according to my copy here for NVDA 2025.3.3. If possible, can you attempt to install NVDA 2026.1 beta 13?

[Nedashki]

I noticed an odd thing.
Your issue description says NVDA 2025.3.3, but your log says:

Faulting application name: nvda_noUIAccess.exe, version: 2023.3.0.29780

Can you verify that you are trying with NVDA 2025.3.3, and not an old copy of the installer?
nvda_noUIAccess.exe should not be indicating that version number according to my
copy here for NVDA 2025.3.3.

If possible, can you attempt to install NVDA 2026.1 beta 13?

I've tried installing versions 2026.1beta11 and 2025.1beta13, but the result was the same. Here's the log.

I also noticed that before the installer crashes, there is an entry in the Application log showing that SenseMdr crashes as well.

A new process has been created.

Creator Subject:
Security ID: SYSTEM
Account Name:
Account Domain:
Logon ID: 0x3E7

Target Subject:
Security ID:
Account Name:
Account Domain:
Logon ID: 0x139D0247

Process Information:
New Process ID: 0x2294
New Process Name: C:\Users\User\Downloads\nvda_2026.1beta13.exe
Token Elevation Type: TokenElevationTypeFull (2)
Mandatory Label: Mandatory Label\High Mandatory Level
Creator Process ID: 0x3480
Creator Process Name: C:\Windows\explorer.exe
Process Command Line: "C:\Users\User\Downloads\nvda_2026.1beta13.exe"

A new process has been created.

Creator Subject:
Security ID:
Account Name:
Account Domain:
Logon ID: 0x139D0247

Target Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Process Information:
New Process ID: 0x3670
New Process Name: C:\Users\User\AppData\Local\Temp\nsg7D5A.tmp\app\nvda_noUIAccess.exe
Token Elevation Type: TokenElevationTypeFull (2)
Mandatory Label: Mandatory Label\High Mandatory Level
Creator Process ID: 0x2294
Creator Process Name: C:\Users\User\Downloads\nvda_2026.1beta13.exe
Process Command Line: C:\Users\User\AppData\Local\Temp\nsg7D5A.tmp\app\nvda_noUIAccess.exe --launcher

[seanbudd]

I've already tried to start the setup from locations allowed by execution policies. The result is the same

The installer unpacks to a temporary directory and runs from there, so this won't work, unless you make C:\Users\User\AppData\Local\Temp\ a trusted directory, which is not a good idea. You will need to disable the policy for the installer to work.

Alternatively, you could create a portable copy on another machine, and install using the portable copy.

[Nedashki]

I've already tried to start the setup from locations allowed by execution policies. The result is the same

The installer unpacks to a temporary directory and runs from there, so this won't work, unless you make C:\Users\User\AppData\Local\Temp\ a trusted directory, which is not a good idea. You will need to disable the policy for the installer to work.
Alternatively, you could create a portable copy on another machine, and install using the portable copy.

I've tried changing %TEMP% (C:\Users\User\AppData\Local\Temp) to a trusted directory (setting both TEMP and TMP via set TEMP and TMP), but the result is still the same. The portable version also doesn't work.

However, if I run the setup before joining the machine to the domain, NVDA installs successfully. After joining the domain, the software works fine, so the issue appears to be only with the installer.