Forum Discussion

MW_Didata's avatar
MW_Didata
Super Contributor
1 day ago

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 w...
desktop testing
rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
1 day ago

I have a VM which has TestExecute installed, and a PowerShell script, which has the following command, called by Task Scheduler at a given time.

& 'C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\SessionCreator.exe' RunTest /UserName:TestUser1 /password:'testuser1' /UseActiveSession /ScreenResolution:"1920*1080" /ProjectPath:"C:\Sandbox\TestComplete\ALS\ALS.pjs" /ExportLog:"C:\Sandbox\Log\TC_Automation_$tc_timestamp\index.html" /ExportSummary:"$summary_report" | Out-Null

The VM has been set up to automatically login user 'TestUser1', and the VM is always unlocked (this is my active session). When I invoke the script to launch SessionCreator, it will spool up another session to run the automation scripts.

SessionCreator

The utility opens interactive user sessions required for the TestComplete interaction with your tested application GUI. If an interactive user session is not opened, the test engine will not be able to access the GUI, and your tests will fail.

MW_Didata's avatar
MW_Didata
Super Contributor
1 day ago

I run the tests on a physical PC. It has Testexecute and Testcomplete Installed. 
I use pretty much the same command, but instead of the entire ProjectSuite it runs each project one after the other with the /Project flag.

but it no longer works. Like I stated above I even went back to a very basic batch script that should just start the testrun.

That also did not work.

I run other projects on another PC, that one still works. SessionCreator creates the session and testing begins, its only 1 machine that no longer works.

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    1 day ago

    Use Task Manager, and check the number of Users on both machines? Do both machines have the same OS versions? Check your security options for your Task Schedular, on both machines too.

    • MW_Didata's avatar
      MW_Didata
      Super Contributor
      1 day ago

      The PC has 2 users, 1 is the admin account of my org, and the other is the user account.
      The user account is also an administator on the machine.

      When checking Task manager only the 2nd user is shown, that is the user that should start the task.

      Both machines use the latest Win11 Pro 25H2.

      In taskschedular the options "Run with highest privileges" and "Run whether use is logged on or not" are both enabled. (Same as the other machine)

      • Hassan_Ballan's avatar
        Hassan_Ballan
        Icon for Champion Level 3 rankChampion Level 3
        1 day ago

        Even with the same org policy, two Windows 11 PCs can still behave differently. GPO defines intent, not the effective state at runtime, and SessionCreator is very sensitive to that state.

        Common reasons one PC works while the other fails:

        • Policy application timing / drift
          Updates, reboots, and logon state (locked vs unlocked) can leave machines with different effective settings.
        • Local Security Policy differences
          Local overrides (secpol.msc) like Log on locally, Log on as a batch job, or hidden Deny entries can block interactive session creation on one PC only.
        • Credential Guard / LSA protection
          These may be enabled by updates on one machine and not the other, breaking password-based session creation and causing exit code 7.
        • Session state at task start
          If one PC has an active/unlocked session (or lingering session), SessionCreator can work. A fully locked console often fails on Win11 now.
        • Task Scheduler execution context
          Tasks that look identical in the UI can differ in XML (logon type, session, SID).

        Quick isolation steps:

        1. Compare rsop.msc or gpresult /h outputs
        2. Check secpol.msc → User Rights Assignment
        3. Verify Credential Guard / LSA status
        4. Run query user at task time
        5. Export & diff Task Scheduler task XML
        6. Test with auto-login + unlocked session

         

        Bottom line:
        Windows 11 has tightened interactive session rules. One machine likely crossed a security threshold the other hasn’t yet, which explains why SessionCreator fails only on the locked PC.

        🤖 AI-assisted response
        👍 Found it helpful? Click Like
        ✅ Issue resolved? Click Mark as Solution