none
Windows Server 2012 R2 更新补丁后无法显示桌面 RRS feed

  • 问题

  • 例行维护服务器安装补丁并重启服务器,有补丁更新提示安装,安装后重启服务器。配置更新应用重启了两次,第三次可以输入用户名和密码的界面,但是进入系统后桌面是黑色的没有图标,只有一个CMD的窗口,类似于windows server 核心版的样子。我不清楚是否和补丁更新有关,又重启了两次还是没有桌面图标,也无法打开任务管理器。

    所以我在上网找到了core版的命令,需要将核心模式core 变回完整模式 Full,用dism命令。

    dism  /online  /enable-feature  /all  /featurename:servercore-fullserver  /featurename:server-gui-shell  /featurename:server-gui-mgmt

    等了10多分钟依然没有反应,我就重启了服务器,这是服务器又显示更新配置,我不知道是不是这条命令生效了还是之前的补丁更新没有完全完成。之后就可以进入到桌面了。

    在网上 也查过有朋友说是卸载了.net framework但是我这里根本就没有装过.net,更没有卸载过。

    百思不得其解,求大神解答,担心下次重启服务器还会发生这种问题。

    PS:现在服务器是可以使用了。附上次更新的补丁:

    2018年8月23日 6:24

全部回复

  • 暂时不能发图片。。更新的补丁大多是安全新的和update的补丁,

    KB3178539
    KB3156059
    KB3121461
    KB3109103
    KB3091297
    KB3087137
    KB3086255
    KB3061512
    KB3055323
    KB3054256
    KB3046737
    KB3045717
    KB3044673
    KB3043812
    KB3036612
    KB3035126
    KB3024755
    KB3019978
    KB3013172
    KB2989930
    KB2965500
    KB2954879
    KB4338831
    KB3118401

    2018年8月23日 6:30
  • 你好,

    感谢在此回帖。

    • 上次更新是什么时候,我看到有些补丁是几年前的了。
    • 从目前的信息来看,很大可能是更新出错或者没有完成。因为其中有的补丁是对图形界面的补漏。
    • 另外看一下系统日志,有没有相关的报错。
    • 为了避免下次更新时再次出现错误,我建议您在更新之前设置一个系统还原点。如果出现了不可修复的错误,直接系统还原。

    祝您工作顺利!

    Travis


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    2018年8月24日 3:32
    版主
  • 系统是前几个月新装的,可能以前的补丁没有安装全。

    关于系统日志有如下几个报错,

    Event ID 7023

    The Windows Modules Installer service terminated with the following error:
    The process cannot access the file because it is being used by another process.

    Event ID 10149

    The WinRM service is not listening for WS-Management requests.

     User Action
     If you did not intentionally stop the service, use the following command to see the WinRM configuration:

     winrm enumerate winrm/config/listener

    Event ID 27

    HP Ethernet 1Gb 2-port 361i Adapter #2
     Network link is disconnected.

    Event ID 7009

    A timeout was reached (30000 milliseconds) while waiting for the SQL Server CEIP service (MSSQLSERVER) service to connect.

    Event ID 7000

    The SQL Server CEIP service (MSSQLSERVER) service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion.

    Event ID 2511

    The server service was unable to recreate the share WSUSTemp because the directory C:\Program Files\Update Services\LogFiles\WSUSTemp no longer exists.  Please run "net share WSUSTemp /delete" to delete the share, or recreate the directory C:\Program Files\Update Services\LogFiles\WSUSTemp.

    Event ID 10010

    The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.

    Event ID 7022

    The McAfee ePolicy Orchestrator 5.9.1 Server service hung on starting.

    Event ID 6038

    Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
     
    NTLM is a weaker authentication mechanism. Please check:
     
          Which applications are using NTLM authentication?
          Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication?
          If NTLM must be supported, is Extended Protection configured?
     
    Details on how to complete these checks can be found at

    Event ID 5009

    A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '7300'. The process exit code was '0xfffffffe'.

    Event ID 5002

    Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

    Event ID 5719

    This computer was not able to set up a secure session with a domain controller in domain XFNQA due to the following:
    There are currently no logon servers available to service the logon request.
    This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. 

    ADDITIONAL INFO
    If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

    请帮忙查下看日志里有相关内容吗?

    2018年8月24日 5:31
  • 你好,

    从日志中没有找到有关更新的报错。

    只能在下次更新时,提前做好准备。

    祝您周末愉快,

    Travis


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    2018年8月24日 9:25
    版主