none
ServerManager.exe - This application could not be started. - Windows Server 2012 R2 RRS feed

  • Question

  • Hello All,

    We have a Dell Precision M4800 installed with Windows Server 2012 R2, and we are unable to get the Server Manager working. When we click on ServerManager, the below error occurs,

    Error Message: ServerManager.exe - This application could not be started.

    Action Taken:

    1. Windows Updates, and Windows Security Updates are up-to-date, rebooted

    2. Display Drivers are updated, rebooted

    3. .NET Framework 4.5.2 is updated, rebooted

    Still the same error. Please assist.

    Thank you, Anand


    Anand Franklin

    Thursday, March 19, 2015 6:39 AM

Answers

  • Hi,

    Thanks for your post.

    Usually, ServerManager.exe error may be caused by:                    
    • The registry key of ServerManager.exe is invalid or damaged.
    • Computer malware has injected malicious code and modified ServerManager.exe file.
    • The ServerManager.exe file was uninstalled by other software.
    • The ServerManager.exe file was intentionally or mistakenly deleted by other software.
    • The required version of ServerManager.exe file is overwritten by other software.
    • There is a hardware failure, such as a bad hard disk.

    You can use the following solutions as the article mentioned to fix ServerManager.exe error:

    http://www.fixerrorhelps.com/fix-pc-error/how-to-fix-ServerManager.exe-error.html

    If all the suggestions did not work, i think we need to reinstall the Operating System.

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, March 20, 2015 6:53 AM
    Moderator

All replies

  • Hi,

    Thanks for your post.

    Usually, ServerManager.exe error may be caused by:                    
    • The registry key of ServerManager.exe is invalid or damaged.
    • Computer malware has injected malicious code and modified ServerManager.exe file.
    • The ServerManager.exe file was uninstalled by other software.
    • The ServerManager.exe file was intentionally or mistakenly deleted by other software.
    • The required version of ServerManager.exe file is overwritten by other software.
    • There is a hardware failure, such as a bad hard disk.

    You can use the following solutions as the article mentioned to fix ServerManager.exe error:

    http://www.fixerrorhelps.com/fix-pc-error/how-to-fix-ServerManager.exe-error.html

    If all the suggestions did not work, i think we need to reinstall the Operating System.

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, March 20, 2015 6:53 AM
    Moderator
  • Hello Anand, did you have find a resolution on this?  I have this same problem as well and have scanned endless articles with nothing suggested working.   I would appreciate your letting me know how you resolved the issue.  Thank you,  Terri
    • Proposed as answer by Martin Sturm Wednesday, November 11, 2015 1:23 AM
    Friday, November 6, 2015 9:51 PM
  • Hello Terri,

    We were unable to resolve, so, we had to format and reload Windows Server 2012 R2 again.

    Thank you, Anand


    Anand Franklin

    Saturday, November 7, 2015 3:52 PM
  • Hello Terri and Anand,

    I recently experienced this issue, and after struggling to find a solution I finally found one. For whatever reason (.Net Update?) .Net 2.0 was set to run in 32 bit mode. Executing ldr64.exe query from C:\Windows\Microsoft.NET\Framework64\v2.0.50727 will return 0x0000000 if set to 32 bit mode. To set it to 64 bit mode, execute ldr64.exe set64, which should return 0x0000001. Server Manager should not start.

    Regards,

    • Proposed as answer by TakisKalf Wednesday, July 12, 2017 8:34 PM
    Wednesday, March 8, 2017 10:38 PM
  • Thank you,

    The To set it to 64 bit mode, execute ldr64.exe set64, which should return 0x0000001. worked for me.

    Saturday, April 29, 2017 12:32 PM
  • Thank you ...!!!!!

    I was one step away from formatting the server and clean installing again...!!!!!!

    Thanks again.

    Wednesday, July 12, 2017 8:34 PM
  • Did didn't work for me. I have tried everything. The only way I have been able to load it is by resetting the windows up date folders. I load fine but by end of day it starts crashing again. I guess windows update tries to install something and messes everything us again.

    I'm running out of options.

    Thanks,

    Sunday, August 20, 2017 12:26 PM
  • Hello Juan.

    I did what you describe and it works !!!!! Thank's for sharing the solution :D

    Wednesday, August 23, 2017 1:48 PM
  • Its worked for me. Thank you very much


    Monday, August 28, 2017 10:54 AM
  • Hello All,

    I solved it by reinstalling framework by command prompt like below:

    DISM.exe /online /enable-feature /all /featurename:NetFx3

    DISM.exe /online /enable-feature /all /featurename:NetFx4.

    After that my problem solved.

    Thank you.

    regards

    Paolo Zanolla

    • Proposed as answer by Ciarán Reilly Monday, January 15, 2018 12:56 PM
    Tuesday, November 7, 2017 8:09 PM
  • thank you Paolo.

    this worked for me.

    regards.

    Friday, November 24, 2017 4:14 AM
  • Hi Juan,

    Thanks for your suggestion to resolve the issue....

    Regards,

    Gopal,

    Thursday, January 11, 2018 12:47 PM
  • Many thanks, Paolo. Your solution worked for me.
    Monday, January 15, 2018 12:57 PM
  • Thanks paolo

    its worked for me appriciated

    Thursday, January 18, 2018 12:37 PM
  • This worked for me. I am so grateful you posted it.

    David Kellett

    Monday, June 18, 2018 8:03 PM
  • Thanks, Your solution worked.
    Saturday, October 6, 2018 3:28 AM
  • Thank you,

    The To set it to 64 bit mode, execute ldr64.exe set64, which should return 0x0000001. worked for me.

    Monday, November 12, 2018 4:47 PM
  • it works for me
    Friday, December 28, 2018 8:28 AM
  • Hi

    Check the below .This solution worked for me

    The application could not be started correctly

    (0xc0000135)

     On Windows Server 2016

    You have to fix frameworks 3 and 4.

    To do this, start cmd Administrator Enter and enter the following commands.

     DISM.exe /online /enable-feature /all /featurename:NetFx3

    DISM.exe /online /enable-feature /all /featurename:NetFx4

    Afterwards, the server manager application will be back

    Error Cause:

    In any case, you should not remove the features under the tool itself

    .NET Framework 3.5 features

    And

    .NET Framework 4.6 features



    Friday, May 3, 2019 5:03 AM
  • not working 
    Thursday, July 11, 2019 2:51 AM
  • I was able to resolve this by installing .NET remotely from another computer with the same OS without issue.
    Thursday, August 22, 2019 7:21 AM