Windows 服务器管理^{(Windows Server Manager)}器使 IT 人员能够密切关注网络上托管的所有服务器。服务器管理器^{(Server Manager)}工具使 IT 人员能够管理服务器角色，而无需对服务器进行物理访问。如果您无法让服务器管理器^{(Server Manager)}工作，当您单击服务器管理器^{(Server Manager)}时，您会遇到错误消息ServerManager.exe – 此应用程序无法启动^{(ServerManager.exe – This application could not be started)}，那么本文中提供的解决方案旨在帮助您解决问题。

当您遇到此问题时，您将收到以下完整错误消息；

ServerManager.exe – This application could not be started. L?.
This application could not be started.
Do you want to view Information about this issue?

由于以下一种或多种原因，您可能会遇到此错误：

• ServerManager.exe的注册表项无效或损坏。
• 计算机^(Computer)恶意软件注入了恶意代码并修改了ServerManager.exe文件。
• ServerManager.exe文件被其他软件卸载。
• ServerManager.exe文件被其他软件有意或错误地删除。
• 所需版本的ServerManager.exe文件被其他软件覆盖。
• 存在硬件故障，例如硬盘损坏。

ServerManager.exe – 此应用程序无法启动

如果您遇到此问题，您可以尝试以下我们推荐的解决方案（不分先后顺序），看看是否有助于解决问题。

1. 运行 DISM 命令
2. 手动删除 user.config 文件
3. 编辑 ServerList.xml
4. 执行系统还原
5. 执行就地升级修复
6. 格式化并全新安装服务器操作系统

让我们看一下关于列出的每个解决方案所涉及的过程的描述。

1]运行DISM命令

此解决方案要求您使用DISM命令修复/重新安装.NET Frameworks版本 3 和 4 。就是这样：

• 以管理员模式打开命令提示符^{(Open Command Prompt in admin mode)}。
• 在CMD提示窗口中，依次运行以下命令：

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

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

之后，服务器管理器应用程序应该打开而没有错误。

2]手动删除user.config文件

请执行下列操作：

• 按Windows key + E打开文件资源管理器。
• 导航到 C 驱动器中的以下文件路径或包含服务器安装标识为根文件夹的驱动器：

C:\Users\<YourUserName>\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj10.0.0.0user.config

• 在该位置，删除user.config 文件。
• 重新启动服务器管理器^{(Restart Server Manager)}- 这将重新创建文件，还将解决文件已损坏等任何问题。

3]编辑ServerList.xml

如果您正在运行多个服务器操作系统安装，您可能会发现其中一台服务器导致了服务器管理器^{(Server Manager)}错误。您可以通过在其他服务器上打开服务器管理^{(Server Manager)}器并尝试添加服务器来确定这一点。一切都很顺利，直到您尝试在特定服务器上执行相同操作，那时服务器管理器将崩溃并再次停止工作。在这种情况下，您可以编辑ServerList.xml并删除有问题的服务器。服务器管理器^{(Server Manager)}现在应该可以正常工作了。

4]执行系统还原

与客户端操作系统 Windows 10 类似，您可以执行系统还原并查看是否有帮助。这适用于您最近无法启动 服务器管理器^{(Server Manager)} 并且在此之前一切正常的情况。

5]执行就地升级修复

此外，与客户端操作系统 Windows 10^{(OS Windows 10)}类似，您可以执行就地升级修复，看看是否有帮助。

6]格式化^(Format)并全新安装服务器操作系统^{(Server OS)}

作为最后的手段，您可以格式化并全新安装^{(clean install)}服务器操作系统。

希望这里的东西可以帮助你。

ServerManager.exe - This application could not be started

The Windows Server Manager enables the IT staff to keep a tab on all the servers hosted on a network. The Server Manager tool gives IT staff the ability to manage server roles without having physical access to the servers. If you’re unable to get the Server Manager working, whereby when you click on Server Manager, you encounter the error message ServerManager.exe – This application could not be started, then the solutions presented in this post are intended to help you resolve the issue.

When you encounter this issue, you’ll receive the following full error message;

ServerManager.exe – This application could not be started. L?.
This application could not be started.
Do you want to view Information about this issue?

You may encounter this error due to one or more of the following reasons:

• 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.

ServerManager.exe – This application could not be started

If you’re faced with this issue, you can try our recommended solutions below in no particular order and see if that helps to resolve the issue.

1. Run DISM command
2. Manually delete user.config file
3. Edit the ServerList.xml
4. Perform System Restore
5. Perform In-place Upgrade Repair
6. Format and clean install Server OS

Let’s take a look at the description of the process involved concerning each of the listed solutions.

1] Run DISM command

This solution requires you to fix/reinstall .NET Frameworks versions 3 and 4 using the DISM command. Here’s how:

• Open Command Prompt in admin mode.
• In the CMD prompt window, run the following command one after the other:

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

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

Afterward, the server manager application should open without the error.

2] Manually delete user.config file

Do the following:

• Press Windows key + E to open File Explorer.
• Navigate to the file path below in your C drive or the drive housing the server installation identified as the root folder:

C:\Users\<YourUserName>\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj10.0.0.0user.config

• At the location, delete the user.config file.
• Restart Server Manager – this recreates the file and will also address any issues of the file has become corrupted and such.

3] Edit the ServerList.xml

If you have multiple server OS installations running, you may discover that one of the servers is responsible for the Server Manager error. You can determine this by opening Server Manager on the other servers and try adding servers. All goes well until you try doing the same on a particular server, that’s when the server manager would crash and stop working again. In this case, you can edit the ServerList.xml, and remove the problematic server. The Server Manager should work fine now.

4] Perform System Restore

Similar to the client operating system Windows 10, you can perform a system restore and see if that helps. This is applicable if you are unable to start Server Manager only recently and that things worked fine prior to that.

5] Perform In-place Upgrade Repair

Also, similar to the client OS Windows 10, you can perform an In-place Upgrade Repair and see if that helps.

6] Format and clean install Server OS

As a last resort, you can format and clean install the server OS.

Hope something here helps you.

Related posts

• Fix Ca Windows 11上的PIA上没有达到VPN Server error

• Windows无法验证数字签名（Code 52）

• 修复存档以未知格式或损坏错误

• 此功能需要可移动媒体 - Password复位错误

• Fix Microsoft Store在Windows 11/10上登录error 0x801901f4

• 如何在Windows 11/10将Start PXE修复Start PXE

• Error 1327 Invalid Drive安装或卸载程序时

• Fix Error Code 30038-28更新Office时

• Runtime error 429，ActiveX component无法创建对象

• 存根在Windows 10上收到了一个坏data error message

• 该版本不支持此版本的file format，0xC03A0005

• 哎呀！我们无法保存一个 - 的Windows Photos App

• 用户注销Windows 10计算机时Fix Event ID 7031或7034错误

• Fix ShellExecuteEx失败;代码error 8235在Windows10

• Fix Windows 10 Upgrade Install error 0x8007042B - 0x2000D

• 出了错，Turn关anti-virus software，0x8007045d

• 该file install.wim对于destination file system太大

• Fix OOBEKEYBOARD，OOBELOCAL，在Windows OOBEREGION错误

• 错误0x80073D26,0x8007139F或0x00000001游戏service error

• Windows 10中的Fix ShellExecuteEx错误错误