Windows 更新疑难解答Windows Update troubleshooting

适用于:Windows 10Applies to: Windows 10

如果在使用 Windows 更新时遇到问题,不妨从以下步骤着手:If you run into problems when using Windows Update, start with the following steps:

  1. 运行内置的 Windows 更新疑难解答来解决常见问题。Run the built-in Windows Update troubleshooter to fix common issues. 导航到设置 > 更新和安全性 > 疑难解答 > Windows 更新Navigate to Settings > Update & Security > Troubleshoot > Windows Update.

  2. 从 Microsoft 更新目录中安装与你的 Windows 版本相匹配的最新服务堆栈更新 (SSU)。Install the most recent Servicing Stack Update (SSU) that matches your version of Windows from the Microsoft Update Catalog. 请参阅服务堆栈更新,获取关于服务堆栈更新的更多详细信息。See Servicing stack updates for more details on servicing stack updates.

  3. 请务必安装最新的 Windows 更新、累积更新和汇总更新。Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. 若要验证更新状态,请参阅系统相应的更新历史记录:To verify the update status, refer to the appropriate update history for your system:

高级用户还可以参阅 Windows 更新生成的日志,以便进一步调查。Advanced users can also refer to the log generated by Windows Update for further investigation.

使用 Windows 更新时,可能会遇到以下情况。You might encounter the following scenarios when using Windows Update.

为什么给我提供的是旧版更新?Why am I offered an older update?

提供给设备的更新取决于多种因素。The update that is offered to a device depends on several factors. 以下是一些最常见的属性:The following are some of the most common attributes:

  • 操作系统内部版本OS Build
  • 操作系统分支OS Branch
  • 操作系统区域设置OS Locale
  • 操作系统体系结构OS Architecture
  • 设备更新管理配置Device update management configuration

如果为你提供的更新不是最新的可用版本,这可能是因为你的设备由 WSUS 服务器管理,并且你正在该服务器上获得可用更新。If the update you're offered isn't the most current available, it might be because your device is being managed by a WSUS server, and you're being offered the updates available on that server. 如果你的设备是部署组的一部分,管理员也可能有意减慢更新的推出速度。It's also possible, if your device is part of a deployment group, that your admin is intentionally slowing the rollout of updates. 由于刚开始部署时速度较慢且慎重,因此并非所有设备都会在同一天收到更新。Since the deployment is slow and measured to begin with, all devices will not receive the update on the same day.

我的设备在扫描时冻结。My device is frozen at scan. 为什么?Why?

设置 UI 与更新 Orchestrator 服务通信,而更新 Orchestrator 服务又与 Windows 更新服务通信。The Settings UI communicates with the Update Orchestrator service that in turn communicates with to Windows Update service. 如果这些服务意外停止,你可能会看到此行为。If these services stop unexpectedly, then you might see this behavior. 在此类情况下,请按照以下步骤操作:In such cases, follow these steps:

  1. 关闭“设置”应用并重新将其打开。Close the Settings app and reopen it.

  2. 启动 Services.msc 并检查以下服务是否正在运行:Start Services.msc and check if the following services are running:

    • 更新状态 OrchestratorUpdate State Orchestrator
    • Windows 更新Windows Update

未提供功能更新,但提供了其他更新Feature updates are not being offered while other updates are

运行 Windows 10 版本 1709 到 Windows 10 版本 1803 且配置为从 Windows 更新(包括适用于企业的 Windows 更新)进行更新的设备能够安装服务更新和定义更新,但从未收到功能更新。Devices running Windows 10, version 1709 through Windows 10, version 1803 that are configured to update from Windows Update (including Windows Update for Business) are able to install servicing and definition updates but are never offered feature updates.

检查 WindowsUpdate.log 会显示以下错误:Checking the WindowsUpdate.log reveals the following error:

YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           * START * Finding updates CallerId = Update;taskhostw  Id = 25
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Online = Yes; Interactive = No; AllowCachedResults = No; Ignore download priority = No
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           ServiceID = {855E8A7C-ECB4-4CA3-B045-1DFA50104289} Third party service
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Search Scope = {Current User}
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Caller SID for Applicability: S-1-12-1-2933642503-1247987907-1399130510-4207851353
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            Got 855E8A7C-ECB4-4CA3-B045-1DFA50104289 redir Client/Server URL: https://fe3.delivery.mp.microsoft.com/ClientWebService/client.asmx""
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            Token Requested with 0 category IDs.
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            GetUserTickets: No user tickets found. Returning WU_E_NO_USERTOKEN.
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method failed [AuthTicketHelper::GetDeviceTickets:570]
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] GetDeviceTickets
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method failed [AuthTicketHelper::AddTickets:1092]
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Method failed [CUpdateEndpointProvider::GenerateSecurityTokenWithAuthTickets:1587]
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] GetAgentTokenFromServer
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] GetAgentToken
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] EP:Call to GetEndpointToken
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Misc            *FAILED* [80070426] Failed to obtain service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 plugin Client/Server auth token of type 0x00000001
YYYY/MM/DD HH:mm:ss:SSS PID  TID  ProtocolTalker  *FAILED* [80070426] Method failed [CAgentProtocolTalkerContext::DetermineServiceEndpoint:377]
YYYY/MM/DD HH:mm:ss:SSS PID  TID  ProtocolTalker  *FAILED* [80070426] Initialization failed for Protocol Talker Context
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           Exit code = 0x80070426
YYYY/MM/DD HH:mm:ss:SSS PID  TID  Agent           * END * Finding updates CallerId = Update;taskhostw  Id = 25

0x80070426 错误代码转换为:The 0x80070426 error code translates to:

ERROR_SERVICE_NOT_ACTIVE - # The service has not been started.

Microsoft 帐户登录助手(MSA 或 wlidsvc)是相关服务。Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. DCAT 外部测试服务(ServiceId:855E8A7C-ECB4-4CA3-B045-1DFA50104289)依赖 MSA 获取设备的全局设备 ID。The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on MSA to get the global device ID for the device. 如果没有运行 MSA 服务,客户端就不会生成和发送全局设备 ID,并且功能更新搜索永远不会成功完成。Without the MSA service running, the global device ID won't be generated and sent by the client and the search for feature updates never completes successfully.

若要解决此问题,请将 MSA 服务重置为默认的“手动”StartType。To resolve this issue, reset the MSA service to the default StartType of "manual."

Windows 更新使用 WinHttp 与部分范围请求 (RFC 7233) 从 Windows 更新服务器或本地 WSUS 服务器下载更新和应用程序。Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. 因此,网络上的代理服务器必须支持 HTTP RANGE 请求。Therefore proxy servers on the network must support HTTP RANGE requests. 如果代理在 Internet Explorer(用户级别)中进行配置,而不是在 WinHTTP(系统级别)中进行,与 Windows 更新的连接就会失败。If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.

若要解决此问题,请通过以下 netsh 命令在 WinHTTP 中配置代理:To fix this issue, configure a proxy in WinHTTP by using the following netsh command:

netsh winhttp set proxy ProxyServerName:PortNumber 

备注

还可以使用以下命令从 Internet Explorer 导入代理设置:netsh winhttp import proxy source=ieYou can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie

如果通过代理服务器进行下载失败,并出现 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH 错误,或者在下载更新的过程中发现 CPU 使用率很高,请检查代理配置以允许 HTTP RANGE 请求运行。If downloads through a proxy server fail with a 0x80d05001 DO_E_HTTP_BLOCKSIZE_MISMATCH error, or if you notice high CPU usage while updates are downloading, check the proxy configuration to permit HTTP RANGE requests to run.

可以选择应用规则来允许对以下 URL 的 HTTP RANGE 请求:You might choose to apply a rule to permit HTTP RANGE requests for the following URLs:

*.download.windowsupdate.com
*.dl.delivery.mp.microsoft.com *.delivery.mp.microsoft.com

如果无法允许 RANGE 请求,下载的内容将多于更新中所需的内容(因为增量修补将不起作用)。If you can't allow RANGE requests, you'll be downloading more content than needed in updates (as delta patching will not work).

该更新不适用于你的计算机The update is not applicable to your computer

下表介绍了导致此错误的最常见原因:The most common reasons for this error are described in the following table:

原因Cause 说明Explanation 解决方案Resolution
更新已被取代Update is superseded 随着组件的更新得以发布,更新的组件将取代已在系统中的旧组件。As updates for a component are released, the updated component will supersede an older component that is already on the system. 发生这种情况时,之前的更新就标记为“已被取代”。When this occurs, the previous update is marked as superseded. 如果尝试安装的更新在系统中已有较新版本的有效负载,则可能会收到这条错误消息。If the update that you're trying to install already has a newer version of the payload on your system, you might receive this error message. 检查要安装的程序包是否包含较新版本的二进制文件。Check that the package that you are installing contains newer versions of the binaries. 或者,检查该程序包是否已由另一个新程序包取代。Or, check that the package is superseded by another new package.
更新已安装Update is already installed 例如,如果以前安装了尝试安装的更新(例如由另一个执行同一有效负载的更新安装),则可能会遇到这条错误消息。If the update that you're trying to install was previously installed, for example, by another update that carried the same payload, you may encounter this error message. 验证以前有没有安装你尝试安装的程序包。Verify that the package that you are trying to install was not previously installed.
体系结构更新错误Wrong update for architecture 更新由 CPU 体系结构发布。Updates are published by CPU architecture. 如果尝试安装的更新与 CPU 的体系结构不匹配,则可能会遇到此错误消息。If the update that you're trying to install does not match the architecture for your CPU, you may encounter this error message. 验证你尝试安装的程序包是否与使用的 Windows 版本匹配。Verify that the package that you're trying to install matches the Windows version that you are using. 可以在每个更新的文章的“适用于”部分中找到 Windows 版本信息。The Windows version information can be found in the "Applies To" section of the article for each update. 例如,基于 Windows Server 2012 R2 的计算机上不能安装仅适用于 Windows Server 2012 的更新。For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers.
此外,请验证你尝试安装的程序包是否与使用的 Windows 版本的处理器体系结构相匹配。Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. 例如,基于 x64 的 Windows 安装上无法安装基于 x86 的更新。For example, an x86-based update cannot be installed on x64-based installations of Windows.
缺少必备更新Missing prerequisite update 某些更新需要先进行必备更新,然后才能应用于系统。Some updates require a prerequisite update before they can be applied to a system. 如果缺少必备更新,则可能会遇到此错误消息。If you are missing a prerequisite update, you may encounter this error message. 例如,必须先在 Windows 8.1 和 Windows Server 2012 R2 计算机上安装 KB 2919355,然后才能安装 2014 年 4 月之后发布的许多更新。For example, KB 2919355 must be installed on Windows 8.1 and Windows Server 2012 R2 computers before many of the updates that were released after April 2014 can be installed. 请在 Microsoft 知识库 (KB) 中查看该程序包的相关文章,确保已安装必备更新。Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. 例如,如果在 Windows 8.1 或 Windows Server 2012 R2 中遇到该错误消息,则可能必须安装 2014 年 4 月更新 2919355 作为必备更新,并安装一个或多个必备服务更新(KB 2919442 和 KB 3173424)。For example, if you encounter the error message on Windows 8.1 or Windows Server 2012 R2, you may have to install the April 2014 update 2919355 as a prerequisite and one or more pre-requisite servicing updates (KB 2919442 and KB 3173424).
若要确定是否安装了这些必备更新,请运行以下 PowerShell 命令:To determine if these prerequisite updates are installed, run the following PowerShell command:
get-hotfix KB3173424,KB2919355, KB2919442..
如果安装了更新,该命令将在输出的 InstalledOn 部分返回安装日期。If the updates are installed, the command will return the installed date in the InstalledOn section of the output.

可能在 Windows 更新日志中看到的错误:Error that you might see in Windows Update logs:

DownloadManager    Error 0x800706d9 occurred while downloading update; notifying dependent calls. 

Or

[DownloadManager] BITS job {A4AC06DD-D6E6-4420-8720-7407734FDAF2} hit a transient error, updateId = {D053C08A-6250-4C43-A111-56C5198FE142}.200 <NULL>, error = 0x800706D9 

Or

DownloadManager [0]12F4.1FE8::09/29/2017-13:45:08.530 [agent]DO job {C6E2F6DC-5B78-4608-B6F1-0678C23614BD} hit a transient error, updateId = 5537BD35-BB74-40B2-A8C3-B696D3C97CBA.201 <NULL>, error = 0x80D0000A 

转到 Services.msc,并确保 Windows 防火墙服务已启用。Go to Services.msc and ensure that Windows Firewall Service is enabled. Microsoft 不支持停止与高级安全 Windows 防火墙关联的服务。Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. 有关详细信息,请参阅我需要禁用 Windows 防火墙For more information, see I need to disable Windows Firewall.

因配置冲突策略而引发的问题Issues arising from configuration of conflicting policies

Windows 更新提供了大量配置策略,用于控制托管环境中 Windows 更新服务的行为。Windows Update provides a wide range configuration policy to control the behavior of the Windows Update service in a managed environment. 虽然这些策略让你可以精细地配置设置,但错误配置或设置冲突策略可能会导致意外行为。While these policies let you configure the settings at a granular level, misconfiguration or setting conflicting policies may lead to unexpected behaviors.

有关详细信息,请参阅如何使用组策略或注册表设置配置自动更新For more information, see How to configure automatic updates by using Group Policy or registry settings for more information.

设备无法访问更新文件Device cannot access update files

确保设备可以通过防火墙访问必要的 Windows 更新终结点。Ensure that devices can reach necessary Windows Update endpoints through the firewall. 例如,对于 Windows 10 版本 2004,以下协议必须能够访问各自这些终结点:For example, for Windows 10, version 2004, the following protocols must be able to reach these respective endpoints:

协议Protocol 终结点 URLEndpoint URL
TLS 1.2TLS 1.2 *.prod.do.dsp.mp.microsoft.com
HTTPHTTP emdl.ws.microsoft.com
HTTPHTTP *.dl.delivery.mp.microsoft.com
HTTPHTTP *.windowsupdate.com
HTTPSHTTPS *.delivery.mp.microsoft.com
TLS 1.2TLS 1.2 *.update.microsoft.com
TLS 1.2TLS 1.2 tsfe.trafficshaping.dsp.mp.microsoft.com

备注

请务必不要对指定 HTTP 的终结点使用 HTTPS,反之亦然。Be sure not to use HTTPS for those endpoints that specify HTTP, and vice versa. 连接将失败。The connection will fail.

特定终结点在各种 Windows 10 版本中可能有所不同。The specific endpoints can vary between Windows 10 versions. 例如,请参阅 Windows 10 2004 企业版连接终结点See, for example, Windows 10 2004 Enterprise connection endpoints. 旁边的目录提供了其他 Windows 10 版本的类似文章。Similar articles for other Windows 10 versions are available in the table of contents nearby.

更新不会从 Intranet 终结点(WSUS 或 Configuration Manager)下载Updates aren't downloading from the intranet endpoint (WSUS or Configuration Manager)

Windows 10 设备可以接收来自各种源的更新,包括联机 Windows 更新、Windows Server Update Services 服务器和其他源。Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. 若要确定设备上当前使用的 Windows 更新源,请按照以下步骤操作:To determine the source of Windows Updates currently being used on a device, follow these steps:

  1. 以管理员身份启动 Windows PowerShell。Start Windows PowerShell as an administrator.
  2. 运行 $MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager"。Run $MUSM = New-Object -ComObject "Microsoft.Update.ServiceManager".
  3. 运行 $MUSM.Services。Run $MUSM.Services.

检查 Name 和 OffersWindowsUPdates 参数的输出,你可以根据下表进行解读。Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.

输出Output 含义Meaning
- Name: Microsoft Update- Name: Microsoft Update
-OffersWindowsUpdates: True-OffersWindowsUpdates: True
- 更新源是 Microsoft 更新,这意味着还可以提供操作系统之外的其他 Microsoft 产品的更新。- The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.
- 指示客户端配置为接收所有 Microsoft 产品(Office 等)的更新- Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.)
- Name: DCat Flighting Prod- Name: DCat Flighting Prod
- OffersWindowsUpdates: True- OffersWindowsUpdates: True
- 从 Windows 10 1709 开始,功能更新始终通过 DCAT 服务提供。- Starting with Windows 10 1709, feature updates are always delivered through the DCAT service.
- 指示客户端配置为从 Windows 更新接收功能更新。- Indicates that the client is configured to receive feature updates from Windows Update.
- Name: Windows Store (DCat Prod)- Name: Windows Store (DCat Prod)
- OffersWindowsUpdates: False- OffersWindowsUpdates: False
- 更新源是应用商店应用的预览体验成员更新。-The update source is Insider Updates for Store Apps.
- 指示客户端不会接收或未配置为接收这些更新。- Indicates that the client will not receive or is not configured to receive these updates.
- Name: Windows Server Update Service- Name: Windows Server Update Service
- OffersWindowsUpdates: True- OffersWindowsUpdates: True
- 源是 Windows Server Updates Services 服务器。- The source is a Windows Server Updates Services server.
- 客户端配置为从 WSUS 接收更新。- The client is configured to receive updates from WSUS.
- Name: Windows Update- Name: Windows Update
- OffersWindowsUpdates: True- OffersWindowsUpdates: True
- 源是 Windows 更新。- The source is Windows Update.
- 客户端配置为从联机 Windows 更新接收更新。- The client is configured to receive updates from Windows Update Online.

环境中的设置不正确You have a bad setup in the environment

在本例中,根据通过注册表设置的组策略,系统配置为使用 WSUS 下载更新(注意第二行):In this example, per the Group Policy set through registry, the system is configured to use WSUS to download updates (note the second line):

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU] 
"UseWUServer"=dword:00000001

在 Windows 更新日志中:From Windows Update logs:

2018-08-06 09:33:31:085  480 1118 Agent ** START **  Agent: Finding updates [CallerId = OperationalInsight  Id = 49] 
2018-08-06 09:33:31:085  480 1118 Agent ********* 
2018-08-06 09:33:31:085  480 1118 Agent   * Include potentially superseded updates 
2018-08-06 09:33:31:085  480 1118 Agent   * Online = No; Ignore download priority = No 
2018-08-06 09:33:31:085  480 1118 Agent   * Criteria = "IsHidden = 0 AND DeploymentAction=*" 
2018-08-06 09:33:31:085  480 1118 Agent   * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service 
2018-08-06 09:33:31:085  480 1118 Agent   * Search Scope = {Machine} 
2018-08-06 09:33:32:554  480 1118 Agent   * Found 83 updates and 83 categories in search; evaluated appl. rules of 517 out of 1473 deployed entities 
2018-08-06 09:33:32:554  480 1118 Agent ********* 
2018-08-06 09:33:32:554  480 1118 Agent **  END  **  Agent: Finding updates [CallerId = OperationalInsight  Id = 49] 

在上述日志代码片段中,我们看到 Criteria = "IsHidden = 0 AND DeploymentAction=*"In the above log snippet, we see that the Criteria = "IsHidden = 0 AND DeploymentAction=*". “*”表示服务器未指定任何内容。"*" means there is nothing specified from the server. 这样一来,扫描行为发生,但没有下载或安装到代理的任何指令。So, the scan happens but there is no direction to download or install to the agent. 因此,只会扫描更新并提供结果。So it just scans the update and provides the results.

如以下日志所示,自动更新将运行扫描,并且发现未对其批准任何更新。As shown in the following logs, automatic update runs the scan and finds no update approved for it. 因此自动更新会报告没有要安装或下载的更新。So it reports there are no updates to install or download. 这是因为配置不正确。This is due to an incorrect configuration. 根据策略,WSUS 端应批准 Windows 更新的更新,以便其获取更新并在指定时间安装更新。The WSUS side should approve the updates for Windows Update so that it fetches the updates and installs them at the specified time according to the policy. 由于此场景不包括 Configuration Manager,因此无法安装未经批准的更新。Since this scenario doesn't include Configuration Manager, there's no way to install unapproved updates. 你期望操作见解代理执行扫描并自动触发下载和安装,但对于此配置,并不会发生这种情况。You're expecting the operational insight agent to do the scan and automatically trigger the download and installation but that won’t happen with this configuration.

2018-08-06 10:58:45:992  480 5d8 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 57] 
2018-08-06 10:58:45:992  480 5d8 Agent ********* 
2018-08-06 10:58:45:992  480 5d8 Agent   * Online = Yes; Ignore download priority = No 
2018-08-06 10:58:45:992  480 5d8 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1" 
   
2018-08-06 10:58:46:617  480 5d8 PT   + SyncUpdates round trips: 2 
2018-08-06 10:58:47:383  480 5d8 Agent   * Found 0 updates and 83 categories in search; evaluated appl. rules of 617 out of 1473 deployed entities 
2018-08-06 10:58:47:383  480 5d8 Agent Reporting status event with 0 installable, 83 installed,  0 installed pending, 0 failed and 0 downloaded updates 
2018-08-06 10:58:47:383  480 5d8 Agent ********* 
2018-08-06 10:58:47:383  480 5d8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates  Id = 57] 

Windows 更新在 Windows 10 上的高带宽使用率High bandwidth usage on Windows 10 by Windows Update

用户可能会看到,Windows 10 占用了系统环境下不同办事处的所有带宽。Users might see that Windows 10 is consuming all the bandwidth in the different offices under the system context. 此行为是设计使然。This behavior is by design. 可能消耗带宽的组件不局限于 Windows 更新组件的范围。Components that might consume bandwidth expand beyond Windows Update components.

以下组策略可帮助减少这种情况:The following group policies can help mitigate this situation:

连接到 Internet 的其他组件:Other components that connect to the internet: