2019.12月发现累积几个月的更新没有重启动，

重启动后BIOS模式也遇到启动自动进入恢复模式了,使用

dism.exe /image:c:\ /cleanup-image /revertpendingactions

取消更新，正常启动后继续安装更新正常。

————————————————————————————————————————————————————————

早期原文：

EFI模式请慎重安装KB4512486 KB4512506  KB4512514

物理机或者虚拟机EFI模式启动将有问题，BIOS模式启动的没问题！

IA64 设备（在任何配置中）和使用预配的 EFI 启动的 x64 设备在安装 7 月 9 日的更新和/或跳过建议的更新 (KB3133977) 之后，可能无法启动并出现以下错误：

“文件: \Windows\system32\winload.efi

状态: 0xc0000428

信息: Windows 无法验证此文件的数字签名。”

要解决此问题，请按照针对错误代码 0xC0000428 的 SHA-2 支持常见问题解答文章中概述的步骤进行操作。

IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error:

"File: \Windows\system32\winload.efi

Status: 0xc0000428

Info: Windows cannot verify the digital signature for this file."

To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428.

处理方法如下：

自动进入修复模式,界面如下（如没自动进入修复模式，也可以从安装光盘引导，选择R进入修复模式）：

也可使用MSDaRT 光盘(不需要本地Administrator帐号密码)MSDaRT 全称是：Microsoft Diagnostics and Recovery Toolset（微软诊断和恢复工具集）

此时按下一步按钮,之后的界面选命令行恢复,在命令行提示符下输入dism.exe /image:c:\ /cleanup-image /revertpendingactions

如下图：

完成后按提示选择重启动,系统可以启动到更新回滚界面,如下图：

回滚完成后可正常登录系统；

登录系统后需要先安装KB3133977更新，重启动系统后再安装KB4512486 KB4512506 KB4512514；

以上修复方法经过测试。

另一种方法，恢复模式下DISM安装KB3133977更新包，测试重启动后还是进入恢复模式,不能恢复正常,该方法无效。

操作命令如下：

再另一种方法，恢复模式下删除更新包，测试重启动后还是进入恢复模式,不能恢复正常,该方法无效。

操作命令如下：

参考国外谈论：

Site Feedback

FE

Fearless96Created on August 17, 2019

KB4512506 / KB4512486 winload.efi Windows cannot verify the digital signature

TLDR - After you uninstall the broken update to get your OS working again, install KB3133977 and try again.

The full story:

Until I fixed it, I couldn't boot after installing KB4512506 or KB4512486 - Windows cannot verify the digital signature of winload.efi.

On the first boot failure I had to recreate the BCD. On every subsequent failure I had to uninstall the update via the recovery console.

I already had KB4474419-v2 installed and no 3rd party antivirus. Dism /Online /Cleanup-Image /CheckHealth found no corruption.

I restored a system image to a spare HDD and booted it to troubleshoot. I found that installing all optional updates fixed the issue. I didn't want that to be the solution for my permanent OS so I investigated further. I eventually installed only KB3133977 to fix the issue. (That update is for a BitLocker issue but I don't use BitLocker. I don't know why it helped.)

Reply

I recommend this discussion (81)

Discussion Info

Last updated September 9, 2019Views 2,167Applies to:

  • Windows 7
  • /
  • Windows update, recovery, & backup

Replies (3) 

DA

DannyMosesReplied on August 20, 2019

Thank you for the tip.  Downloading and installing KB3133977 allowed me to finally, successfully install KB4512506 on my Windows 7 SP1 X64 system.

Reply

Up vote (7)

ED

EdwardG1345Replied on August 22, 2019

This fix applies to Windows Server 2008 R2 as well.  After installing, in August 2019, Microsoft Security Only Patch KB4512486, all our physical 2008 R2s rebooted into System Recovery and the only fix we could find was to revert via "dism.exe /image:C:\ /cleanup-image /revertpendingactions".  Needless to say, this prevented the patch from being installed.  I recently found this post, gave it a shot with the 2008 R2 x64 version of KB3133977, and now the servers are good to go.  Thanks for finding this.

Reply

Up vote (9)

SL

sleightyReplied on August 27, 2019

Just an FYI for those having issues getting KB3133977 to install - KB3125574 supersedes 3133977.

https://support.microsoft.com/en-us/help/3125574/convenience-rollup-update-for-windows-7-sp1-and-windows-server-2008-r2

Reply

Up vote (4)

Windows Updates KB4512506/KB4512486 drops error 0x80092004

Posted on 2019-08-14 by guenni

[German]A brief information for users who install the August 2019 security updates KB4512506 or KB4512486 for Windows 7 SP1 and Windows Server 2008 R2 in an installation error 0x80092004. It is highly likely that updates to retrofit SHA-2 support will then be missing.

Advertising

Users report error 0x80092004

It didn’t take long after the release of the security updates KB4512506 (Monthly Rollup) or KB4512486 (Security Only) for Windows 7 SP1 and Windows Server 2008 R2 until the first users reported issues within my German blog. German blog reader Heidemann wrote in this comment:

The attempt to install the update to W2K8R2 fails here with Installation Failure: Windows failed to install the following update with error 0x80092004: Security Update for Windows (KB4512486).

No Symantec or Norton (but McAfee) on the systems.

And a short time later M. Gruber posted this comment with the same tenor, but to another German blog post.

I repeatedly fail to install KB4512506 (Monthly Security Quality Rollup) with code 80092004 under a naked Win7 x64 without AV software.
Am I the only one or is there a workaround?

The user then pointed out similar feedback from users in the English DSL forum.

I can’t install KB4512506 on two different Windows 7 64 bit systems. Each one fails with the error code: 80092004. Multiple restarts and retries result in same error. Anyone else seeing this?

I found also a japanese post mentions this error code without giving further hints.

The error has already occurred with .NET

I mentioned the error code 0x80092004 in some blog posts (see links at the end of the article) and Microsoft also published a KB article about the error. However, this KB article refers to a bug in the .NET framework that prevents updates from being installed. However, I don’t consider this to be a valid cause, as these are currently Windows updates.

Advertising

What does error code 0x80092004 stands for?

Before you start any wild experiments, it’s good to know what the cause of the error is. The error code 0x80092004 stands for CRYPT_E_NOT_FOUND. Windows Update could not find any cryptographic value and rejects the update.

There was something SHA-2 signing?

I had it mentioned in the blog post Symantec/Norton blocks Windows Updates (SHA-2). Microsoft changed the signing of update packages for Windows 7 SP1 and Windows Server 2008/R2 for the first time in August 2019. Instead of signing the packages with both SHA-1 and SHA-2, only a SHA-2 hash value is stored in the package. The above error code indicates that Windows Update is looking for the SHA-1 signature in the package and does not find it.

What should be checked

One possibility is that an external virus scanner recognizes and modifies the update packets incorrectly. The blog post Symantec/Norton blocks Windows Updates (SHA-2) mentions that Symantec and Norton security solutions cause trouble. In this scenario, however, Microsoft blocks the delivery of security updates.

Weighting the above information, there is a lot of evidence that the support for the new updates and Windows signed exclusively by SHA-2 is simply missing. As of March 12, 2019, Microsoft had extended support article 4472027 (2019 SHA-2 Code Signing Support requirement for Windows and WSUS) to include the SHA-2 updates required for Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1, and Windows Server 2008 Service Pack 2.

  • Update KB4474419 (SHA-2 code signing support update for Windows Server 2008 R2 and Windows 7: March 12, 2019) adds support for SHA-2 signature checks for the above operating systems.
  • In addition, the Servicing Stack Update KB4490628 was published in March 2019. This fixes a problem in the Servicing Stack, which occurs as soon as packages are signed with SHA-2 only.

I had mentioned within my blog post Windows 7: Updates for SHA-2 support, that it’s required both updates are installed. Within my German comment here I had recommended checking to see if the relevant updates were available. In fact, blog reader M. Gruber reported here that the SSU KB4490628 was missing on his machine. After installing the Servicing Stack Update (SSUs) from March 2019, the August 2019 security update for Windows 7 SP1 and Windows Server 2008 R2 was successfully installed. And I got a 2nd feedback, that this was the root cause for the update install error. Perhaps it will help one or the other affected person.

Similar articles
Fix for .Net Framework Update KB4340558 error 0x80092004
.Net Framework: Update KB4340558 drops error 0x80092004?
Patchday: Updates for Windows 7/8.1/Server (August 13, 2019)
Symantec/Norton blocks Windows Updates (SHA-2)
Windows 7: Updates for SHA-2 support

注意： 如何解决Windows Server 2008 R2 EFI启动模式安装2019年8月更新KB4512486 KB4512506  KB4512514后自动进入修复模式，无法正常启动问题！！！相关推荐

  1. 在Windows Server 2008 R2(64位)上安装SharePoint 2007出现的一个错误的解决方法

    昨天在 Windows Server 2008 R2(64位)上安装 SharePoint2007,没想到压缩包解压完毕后立即弹出一个错误提示框: 提示:"Internet 信息服务(IIS ...

  2. 解决 Windows server 2008 R2 DataCenter 不能安装 .NETFramework4.6.1

    解决 Windows server 2008 R2 DataCenter 不能安装 .NETFramework4.6.1 转载地址 https://blog.csdn.net/jackrong/art ...

  3. Windows Server 2008 R2 活动目录的安装和配置

    Windows Server 2008 R2 活动目录的安装和配置 我所用的版本是 <cn_windows_server_2008_r2_hpc_edition_with_service_pac ...

  4. mysql无法安装 server 2008 r2_【运维】windows server 2008 R2 Standard中如何安装 mysql8.0

    场景描述 操作系统:windows server 2008 R2 Standard x64 待安装mysql版本: mysql8.0.12(免安装压缩包版,需对数据库进行初始化操作) 安装时出现缺少x ...

  5. 解决Windows Server 2008 R2安装声卡驱动后还是提示无音频设备的问题

    之前使用windows server 2008 R2,都没有用的声音播放的功能,所以一般情况下都不安装声卡驱动,或者装了也没用上,所以也没发现问题.今天正好有个项目需要用声卡播放告警语音,所以需要用到 ...

  6. 程序不支持新服务器,解决Windows Server 2008 R2的兼容性问题

    尽管大多数的新应用程序在Windows Server 2008 R2上运行得还算不错,但有些为旧版操作系统所写的应用程序可能无法在R2上安装或运行.幸运的是,有几种方法能解决这些兼容性的挑战. 及时更 ...

  7. 解决Windows Server 2008 R2无法保存网络发现状态更改问题

    原文来自jkd395的BLOG鹤舞长空,链接于http://jkd395.blog.51cto.com/640716/364848 原文有图片,CSDN转载时不能引用,不发图了,很简单. 在Windo ...

  8. 解决Windows Server 2008 R2域控备份提示VSS卷影复制失败 0x800423F4

    解决 2008R2域控备份 提示"卷影复制失败 0x800423F4 " 1. 问题描述: 做好域控制器后,使用Windows Server Backup 备份时,出现" ...

  9. 解决Windows server 2008 R2无法更新系统，提示：windows update无法检查更新,错误代码80072EFE 问题

    一.问题现象 widow server2008在系统更新时无法更新,提示以下报错 二.解决办法 1.首先检查下驱动有没有问题,把基本该有的驱动打上,然后再检测,如果还是不行.请参照第二步. 2.(1) ...

最新文章

  1. dubbo admin默认端口_Dubbo学习(四) Dubbo 从下载到编译成功
  2. win mysql 2003错误_windows MySql 报1067错误 2003错误
  3. 解决 dubbo问题：Forbid consumer 192.xx.xx.1 access service com.xx.xx.xx.rpc.api.xx from registry 116.xx1
  4. Chapter2-1_Voice Conversion(Feature Disentangle)
  5. java字符流和字节流的区别_java字符流与字节流的区别是什么
  6. 常见HTTP状态(404,500等)
  7. oc73--NSArray使用
  8. github 创建团队_如何为团队创建影响图
  9. c语言编程继承例子,C语言模拟实现C++的继承与多态示例
  10. iptraf：一个实用的TCP/UDP网络监控工具
  11. 移动终端开发必备知识（转载）
  12. Android相关笔记-4
  13. python的自定义异常类，带参Exception,多个except，断言语句，断点，try...except，try...except...else,try...except...finally处理
  14. 文本嵌入的经典模型与最新进展
  15. flutter的PDF阅读器
  16. 【毕业设计】深度学习 python opencv 火焰检测识别
  17. 三菱plc指令dediv_三菱 PLC梯型图（指令编码）反汇编程序--开源 PLC 编程重点参考资料...
  18. 中国500强企业是如何构建电子签章系统的？
  19. 【分立元件】电感器（inductor）——简介
  20. 在Edge浏览器中设置编码方式

热门文章

  1. cad2017单段线_CAD中如何绘制多段线
  2. 运放的原理、应用、参数和命名规则
  3. 【工业互联网】余晓晖：工业互联网发展态势与展望
  4. c语言单片机教程,开发板选择
  5. Spring源码学习第四天==＞初识Refresh()
  6. 微信公众号自定义菜单添加emoji表情图标
  7. 如何安装正版的Xmanager
  8. 前端白屏问题_小程序白屏问题和内存解决方法
  9. 音频处理-1 基础知识
  10. 设计必备，5个免费图标资源网站