Исправить ошибку 80072EFE обновления в Windows 10/7

Основной причиной ошибки 80072EFE в центре обновления Windows является разрыв соединения между вашим компьютером и серверами microsoft. Это означает, что ошибка может быть из-за плохого интернета с вашей стороны или сервер microsoft временно не работают. Если ваше интернет-соединение прерывается, то может быть так, что вирус-руткит может быть виновником этой проблемы. Также, сторонние антивирусы и брандмауэры могут блокировать подключение к серверам по обновлению и тем самым вызывать ошибку.

Ошибка 80072EFE может появляться на Windows 7 и Windows 10 и дополняться следующим сообщением «Соединение с сервером было разорвано» и иметь код:

• ERROR_INTERNET_CONNECTION_ABORTED
• WININET_E_CONNECTION_ABORTED
• ERROR_WINHTTP_CONNECTION_ABORTED

Как исправить ошибку 80072EFE в Windows 10/7

1. Подождите минут 7. Дело может быть в самих серверах Microsoft.
2. Перезагрузите роутер (модем) и ПК.
3. Отключите сторонний антивирус и брандмауэр и проверьте обновления.
4. Воспользуйтесь антивирусным сканером .
5. Если у вас есть программа или расширение в браузере VPN/Прокси, то отключите или удалите на время.
6. Местные провайдеры дают свой нестабильный DNS. Измените DNS-адрес и сбросьте Winsock, TCP/IP, DNS .

Вы должны понимать, что ошибка 80072EFE по большей части связана с прерыванием интернет соединения, когда ваш компьютер не может стабильно подключаться к серверам Microsoft. По этому, уделите внимание сторонним программ, которые работают с сетевым соединением. Если выше, быстрые пункты не помогли вам решить проблему, то приступим к более радикальным способам.

1. Устранение неполадок

Запустите устранение неполадок сетевого адаптера и центра обновления Windows 10. Откройте «Параметры» > «Обновление и безопасность» > «Устранение неполадок» > справа «Дополнительные средства устранения неполадок«. В списке запустите следующую диагностику:

1. Подключение к Интернету
2. Сетевой адаптер
3. Центр обновления Windows

2. Исправление для Windows 7, Windows 8 и Server

Если вы используете старые операционные системы как Windows 7, Windows 8.1 или серверные Windows Server 2012, Windows Server 2008 R2 SP1, то нужно вручную обновить агент обновления Windows, скачав с официального сайта Microsoft.

Для Windows 8 и Windows Server 2012:

• 32-разрядные версии Windows 8 ( KB2937636 )
• 64-разрядные версии Windows 8 ( KB2937636 )
• 64-разрядные версии Windows Server 2012 ( KB2937636 )

Для Windows 7 (SP1) и Windows Server 2008 R2 (SP1)

• 32-разрядные версии Windows 7 (SP1)
• 64-разрядные версии Windows 7 (SP1)
• 32-разрядные версии Windows Server 2008 R2 (SP1)
• 64-разрядные версии Windows Server 2008 R2 (SP1)
• Windows Server 2008 R2 (SP1) с архитектурой Itanium

3. Удаление папки Catroot2

В системной папке Catroot2 находятся подписи обновлений Windows. Любое повреждение подписи может вызвать ошибку 80072EFE в центре обновлений Windows. По этой причине нужно удалить эту папку. Чтобы удалить папку Catroot2 нужно сначала отключить службу, которая работает в этой папке. Приступим.

Шаг 1. Нажмите Win+R и введите services.msc, чтобы открыть службы. Далее найдите службу «Службы криптографии» и нажмите по ней два раза. В новом коне свойств нажмите на «Остановить«. Не закрывает это окно и перейдите ниже к шагу 2.

Шаг 2. Откройте проводник (Этот компьютер) и перейдите по пути C:\Windows\System32\. Найдите папку Catroot2 и удалите её.

Шаг 3. Мы остановили службу в шаге 1, чтобы была возможность удалить папку. Теперь нужно эту службу включить обратно. Приступите к шаг 1 и включите службу криптографии. Далее проверьте обновления.

4. Сброс папки SoftwareDistribution

Мы создадим новую папку SoftwareDistribution, которая отвечает за обновления в Windows 10. Только мы пойдем другим и более быстрым путем, чем выше с папкой Catroot2. Запустите командную строку от имени администратора и введите команды по очереди:

Fix Windows Update errors

What does this guided walk-through do?

This guided walk-through provides steps to fix problems with Windows Updates for Windows 8.1 and 7, such as taking a long time to scan, or error codes while installing updates.

For help with Windows Update issues in Windows 10, see Troubleshoot problems updating Windows 10 instead.

A common cause of errors is inadequate drive space. If you need help freeing up drive space, see Tips to free up drive space on your PC.

Common error codes

The steps in this guided walk-through should help with all Windows Update errors and other issues— you don’t need to search for the specific error to solve it. As an example, here are some commonly seen error codes: 0x0xc1900223223; 0x80240034; 0x8007000E, 0x80242006​, 0x80244018​, 0x80D02002​, 0x80246017​, 0x80240438​, 0x80070070​, 0x8007000D​, 0x80246008​, 0x80096004​, 0x80070020.
The steps provided here should help fix any errors that come up during the Windows Update process.

How does it work?

We’ll begin by asking you questions about the Windows version you’re using and the issue you’re experiencing. Next, we’ll take you through a series of troubleshooting steps that are specific to your situation. At the end of each step, you’ll be asked “Did this resolve the issue?” If it’s resolved, select Yes, and you’re done! If it isn’t resolved, select No and continue with the guided walk-through.

Resolve Windows activation error codes

This article is intended for technical support agents and IT professionals. If you’re looking for more information about Windows activation error messages, see Get help with Windows activation errors.

This article provides troubleshooting information to help you respond to error messages that you may receive when you try to use a Multiple Activation Key (MAK) or the Key Management Service (KMS) to perform Volume Activation on one or more Windows-based computers. Look for the error code in the following table, and then select the link to see more information about that error code and how to resolve it.

For more information about volume activation, see Plan for volume activation.

For more information about volume activation for current and recent versions of Windows, see Volume Activation [client].

For more information about volume activation for older versions of Windows, seeВ KB 929712,В Volume Activation information for Windows Vista, Windows Server 2008, Windows Server 2008 R2 and Windows 7.

Diagnostic tool

This tool is intended to help fix Windows activation problems on computers that run Enterprise, Professional, or Server edition of Windows.

Microsoft Support and Recovery Assistant (SaRA) simplifies Windows KMS Activation troubleshooting. Download the diagnostic tool from here.

This tool will try to activate Windows. If it returns an activation error code, the tool will display targeted solutions for known error codes.

The following error codes are supported: 0xC004F038, 0xC004F039, 0xC004F041, 0xC004F074, 0xC004C008, 0x8007007b, 0xC004C003, 0x8007232B.

Summary of error codes

Error code	Error message	ActivationВ type
0x8004FE21	This computer is not running genuine Windows.	MAK KMS client
0x80070005	Access denied. The requested action requires elevated privileges.	MAK KMS client KMS host
0x8007007b	0x8007007b DNS name does not exist.	KMS client
0x80070490	The product key you entered didn’t work. Check the product key and try again, or enter a different one.	MAK
0x800706BA	The RPC server is unavailable.	KMS client
0x8007232A	DNS server failure.	KMS host
0x8007232B	DNS name does not exist.	KMS client
0x8007251D	No records found for DNS query.	KMS client
0x80092328	DNS name does not exist.	KMS client
0xC004B100	The activation server determined that the computer could not be activated.	MAK
0xC004C001	The activation server determined the specified product key is invalid	MAK
0xC004C003	The activation server determined the specified product key is blocked	MAK
0xC004C008	The activation server determined that the specified product key could not be used.	KMS
0xC004C020	The activation server reported that the Multiple Activation Key has exceeded its limit.	MAK
0xC004C021	The activation server reported that the Multiple Activation Key extension limit has been exceeded.	MAK
0xC004F009	The Software Protection Service reported that the grace period expired.	MAK
0xC004F00F	The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance.	MAK KMS client KMS host
0xC004F014	The Software Protection Service reported that the product key is not available	MAK KMS client
0xC004F02C	The Software Protection Service reported that the format for the offline activation data is incorrect.	MAK KMS client
0xC004F035	The Software Protection Service reported that the computer could not be activated with a Volume license product key.	KMS client KMS host
0xC004F038	The Software Protection Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.	KMS client
0xC004F039	The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled.	KMS client
0xC004F041	The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated.	KMS client
0xC004F042	The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used.	KMS client
0xC004F050	The Software Protection Service reported that the product key is invalid.	MAK KMS KMS client
0xC004F051	The Software Protection Service reported that the product key is blocked.	MAK KMS
0xC004F064	The Software Protection Service reported that the non-genuine grace period expired.	MAK
0xC004F065	The Software Protection Service reported that the application is running within the valid non-genuine period.	MAK KMS client
0xC004F06C	The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid.	KMS client
0xC004F074	The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.	KMS client

Causes and resolutions

0x8004FE21 This computer is not running genuine Windows

Possible cause

This issue can occur for several reasons. The most likely reason is that language packs (MUI) have been installed on computers that are running Windows editions that are not licensed for additional language packs.

This issue is not necessarily an indication of tampering. Some applications can install multi-lingual support even when that edition of Windows is not licensed for those language packs.)

This issue may also occur if Windows has been modified by malware to allow additional features to be installed. This issue may also occur if certain system files are corrupted.

Resolution

To resolve this issue, you must reinstall the operating system.

0x80070005 Access denied

The full text of this error message resembles the following:

Access denied. The requested action requires elevated privileges.

Possible cause

User Account Control (UAC) prohibits activation processes from running in a non-elevated Command Prompt window.

Resolution

Run slmgr.vbs from an elevated command prompt. To do this, on the Start menu, right-click cmd.exe, and then select Run as administrator.

0x8007007b DNS name does not exist

Possible cause

This issue may occur if the KMS client cannot find the KMS SRV resource records in DNS.

Resolution

For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.

0x80070490 The product key you entered didn’t work

The full text of this error resembles the following:

The product key that you entered didn’t work. Check the product key and try again, or enter a different one.

Possible cause

This issue occurs because the MAK that was entered was not valid, or because of a known issue in Windows Server 2019.

Resolution

To work around this issue and activate the computer, run slmgr -ipk at an elevated command prompt.

0x800706BA The RPC server is unavailable

Possible cause

Firewall settings are not configured on the KMS host, or DNS SRV records are stale.

Resolution

On the KMS host, make sure that a firewall exception is enabled for the Key Management Service (TCP port 1688).

Make sure that the DNS SRV records point to a valid KMS host.

Troubleshoot network connections.

For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.

0x8007232A DNS server failure

Possible cause

The system has network or DNS issues.

Resolution

Troubleshoot network and DNS.

0x8007232B DNS name does not exist

Possible cause

The KMS client cannot find KMS server resource records (SRV RRs) in DNS.

Resolution

Verify that a KMS host has been installed and DNS publishing is enabled (default). If DNS is unavailable, point the KMS client to the KMS host by using slmgr.vbs /skms .

If you do not have a KMS host, obtain and install an MAK. Then, activate the system.

For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.

0x8007251D No records found for DNS query

Possible cause

The KMS client cannot find KMS SRV records in DNS.

Resolution

Troubleshoot network connections and DNS. For more information about how to troubleshoot such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.

0x80092328 DNS name does not exist

Possible cause

This issue may occur if the KMS client cannot find the KMS SRV resource records in DNS.

Resolution

For more information about troubleshooting such DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.

0xC004B100 The activation server determined that the computer could not be activated

Possible cause

The MAK is not supported.

Resolution

To troubleshoot this issue, verify that the MAK that you are using is the MAK that was provided by Microsoft. To verify that the MAK is valid, contact the Microsoft Licensing Activation Centers.

0xC004C001 The activation server determined the specified product key is invalid

Possible cause

The MAK that you entered is not valid.

Resolution

Verify that the key is the MAK that was provided by Microsoft. For additional assistance, contact the Microsoft Licensing Activation Centers.

0xC004C003 The activation server determined the specified product key is blocked

Possible cause

The MAK is blocked on the activation server.

Resolution

To obtain a new MAK, contact the Microsoft Licensing Activation Centers. After you obtain the new MAK, try installing and activating Windows again.

0xC004C008 The activation server determined that the specified product key could not be used

Possible cause

The KMS key has exceeded its activation limit. A KMS host key can be activated up to 10 times on up to six different computers.

Resolution

If you require additional activations, contact the Microsoft Licensing Activation Centers.

0xC004C020 The activation server reported that the Multiple Activation Key has exceeded its limit

Possible cause

The MAK has exceeded its activation limit. By design, MAKs can be activated a limited number of times.

Resolution

If you require additional activations, contact the Microsoft Licensing Activation Centers.

0xC004C021 The activation server reported that the Multiple Activation Key extension limit has been exceeded

Possible cause

The MAK has exceeded its activation limit. By design, MAKs activate a limited number of times.

Resolution

If you need additional activations, contact the Microsoft Licensing Activation Centers.

0xC004F009 The Software Protection Service reported that the grace period expired

Possible cause

The grace period expired before the system was activated. Now, the system is in the Notifications state.

Resolution

0xC004F00F The Software Licensing Server reported that the hardware ID binding is beyond level of tolerance

Possible cause

The hardware has changed or the drivers were updated on the system.

Resolution

If you are using MAK activation, use either online or phone activation to reactivate the system during the OOT grace period.

If you are using KMS activation, restart Windows or run slmgr.vbs /ato.

0xC004F014 The Software Protection Service reported that the product key is not available

Possible cause

No product keys are installed on the system.

Resolution

If you are using MAK activation, install a MAK product key.

If you are using KMS activation, check the Pid.txt file (located on the installation media in the \sources folder) for a KMS Setup key. Install the key.

0xC004F02C The Software Protection Service reported that the format for the offline activation data is incorrect

Possible cause

The system has detected that the data entered during phone activation is not valid.

Resolution

Verify that the CID is entered correctly.

0xC004F035 Invalid Volume License Key

The full text of this error message resembles the following:

Error: Invalid Volume License Key. In order to activate, you need to change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source. ANY OTHER INSTALLATION OF THIS SOFTWARE IS IN VIOLATION OF YOUR AGREEMENT AND APPLICABLE COPYRIGHT LAW.

The error text is correct, but is ambiguous. This error indicates that the computer is missing a Windows marker in its BIOS that identifies it as an OEM system that is running a qualifying edition of Windows. This information is required for KMS client activation. The more specific meaning of this code is «Error: Invalid Volume License Key»

Possible cause

Windows 7 Volume editions are licensed only for upgrade. Microsoft does not support installing a Volume operating system on a computer that does not have a qualifying operating system installed.

Resolution

In order to activate, you need to do one of the following:

Change your product key to a valid Multiple Activation Key (MAK) or Retail key. You must have a qualifying operating system license AND a Volume license Windows 7 upgrade license, or a full license for Windows 7 from a retail source.

If you receive error 0x80072ee2 when you attempt to activate, use the phone activation method that follows instead.

0xC004F038 The count reported by your Key Management Service (KMS) is insufficient

The full text of this error message resembles the following:

The Software Protection Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator.

Possible cause

The count on the KMS host is not high enough. For Windows Server, the KMS count must be greater than or equal to 5. For Windows (client), the KMS count must be greater than or equal to 25.

Resolution

Before you can use KMS to activate Windows, you must have more computers in the KMS pool. To obtain the current count on the KMS host, run Slmgr.vbs /dli.

0xC004F039 The Key Management Service (KMS) is not enabled

The full text of this error message resembles the following:

The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) is not enabled.

Possible cause

KMS did not respond to the KMS request.

Resolution

Troubleshoot the network connection between the KMS host and the client. Make sure that TCP port 1688 (default) is not blocked by a firewall or is otherwise filtered.

0xC004F041 The Software Protection Service determined that the Key Management Server (KMS) is not activated

The full text of this error message resembles the following:

The Software Protection Service determined that the Key Management Server (KMS) is not activated. KMS needs to be activated.

Possible cause

The KMS host is not activated.

Resolution

Activate the KMS host by using either online or telephone activation.

0xC004F042 The Software Protection Service determined that the specified Key Management Service (KMS) cannot be used

Possible cause

This error occurs if the KMS client contacted a KMS host that could not activate the client software. This can be common in mixed environments that contain application-specific and operating system-specific KMS hosts, for example.

Resolution

Make sure that if you use specific KMS hosts to activate specific applications or operating systems, the KMS clients connect to the correct hosts.

0xC004F050 The Software Protection Service reported that the product key is invalid

Possible cause

This can be caused by a typo in the KMS key or by typing in a Beta key on a Released version of the operating system.

Resolution

Install the appropriate KMS key on the corresponding version of Windows. Check the spelling. If the key is being copied and pasted, make sure that em-dashes were not substituted for the hyphens in the key.

0xC004F051 The Software Protection Service reported that the product key is blocked

Possible cause

The activation server determined that Microsoft has blocked the product key.

Resolution

Obtain a new MAK or KMS key, install it on the system, and activate.

0xC004F064 The Software Protection Service reported that the non-genuine grace period expired

Possible cause

Windows Activation Tools (WAT) has determined that the system is not genuine.

Resolution

0xC004F065 The Software Protection Service reported that the application is running within the valid non-genuine period

Possible cause

Windows Activation Tools has determined that the system is not genuine. The system will continue to run during the Non-Genuine grace period.

Resolution

Obtain and install a genuine product key, and activate the system during the grace period. Otherwise, the system will go into the Notifications state at the end of the grace period.

0xC004F06C The request timestamp is invalid

The full text of this error message resembles the following:

The Software Protection Service reported that the computer could not be activated. The Key Management Service (KMS) determined that the request timestamp is invalid.

Possible cause

The system time on the client computer is too different from the time on the KMS host. Time sync is important to system and network security for a variety of reasons.

Resolution

Fix this issue by changing the system time on the client to sync with the KMS host. We recommend that you use a Network Time Protocol (NTP) time source or Active Directory Domain Services for time synchronization. This issue uses UTP time and does not depend on Time Zone selection.

0xC004F074 No Key Management Service (KMS) could be contacted

The full text of this error message resembles the following:

The Software Protection Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.

Possible cause

All of the KMS host systems returned an error.

Resolution

In the Application Event Log, identify each event that has Event ID 12288 and is associated with the activation attempt. Troubleshoot the errors from these events.

For more information about troubleshooting DNS-related issues, see Common troubleshooting procedures for KMS and DNS issues.