Windows Multipoint Server Issue SRCShell.exe (WMS 2011) WMSShell.exe (WMS 2012)

The problem:

Mulitpoint boots up and “auto-logs-in” as WMSShell user however the stations do not initiate a session and the blank default windows desktop is viewable. Its like its stuck in maintenance mode.

The fix:

As it turns out Multipoint server 2011 or 2012 autologs the local user WMSShell in and then autostarts the multipoint interface which is located at: C:\Program Files\Windows MultiPoint Server\SRCShell.exe. (WMS 2011) or C:\Program Files\Windows MultiPoint Server\WMSShell.exe (WMS2012)

The C:\Program Files\Windows MultiPoint Server\SRCShell.exe is the missing part. if you run the EXE (locally) it will start the familiar Multipoint Login Screen.

ok fixed right.. no….not quite…

To make this work after a reboot a little more work is needed. The problem is that the C:\Program Files\Windows MultiPoint Server\SRCShell.exe is called from the WMSShell local user profile. To edit this you must remote into the system as another user and log the WMSShell user off using task manager / users / logoff, then use regedit to open the NTUser.dat file for the WMSShell users profile located in c:\users\WMSShell\NTUser.dat


  1. Open regedit.exe
  2. make sure HKEY_LOCAL_MACHINE is selected on the left panel
  3. click File -> Load Hive in the main menu
  4. open ntuser.dat file in common dialog
  5. specify some temporary name, like USER1
  6. There should be a string key named Shell with the path to the SRCShell.exe however it dissapeered on mine hence the problem so Add a new String Key to HKEY_LOCAL_MACHINE\USER1\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ called Shell with the path to C:\Program Files\Windows MultiPoint Server\WMSShell.exeshell
  7. Make sure HKEY_LOCAL_MACHINE\USER1 is selected on the left panel and then unload hive from main menu
  8. reboot.


If anyone knows the reson why this disapeers let me know!!!!


About the author : dave

6 Comments to “Windows Multipoint Server Issue SRCShell.exe (WMS 2011) WMSShell.exe (WMS 2012)”

You can Leave a Reply or Trackback this post.

  1. ron - September 1, 2015 at 4:43 am Reply

    Thanks for your solution. It saved me alot of work. It saves me a lot of work to deploy all our servers again. Greatings from The Netherlands

  2. Kazys - October 23, 2015 at 12:14 pm Reply

    Hi Dave,

    Thanks for taking the time to write up this issue and fix. The details would have eluded me for a long time.

    Speculating at the cause, I had completed many updates and maintenance activities on 11 WMS servers. Only one of the 11 came back to normal mode. One of the steps taken was executing delprof2 to clean up all user profiles. It’s possible that I didn’t filter out SRCShell account and the profile was mangled by this useful tool. No time to verify now.


  3. twitter automatically follow - October 28, 2016 at 10:05 pm Reply

    Appreciation too my fatgher who informed me onn thhe topic of tis webpage, thks
    weblog is actually remarkable.

  4. John - April 25, 2017 at 3:55 pm Reply


    Thanks for the work. It seems to have fixed our problem with two servers (2012). They both stuck in console mode after a Windows Update. Pretty sure that’s what broke it. Anyway, I removed the update from one of the servers and left it on the other. Both responded the same way to the registry fix and all is well.


Leave a Reply

Your email address will not be published.