gMSA broken in 2026.3?
So I upgraded to 2026.3 yesterday, and I'm having issues with gMSA credentials.
I have jobs that fail with the following error message:
Error executing job: Failed to login user (1326). System.ComponentModel.Win32Exception (1326): The user name or password is incorrect.
It uses the non-builtin Powershell 7 Environment
I have a dedicated API environment which runs as a gMSA using it now results in 404 Client Error (No log text in the log-tab, and no other discernable information I can find)
I've double checked the service account using Test-ADServiceAccount which returns true for the gMSA, the service runs as LocalSystem. I tried creating a new variable (with the same gMSA) and this also fails.
I do have an odd error in PowerShellHost logs which I do not think happened prior to the upgrade:
2026-09-15 23:37:28.829 +02:00 [ERR] Error checking module path System.ArgumentException: The path is not of a legal form. at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.InternalGetDirectoryName(String path) at UniversalHost.AgentService.Initialize(IHostLogger logger) in D:\a\powershell-universal\powershell-universal\src\Host\AgentService.cs:line 48
Environment:
Windows Server 2022 (The CU for this month has not been installed) PSU Version 2026.3
All Comments (6)
@tholabrk Thanks for all the information. I do believe there was a change to gMSA so this may be a result of that. I've opened an issue to track to see if there was something we missed during that work. I will circle back with a confirmation on the bug or if I need more information.
Adam Driscoll
PowerShell Expert and Software Architect at Devolutions
Hey,
do you have an update for that?
I just updated my Company's instance to 2026.3. and no job/app is starting anymore, with the same error.
I use a gMSA account as well, but I did not really see impact.
My scripts run succesfully.
The PSU service is running as the gMSA
I use a gMSA account as well, but I did not really see impact.
My scripts run succesfully.
The PSU service is running as the gMSA
@denistiri
I have the Service running as System and I'm running the Scripts/App with different gmsa credentials depending on the scope of the Script.
having the same issue here on 2026.3.0, running psuni service as system and running apps/schedules as gmsa's, "Error executing job: Failed to login user (1326). System.ComponentModel.Win32Exception (1326): The user name or password is incorrect.."
Can confirm this gas been fixed in 2026.3.1 :)