Access to windows update blocked

Windows Update troubleshooting

If you run into problems when using Windows Update, start with the following steps:

Run the built-in Windows Update troubleshooter to fix common issues. Navigate to Settings > Update & Security > Troubleshoot > Windows Update.

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.

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:

Advanced users can also refer to the log generated by Windows Update for further investigation.

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

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?

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:

Close the Settings app and reopen it.

Start Services.msc and check if the following services are running:

  • Update State Orchestrator
  • Windows Update

Feature updates are not being offered while other updates are

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.

Checking the WindowsUpdate.log reveals the following error:

The 0x80070426 error code translates to:

Microsoft Account Sign In Assistant (MSA or wlidsvc) is the service in question. The DCAT Flighting service (ServiceId: 855E8A7C-ECB4-4CA3-B045-1DFA50104289) relies on MSA to get the global device ID for the device. 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.

To resolve this issue, reset the MSA service to the default StartType of «manual.»

Issues related to HTTP/Proxy

Windows Update uses WinHttp with Partial Range requests (RFC 7233) to download updates and applications from Windows Update servers or on-premises WSUS servers. Therefore proxy servers on the network must support HTTP RANGE requests. If a proxy was configured in Internet Explorer (User level) but not in WinHTTP (System level), connections to Windows Update will fail.

To fix this issue, configure a proxy in WinHTTP by using the following netsh command:

You can also import the proxy settings from Internet Explorer by using the following command: netsh winhttp import proxy source=ie

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.

Читайте также:  Windows 10 iso redstone

You might choose to apply a rule to permit HTTP RANGE requests for the following URLs:

*.dl.delivery.mp.microsoft.com *.delivery.mp.microsoft.com

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 Updates are published by CPU architecture. If the update that you’re trying to install does not match the architecture for your CPU, you may encounter this error message. Verify that the package that you’re trying to install matches the Windows version that you are using. The Windows version information can be found in the «Applies To» section of the article for each update. For example, Windows Server 2012-only updates cannot be installed on Windows Server 2012 R2-based computers.
Also, verify that the package that you are installing matches the processor architecture of the Windows version that you are using. 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. 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. Check the related articles about the package in the Microsoft Knowledge Base (KB) to make sure that you have the prerequisite updates installed. 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).
To determine if these prerequisite updates are installed, run the following PowerShell command:
get-hotfix KB3173424,KB2919355, KB2919442 .
If the updates are installed, the command will return the installed date in the InstalledOn section of the output.

Issues related to firewall configuration

Error that you might see in Windows Update logs:

Go to Services.msc and ensure that Windows Firewall Service is enabled. Stopping the service associated with Windows Firewall with Advanced Security is not supported by Microsoft. For more information, see I need to disable Windows Firewall.

Issues arising from configuration of conflicting policies

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.

Device cannot access update files

Ensure that devices can reach necessary Windows Update endpoints through the firewall. For example, for Windows 10, version 2004, the following protocols must be able to reach these respective endpoints:

Protocol Endpoint URL
TLS 1.2 *.prod.do.dsp.mp.microsoft.com
HTTP emdl.ws.microsoft.com
HTTP *.dl.delivery.mp.microsoft.com
HTTP *.windowsupdate.com
HTTPS *.delivery.mp.microsoft.com
TLS 1.2 *.update.microsoft.com
TLS 1.2 tsfe.trafficshaping.dsp.mp.microsoft.com

Be sure not to use HTTPS for those endpoints that specify HTTP, and vice versa. The connection will fail.

The specific endpoints can vary between Windows 10 versions. See, for example, Windows 10 2004 Enterprise connection endpoints. Similar articles for other Windows 10 versions are available in the table of contents nearby.

Updates aren’t downloading from the intranet endpoint (WSUS or Configuration Manager)

Windows 10 devices can receive updates from a variety of sources, including Windows Update online, a Windows Server Update Services server, and others. To determine the source of Windows Updates currently being used on a device, follow these steps:

  1. Start Windows PowerShell as an administrator.
  2. Run $MUSM = New-Object -ComObject «Microsoft.Update.ServiceManager».
  3. Run $MUSM.Services.

Check the output for the Name and OffersWindowsUPdates parameters, which you can interpret according to this table.

Output Meaning
— Name: Microsoft Update
-OffersWindowsUpdates: True
— The update source is Microsoft Update, which means that updates for other Microsoft products besides the operating system could also be delivered.
— Indicates that the client is configured to receive updates for all Microsoft Products (Office, etc.)
— Name: DCat Flighting Prod
— OffersWindowsUpdates: True
— Starting with Windows 10 1709, feature updates are always delivered through the DCAT service.
— Indicates that the client is configured to receive feature updates from Windows Update.
— Name: Windows Store (DCat Prod)
— 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
— OffersWindowsUpdates: True
— The source is a Windows Server Updates Services server.
— The client is configured to receive updates from WSUS.
— Name: Windows Update
— OffersWindowsUpdates: True
— The source is Windows Update.
— The client is configured to receive updates from Windows Update Online.

You have a bad setup in the environment

In this example, per the Group Policy set through registry, the system is configured to use WSUS to download updates (note the second line):

From Windows Update logs:

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

High bandwidth usage on Windows 10 by Windows Update

Users might see that Windows 10 is consuming all the bandwidth in the different offices under the system context. This behavior is by design. Components that might consume bandwidth expand beyond Windows Update components.

The following group policies can help mitigate this situation:

Other components that connect to the internet:

Как снять блокировку доставки новых версий Windows 10

Новые обновления функций для Windows 10, такие как May 2020 Update и October 2020 Update, нередко вызывают различные крупные и мелкие проблемы в системе. Обычно в таких ситуациях Microsoft принудительно блокирует обновления для затронутых систем и конфигураций оборудования, пока занимается исследованием ошибок и созданием исправлений.

Хотя данные меры действительно имеют смысл, многие люди предпочитают сами контролировать установку обновлений на своих компьютерах. Если вы хотите обойти блокировку установки обновления, то Microsoft представила новую групповую политику «Отключение защиты для обновления компонентов» (DisableWUfBSafeguards).

Политика доступна в Windows 10, версия 1903 и выше при наличии накопительных обновлений, выпущенных в октябре 2020 – KB4579311 для Windows 10, версия 20H2 и 2004 и KB4577671 для Windows 10, версия 1909 и 1903.

Как принудительно устанавливать заблокированные «обновления функций» Windows 10

Редактор локальных групповых политик

Самый простой способ для установки заблокированных обновлений для Windows 10 заключается в использовании редактора групповой политики. Данный инструмент доступен только пользователям Windows 10 Pro и более старших редакций Windows 10.

Если вы используете Windows 10 Pro, убедитесь, что у вас установлены все последние обновления, поскольку необходимая групповая политика была добавлена совсем недавно.

  • Нажмите сочетание клавиш Windows + R , чтобы открыть окно команды «Выполнить».
  • Введите gpedit.msc и нажмите OK, чтобы открыть редактор локальных групповых политик.
  • Перейдите по следующему пути: Конфигурация компьютера > Административные шаблоны > Компоненты Windows > Центр обновления Windows > Центр обновления Windows для бизнеса
  • Найдите политику с названием Отключение защиты для обновления компонентов.
  • После включения этой политики вы сможете загружать обновления от Microsoft, даже если они заблокированы. Microsoft приводит следующее описание данной политики:

Включите этот параметр, если необходимо развернуть обновления компонентов на устройствах, избежав защитной блокировки. Защитные блокировки представляют собой известную проблему совместимости, приостанавливая развертывание обновлений на устройствах до устранения проблемы. Включение этой политики может позволить организации развертывать обновление компонентов на устройствах для тестирования или развертывать его без защитной блокировки.

Редактор реестра

Если вы используете Windows 10 Домашняя, то вы можете добиться аналогичного результата с помощью редактора системного реестра.

  • Нажмите сочетание клавиш Windows + R , чтобы открыть окно команды «Выполнить».
  • Введите regedit и нажмите OK, чтобы открыть редактор реестра.
  • Перейдите по следующему пути:

Если в списке отсутствует раздел WindowsUpdate, выполните следующие действия:

  • Кликните правой кнопкой мыши по разделу Windows и выберите Создать > Раздел.
  • Присвойте новому разделу имя WindowsUpdate нажмите клавишу ввода Enter .
  • Кликните правой кнопкой мыши по WindowsUpdate и выберите Создать > Параметр DWORD (32 бита) .
  • Назовите параметр DisableWUfBSafeguards
  • Установите значение 1.
  • Перезагрузите компьютер.

Windows PowerShell

Вы также можете использовать PowerShell для внесения изменений:

  • Нажмите сочетание клавиш Windows + X , чтобы открыть меню администратора.
  • Выберите Windows PowerShell (администратор) из списка.
  • Запустите следующую команду: