locked
Simulator not starting

    Question

  • Hi,

    I have a fresh installation of Windows 8.1 and Visual Studio 2013 on a Dell XPS15z laptop. I am trying to debug a Windows Store App in the simulator. It works fine when debugging on the local machine. (The sample Hello World app from msdn)

    The simulator loads, but it keeps loading, the five dots are moving from left to right, until after about 30 seconds, it closes and I see the following message in Visual Studio:

    'Unable to start  the Simulator. Cannot process request because the process (xxxxx) has exited.

    I have searched the internet, and all fixed I can find are not helping. I have upgraded my display drivers (Intel 3000 and nVidia 525M to the latest version (even beta version), disabled Cisco anyconnect services, upgraded Visual Studio 2013 to Update 1 RC, but nothing seems to help.

    The event log shows no errors, but it does show three warnings when the simulator is started:

    1. A pointer device did not report a valid unit of angular measurement.
    2. A pointer device reported a bad angular physical range.
    3. A pointer device reported a bad angular logical range.

    And after that an informational message: 'The Desktop Window Manager has exited with code (0xd00002fe)'

    Can anyone help me figure this out?

    Regards, Felix

    Sunday, December 29, 2013 8:53 PM

All replies

  • Hi,

    Try to see these threads below:

    http://social.msdn.microsoft.com/Forums/en-US/d4da010c-a0ea-48c2-8962-b40f4ac26a63/vs2013-preview-simulator-crashing-on-start?forum=w81prevtools

    http://stackoverflow.com/questions/12881217/windows-8-simulator-doesnt-work

    And you could also repair/re-install the VS to
    see if the issue still exist. Run your VS in /SafeMode and reset VS settings.

    If that cannot resolve your problem, you can go
    to Connect: https://connect.microsoft.com/VisualStudio
    I think they will help you with a satisfied solution.

    Best Wishes!



    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey. Thanks<br/> MSDN Community Support<br/> <br/> Please remember to &quot;Mark as Answer&quot; the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.


    • Edited by Anne Jing Monday, December 30, 2013 7:50 AM edit
    • Marked as answer by Anne Jing Monday, January 6, 2014 8:34 AM
    • Unmarked as answer by Felix Planjer Monday, January 6, 2014 9:22 AM
    Monday, December 30, 2013 7:49 AM
  • I had already found and tried the solutions you mentioned. However, they do not fix my issues.

    I reported the issue to connect. I will put their answer here, as soon as they provide one.

    Monday, January 6, 2014 9:24 AM
  • Hi,

    A little update: I found out that our "Cisco Anyconnect Network Access Manager" is causing the problems. I removed it and the simulator is running fine.

    I'll add this to my report on Connect. Hopefully it will be resolved.

    regards, Felix

    Thursday, January 9, 2014 8:56 AM