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

  • 質問

  • 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

    2015年3月19日 6:39

回答

  • 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

    • 回答の候補に設定 Vivian_Wang 2015年3月31日 2:22
    • 回答としてマーク Vivian_Wang 2015年4月1日 10:05
    2015年3月20日 6:53

すべての返信

  • 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

    • 回答の候補に設定 Vivian_Wang 2015年3月31日 2:22
    • 回答としてマーク Vivian_Wang 2015年4月1日 10:05
    2015年3月20日 6:53
  • 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
    • 回答の候補に設定 Martin Sturm 2015年11月11日 1:23
    2015年11月6日 21:51
  • Hello Terri,

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

    Thank you, Anand


    Anand Franklin

    2015年11月7日 15:52
  • 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,

    • 回答の候補に設定 TakisKalf 2017年7月12日 20:34
    2017年3月8日 22:38
  • Thank you,

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

    2017年4月29日 12:32
  • Thank you ...!!!!!

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

    Thanks again.

    2017年7月12日 20:34
  • 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,

    2017年8月20日 12:26
  • Hello Juan.

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

    2017年8月23日 13:48
  • Its worked for me. Thank you very much


    2017年8月28日 10:54
  • 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

    2017年11月7日 20:09
  • thank you Paolo.

    this worked for me.

    regards.

    2017年11月24日 4:14
  • Hi Juan,

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

    Regards,

    Gopal,

    2018年1月11日 12:47
  • Many thanks, Paolo. Your solution worked for me.
    2018年1月15日 12:57
  • Thanks paolo

    its worked for me appriciated

    2018年1月18日 12:37
  • This worked for me. I am so grateful you posted it.

    David Kellett

    2018年6月18日 20:03
  • Thanks, Your solution worked.
    2018年10月6日 3:28
  • Thank you,

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

    2018年11月12日 16:47
  • it works for me
    2018年12月28日 8:28
  • 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



    2019年5月3日 5:03
  • not working 
    2019年7月11日 2:51
  • I was able to resolve this by installing .NET remotely from another computer with the same OS without issue.
    2019年8月22日 7:21
  • THANK YOU, YOU ARE A GENIUS, this save me from my frustration
    2019年10月4日 0:46
  • Depois de tanto tempo sua dica salvou meu dia amigo.

    Obrigado

    2020年4月27日 19:58
  • Great tip!! The command DISM.exe /online /enable-feature /all /featurename:NetFx4  return error:

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3750


    Error: 11

    You cannot service a running 64-bit operating system with a 32-bit version of DISM.
    Please use the version of DISM that corresponds to your computer's architecture.

    Work for me adding feature from other server!!

    Many thanks.

    2020年7月30日 1:58