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

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

     

  • rraghvani's avatar
    rraghvani
    Icon for Champion Level 3 rankChampion Level 3
    14 hours ago

    Is your schedule configured to "Run whether user is logged on or not"? And is the password correct for the user account?