我的 Windows 更新不断失败并出现以下错误：
安装某些更新时出现问题，但我们稍后会重试。如果您继续看到此信息并想搜索网络或联系支持人员获取信息，以下信息可能会有所帮助：
“这可能有帮助”后面只有空白处和重试按钮。按重试只会出现一个小动画，错误又会再次出现。
查看 Windows 更新，我发现软件包 KB3119142 失败了（尽管它已成功安装多次）。我在互联网上看到此更新会导致问题，并且我尝试了有关如何修复它的建议（通过转到“程序和功能”并修复安装）。但仍然没有帮助。
我尝试了互联网上能找到的所有可能的解决方案：
- 运行 sfc /scannow
- 运行 Microsoft WindowsUpdateDiagnostic.diagcab 工具
- 运行 Microsoft ResetWUEng.cmd
- 尝试了几种不同的在线解决方案，包括重新启动服务、删除一些文件等。
什么都没用。以下是 WindowsUpdate.log（通过 Powershell 生成）中最新尝试的摘录：
2016.02.08 22:08:38.1438780 8904 8928 ComApi * START * Init Search ClientId = NULL
2016.02.08 22:08:38.1438819 8904 8928 ComApi * START * Search ClientId = NULL
2016.02.08 22:08:38.1476859 104 1760 Agent * START * Queueing Finding updates [CallerId = <<PROCESS>>: DllHost.exe Id = 5]
2016.02.08 22:08:38.1476937 104 1760 Agent Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
2016.02.08 22:08:38.1479222 8904 8928 ComApi Search ClientId = NULL
2016.02.08 22:08:38.4485033 104 5996 ProtocolTalker PTInfo: syncing with server using normal query
2016.02.08 22:08:39.6122826 104 5996 ProtocolTalker SyncUpdates round trips: 22
2016.02.08 22:08:39.6159627 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C18&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:39.6159636 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6160245 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C18}
2016.02.08 22:08:39.6160705 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_0100&SUBSYS_844D1043&REV_09
2016.02.08 22:08:39.6160708 104 5996 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:39.6160783 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_0100}
2016.02.08 22:08:39.6161095 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_05
2016.02.08 22:08:39.6161095 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6161314 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C2D}
2016.02.08 22:08:39.6161722 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C26&SUBSYS_844D1043&REV_05
2016.02.08 22:08:39.6161722 104 5996 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:39.6161842 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C26}
2016.02.08 22:08:39.6162098 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_0101&SUBSYS_844D1043&REV_09
2016.02.08 22:08:39.6162101 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6162371 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_0101}
2016.02.08 22:08:39.6162545 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C44&SUBSYS_844D1043&REV_05
2016.02.08 22:08:39.6162548 104 5996 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:39.6162899 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C44}
2016.02.08 22:08:39.6162965 104 5996 Driver Matched driver to device ACPI\VEN_INT&DEV_3F0D
2016.02.08 22:08:39.6162965 104 5996 Driver Status: 0x41802000, ProblemNumber: 00000000
2016.02.08 22:08:39.6163403 104 5996 Driver DrvUtil: {ACPI\INT3F0D}
2016.02.08 22:08:39.6163542 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C22&SUBSYS_844D1043&REV_05
2016.02.08 22:08:39.6163545 104 5996 Driver Status: 0x1802000, ProblemNumber: 00000000
2016.02.08 22:08:39.6163935 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C22}
2016.02.08 22:08:39.6164247 104 5996 Driver Matched driver to device USB\VID_0B05&PID_179C&REV_0001
2016.02.08 22:08:39.6164250 104 5996 Driver Status: 00000000, ProblemNumber: 00000000
2016.02.08 22:08:39.6164547 104 5996 Driver DrvUtil: {usb\vid_0b05&pid_179c}
2016.02.08 22:08:39.6164625 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C1C&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:39.6164628 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6165076 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C1C}
2016.02.08 22:08:39.6165301 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C1E&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:39.6165304 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6165604 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C1E}
2016.02.08 22:08:39.6165703 104 5996 Driver Matched driver to device PCI\VEN_8086&DEV_1C10&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:39.6165706 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6166129 104 5996 Driver DrvUtil: {PCI\VEN_8086&DEV_1C10}
2016.02.08 22:08:39.6166408 104 5996 Driver Matched driver to device PCI\VEN_10DE&DEV_13C2&SUBSYS_13C210DE&REV_A1
2016.02.08 22:08:39.6166408 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6166661 104 5996 Driver DrvUtil: {PCI\VEN_10DE&DEV_13C2}
2016.02.08 22:08:39.6166751 104 5996 Driver Matched driver to device PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06
2016.02.08 22:08:39.6166754 104 5996 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:39.6167183 104 5996 Driver DrvUtil: {PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06}
2016.02.08 22:08:39.6167360 104 5996 Driver DrvUtil: {usbprint\hewlett-packardhp_la5a02}
2016.02.08 22:08:41.1568919 104 5996 ProtocolTalker ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016.02.08 22:08:41.1568934 104 5996 ProtocolTalker OK to reuse existing configuration
2016.02.08 22:08:41.1568958 104 5996 ProtocolTalker Existing cookie is valid, just use it
2016.02.08 22:08:41.6673071 104 5996 Agent Added update B176D5A0-9EFC-404F-BEE7-BCD6CAE6226B.200 to search result
2016.02.08 22:08:41.6673113 104 5996 Agent Added update 4A2305D9-E940-48E6-9CE4-D11964F7DC2F.200 to search result
2016.02.08 22:08:41.6673143 104 5996 Agent Added update 9388C4AD-970E-4D1E-BDF6-20C206192BB1.200 to search result
2016.02.08 22:08:41.6673173 104 5996 Agent Added update B69DEC14-F236-48A1-AA30-30A5293A54CB.200 to search result
2016.02.08 22:08:41.6673203 104 5996 Agent Added update DD696945-7B9D-41D4-A8DC-7589DC414CC6.200 to search result
2016.02.08 22:08:41.6673236 104 5996 Agent Added update 26CCDB78-D852-4EDD-91CF-76956D5EEE63.200 to search result
2016.02.08 22:08:41.6673263 104 5996 Agent Added update 83F87564-25D9-4044-9A89-781714992321.200 to search result
2016.02.08 22:08:41.6673290 104 5996 Agent Added update 077DA652-E8B5-4E59-BBB4-79AE56991BF0.200 to search result
2016.02.08 22:08:41.6673407 104 5996 Agent Added update E80BB0B5-277A-4208-9296-7F16488E409B.200 to search result
2016.02.08 22:08:41.6673437 104 5996 Agent Added update AF090FC3-1779-4EC8-8C63-8A84C0B3E5FB.200 to search result
2016.02.08 22:08:41.6673467 104 5996 Agent Added update F8E06312-3A36-4868-8CE5-A6BEFF34A294.200 to search result
2016.02.08 22:08:41.6673494 104 5996 Agent Added update 2B11F691-8DB6-4985-9B7C-C0481E7556E3.200 to search result
2016.02.08 22:08:41.6673527 104 5996 Agent Added update EDE0C184-119B-442F-A6F7-6B014FD64727.200 to search result
2016.02.08 22:08:41.6673558 104 5996 Agent Added update 19978BC2-2F56-48D0-92A9-C5CA7B04F121.201 to search result
2016.02.08 22:08:41.6673585 104 5996 Agent Added update C38BEDE9-86AD-4337-81A4-16E6914980DB.208 to search result
2016.02.08 22:08:41.6675929 104 5996 Agent Found 15 updates and 21 categories in search; evaluated appl. rules of 757 out of 1240 deployed entities
2016.02.08 22:08:41.6795172 104 5996 Agent * END * Finding updates CallerId = Device Driver Retrieval Client Id = 3
2016.02.08 22:08:41.6900431 104 1764 ComApi *RESUMED* Search ClientId = Device Driver Retrieval Client
2016.02.08 22:08:41.6918584 104 8992 Agent * END * Queueing Finding updates [CallerId = <<PROCESS>>: DllHost.exe Id = 5]
2016.02.08 22:08:41.6928935 104 8992 Agent * START * Finding updates CallerId = <<PROCESS>>: DllHost.exe Id = 5
2016.02.08 22:08:41.6928944 104 8992 Agent Online = Yes; Ignore download priority = No
2016.02.08 22:08:41.6928950 104 8992 Agent Criteria = ( IsInstalled = 0 and IsHidden = 0 )""
2016.02.08 22:08:41.6928983 104 8992 Agent ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016.02.08 22:08:41.6928986 104 8992 Agent Search Scope = {Machine}
2016.02.08 22:08:41.6929010 104 8992 Agent Caller SID for Applicability: S-1-5-18
2016.02.08 22:08:41.6929019 104 8992 Agent RegisterService is set
2016.02.08 22:08:41.6943437 104 8992 Misc Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: 7971f918-a847-4430-9279-4a52d1efe18d""
2016.02.08 22:08:41.6974711 104 1764 ComApi Updates found = 15
2016.02.08 22:08:41.6974717 104 1764 ComApi * END * Search ClientId = Device Driver Retrieval Client
2016.02.08 22:08:41.6978389 104 1548 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2016.02.08 22:08:41.6994860 104 8992 Misc Got 7971F918-A847-4430-9279-4A52D1EFE18D redir Client/Server URL: https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx""
2016.02.08 22:08:42.0066264 104 8992 ProtocolTalker ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016.02.08 22:08:42.0066345 104 8992 ProtocolTalker OK to reuse existing configuration
2016.02.08 22:08:42.0066369 104 8992 ProtocolTalker Existing cookie is valid, just use it
2016.02.08 22:08:42.9943524 104 8992 WebServices Auto proxy settings for this web service call.
2016.02.08 22:08:49.8519573 104 8992 ProtocolTalker PTInfo: syncing with server using normal query
2016.02.08 22:08:51.0387275 104 8992 ProtocolTalker SyncUpdates round trips: 2
2016.02.08 22:08:51.0472755 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C18&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:51.0472761 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0473455 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C18}
2016.02.08 22:08:51.0473899 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_0100&SUBSYS_844D1043&REV_09
2016.02.08 22:08:51.0473902 104 8992 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:51.0473977 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_0100}
2016.02.08 22:08:51.0474277 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C2D&SUBSYS_844D1043&REV_05
2016.02.08 22:08:51.0474280 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0474494 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C2D}
2016.02.08 22:08:51.0474890 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C26&SUBSYS_844D1043&REV_05
2016.02.08 22:08:51.0474890 104 8992 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:51.0475007 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C26}
2016.02.08 22:08:51.0475256 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_0101&SUBSYS_844D1043&REV_09
2016.02.08 22:08:51.0475256 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0475520 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_0101}
2016.02.08 22:08:51.0475688 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C44&SUBSYS_844D1043&REV_05
2016.02.08 22:08:51.0475691 104 8992 Driver Status: 0x180000a, ProblemNumber: 00000000
2016.02.08 22:08:51.0476033 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C44}
2016.02.08 22:08:51.0476097 104 8992 Driver Matched driver to device ACPI\VEN_INT&DEV_3F0D
2016.02.08 22:08:51.0476100 104 8992 Driver Status: 0x41802000, ProblemNumber: 00000000
2016.02.08 22:08:51.0476526 104 8992 Driver DrvUtil: {ACPI\INT3F0D}
2016.02.08 22:08:51.0476658 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C22&SUBSYS_844D1043&REV_05
2016.02.08 22:08:51.0476661 104 8992 Driver Status: 0x1802000, ProblemNumber: 00000000
2016.02.08 22:08:51.0477039 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C22}
2016.02.08 22:08:51.0477342 104 8992 Driver Matched driver to device USB\VID_0B05&PID_179C&REV_0001
2016.02.08 22:08:51.0477345 104 8992 Driver Status: 00000000, ProblemNumber: 00000000
2016.02.08 22:08:51.0477634 104 8992 Driver DrvUtil: {usb\vid_0b05&pid_179c}
2016.02.08 22:08:51.0477709 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C1C&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:51.0477712 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0478147 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C1C}
2016.02.08 22:08:51.0478366 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C1E&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:51.0478366 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0478657 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C1E}
2016.02.08 22:08:51.0478756 104 8992 Driver Matched driver to device PCI\VEN_8086&DEV_1C10&SUBSYS_844D1043&REV_B5
2016.02.08 22:08:51.0478759 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0479171 104 8992 Driver DrvUtil: {PCI\VEN_8086&DEV_1C10}
2016.02.08 22:08:51.0479498 104 8992 Driver Matched driver to device PCI\VEN_10DE&DEV_13C2&SUBSYS_13C210DE&REV_A1
2016.02.08 22:08:51.0479501 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0479921 104 8992 Driver DrvUtil: {PCI\VEN_10DE&DEV_13C2}
2016.02.08 22:08:51.0480020 104 8992 Driver Matched driver to device PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06
2016.02.08 22:08:51.0480020 104 8992 Driver Status: 0x180200a, ProblemNumber: 00000000
2016.02.08 22:08:51.0480698 104 8992 Driver DrvUtil: {PCI\VEN_10EC&DEV_8168&SUBSYS_84321043&REV_06}
2016.02.08 22:08:51.0480867 104 8992 Driver DrvUtil: {usbprint\hewlett-packardhp_la5a02}
2016.02.08 22:08:52.6314830 104 8992 ProtocolTalker ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx
2016.02.08 22:08:52.6314848 104 8992 ProtocolTalker OK to reuse existing configuration
2016.02.08 22:08:52.6314878 104 8992 ProtocolTalker Existing cookie is valid, just use it
2016.02.08 22:08:52.8183480 104 8992 Agent Update 5AF4FF91-E9A7-45B3-841F-AE886BB3C658.201 is pruned out due to potential supersedence
2016.02.08 22:08:52.8183543 104 8992 Agent Added update B176D5A0-9EFC-404F-BEE7-BCD6CAE6226B.200 to search result
2016.02.08 22:08:52.8183558 104 8992 Agent Update 81E92824-528F-4583-B074-406D9ED8701B.200 is pruned out due to potential supersedence
2016.02.08 22:08:52.8183585 104 8992 Agent Added update 4A2305D9-E940-48E6-9CE4-D11964F7DC2F.200 to search result
2016.02.08 22:08:52.8183612 104 8992 Agent Added update 9388C4AD-970E-4D1E-BDF6-20C206192BB1.200 to search result
2016.02.08 22:08:52.8183639 104 8992 Agent Added update B69DEC14-F236-48A1-AA30-30A5293A54CB.200 to search result
2016.02.08 22:08:52.8183663 104 8992 Agent Added update DD696945-7B9D-41D4-A8DC-7589DC414CC6.200 to search result
2016.02.08 22:08:52.8183685 104 8992 Agent Added update 26CCDB78-D852-4EDD-91CF-76956D5EEE63.200 to search result
2016.02.08 22:08:52.8183712 104 8992 Agent Added update 83F87564-25D9-4044-9A89-781714992321.200 to search result
2016.02.08 22:08:52.8183736 104 8992 Agent Added update 077DA652-E8B5-4E59-BBB4-79AE56991BF0.200 to search result
2016.02.08 22:08:52.8183817 104 8992 Agent Added update E80BB0B5-277A-4208-9296-7F16488E409B.200 to search result
2016.02.08 22:08:52.8183844 104 8992 Agent Added update AF090FC3-1779-4EC8-8C63-8A84C0B3E5FB.200 to search result
2016.02.08 22:08:52.8183868 104 8992 Agent Added update F8E06312-3A36-4868-8CE5-A6BEFF34A294.200 to search result
2016.02.08 22:08:52.8183889 104 8992 Agent Added update 2B11F691-8DB6-4985-9B7C-C0481E7556E3.200 to search result
2016.02.08 22:08:52.8183904 104 8992 Agent Update 95B42BE3-50BA-4AD2-908B-AF3F10304827.201 is pruned out due to potential supersedence
2016.02.08 22:08:52.8183928 104 8992 Agent Added update EDE0C184-119B-442F-A6F7-6B014FD64727.200 to search result
2016.02.08 22:08:52.8183952 104 8992 Agent Added update 547D2F41-089B-448F-9265-79579EC92F80.200 to search result
2016.02.08 22:08:52.8183997 104 8992 Agent Added update 077DB01E-86F1-445A-BEF8-4B5DE97C899E.204 to search result
2016.02.08 22:08:52.8184021 104 8992 Agent Added update 19978BC2-2F56-48D0-92A9-C5CA7B04F121.201 to search result
2016.02.08 22:08:52.8184066 104 8992 Agent Added update C38BEDE9-86AD-4337-81A4-16E6914980DB.208 to search result
2016.02.08 22:08:52.8184075 104 8992 Agent Found 17 updates and 89 categories in search; evaluated appl. rules of 1442 out of 2019 deployed entities
2016.02.08 22:08:52.8287437 104 8992 Agent * END * Finding updates CallerId = <<PROCESS>>: DllHost.exe Id = 5
2016.02.08 22:08:52.8385699 8904 8924 ComApi *RESUMED* Search ClientId = NULL
2016.02.08 22:08:52.8452030 8904 8924 ComApi Updates found = 17
2016.02.08 22:08:52.8452036 8904 8924 ComApi * END * Search ClientId = NULL
2016.02.08 22:08:52.8473686 8904 8928 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2016.02.08 22:09:35.1743632 104 3556 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
从日志中可以看出，有相当多的更新需要安装。但没有信息说明为什么会失败。事件日志都正常，没有任何错误或警告。
答案1
Windows 10 更新的最佳解决方案是使用第三方软件来安装和隐藏更新。
它无需安装任何内容，它是便携式的，它允许您隐藏任何更新，包括驱动程序。此软件不会对正常的 Windows 更新或您的系统进行任何更改（您允许它安装的更新除外），但会使用 Windows 更新服务，一旦您隐藏了更新并安装了您想要的其他更新，请务必进入 Windows 服务并停止 Windows 更新服务，然后将其设置为禁用，否则它将安装您使用其他软件隐藏的更新。
因此，请保持 Windows 更新服务处于禁用状态，迷你工具将在您运行它时自动启动它，然后在使用完迷你工具后再次将其禁用。
下载链接用于迷你工具
答案2
打开（桌面）控制面板，转到程序和功能，选择 VC++ 2012 运行时条目，单击修改并选择修复。
此后再次安装 VC++ 更新即可工作。
答案3
我想我找到了答案，所以我在这里发布它，以便它可以帮助其他被 Windows 10 这个丑陋怪物困住的池中灵魂。虽然每个人都声称无法控制 Windows 更新，但有一个 Microsoft 工具可用于禁用名为“显示或隐藏更新”的更新。该工具可以在这里找到：https://support.microsoft.com/en-us/kb/3073930 该工具旨在用于防止安装有故障的驱动程序，看来这就是我这边发生的情况。
我运行了该工具并禁用了打印机的 HP 驱动程序，现在更新显示我的设备已是最新的。
奇怪的是，还有其他几个更新我也可以禁用，但即使它们出现在“显示或隐藏更新”工具的更新列表中，Windows 更新也声称没有更新。
目前我不知道为什么其余的更新无法安装。