SessionCreator returns exitcode: 7 Failed to create user session
I currently have an issue on only 1 of my test machines where the testrun never starts and the exitcode is 7 with the message "Failed to create user session"
This machine runs 2 projects and has worked for about 2 years, now since January 6 it won't start the testrun anymore.
To go back to the basics I even made a new bacthscript to start the run with only the minimal required code.
"C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\SessionCreator.exe" RunTest /Username:"<PCName>\<UserName>" /Password:"<Password>" /ProjectPath:"<PathToPJS>\<ProjectSuite>.pjs" /ScreenResolution:1920*1080 /Timeout:9000 /project:"<Project>"
I still cant get the testrun to start.
Windows taskscheduler starts the batch script, this does work, the batch script starts but when it comes time to start a new session sessioncreator returns code 7.
I've already created a support ticket,
But I'm hoping any of you might be able to help me further.
To me this seems like a windows setting that got changed somewhere in an update but i'm not sure.
The PC is running on the lastest Win11 25H2 update
Hello fellow testers,
I sort of solved this issue so I'll let you know what I had to do to get my tests started again.
I have a batchscript in taskmanager that restarts my PC.
Then an other task that starts the tests planned about 15 min later.
Since the testrun can no longer start on when the pc is locked/ logged off,
I've added a registry edit that automatically logs on the user.
It can be added here:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
add these keys:
AutoAdminLogon 1
DefaultUserName {Your Username}
DefaultPassword {Your Password}
DefaultDomainName {Your PCs domain name}When the PC restarts it automatically logs on so it has a active session that SessionCreator/ testexecute can use.
When the testing is done I've added a script that logs off the user.Unfortunately my other PC now also has this issue. It can no longer create a user session.
2 of the 3 PCs i use now have this issue, I've disabled windows updates on the last working PC hoping it can still keep running as it is.
It seems all the vibecoding in windows 11 is breaking more and more everyday.
Please do let me know if anyone else starts having these issues. Maybe with more affected Smartbear can create a fix that solves this once and for all.
