self protection failed error code 4 что это

Whatsminer M21S перезагружается

Aab.prav

Пляшущий с бубном

WhatsminerM21S стал часто перезагружаться и сыпать ошибками.
Error code: 560, reason: Slot0 loss balance
Help

09-04 08:03:20 20497,837,68|15865,835,68|19234,825,71|4980,4980|39,29%,184|1270,3377

09-04 08:03:50 Error code: 210, reason: Power error status: 0x0000->0x0001

power name 21 vender:1 hw: sw——— sn:————

09-04 08:03:40 power enable:1 errors:0 iout:243000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:3377 fan_speed:8970 temp0:454 temp1:465 temp2:377 status:0
09-04 08:03:41 power enable:1 errors:0 iout:243000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:3376 fan_speed:8940 temp0:453 temp1:463 temp2:379 status:0
09-04 08:03:42 power enable:1 errors:0 iout:244000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3388 fan_speed:8880 temp0:451 temp1:464 temp2:379 status:0
09-04 08:03:43 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3375 fan_speed:8970 temp0:453 temp1:462 temp2:384 status:0
09-04 08:03:44 power enable:1 errors:0 iout:243000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:3390 fan_speed:8880 temp0:456 temp1:464 temp2:384 status:0
09-04 08:03:45 power enable:1 errors:0 iout:243000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:3377 fan_speed:8940 temp0:454 temp1:464 temp2:381 status:0
09-04 08:03:46 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3375 fan_speed:8970 temp0:457 temp1:467 temp2:381 status:0
09-04 08:03:47 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3374 fan_speed:8970 temp0:453 temp1:464 temp2:384 status:0
09-04 08:03:48 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3375 fan_speed:8880 temp0:456 temp1:466 temp2:380 status:0
09-04 08:03:49 power enable:1 errors:1 iout:0 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:38 fan_speed:8940 temp0:455 temp1:467 temp2:382 status:0
09-04 08:03:50 power enable:1 errors:1 iout:0 vout:1 vout_set:1270 iin:-1 vin:-1 input_power:37 fan_speed:8850 temp0:452 temp1:466 temp2:383 status:20000
09-04 08:03:50 power enable:1 errors:1 iout:0 vout:1 vout_set:1270 iin:-1 vin:-1 input_power:37 fan_speed:8850 temp0:452 temp1:466 temp2:383 status:20000
09-04 08:03:51 power enable:1 errors:0 iout:0 vout:0 vout_set:1270 iin:-1 vin:-1 input_power:38 fan_speed:8940 temp0:452 temp1:464 temp2:383 status:20000
09-04 08:03:52 16898,837,68|19128,835,68|19611,825,71|4890,4890|39,30%,183|0,38
09-04 08:03:52 power enable:1 errors:0 iout:9000 vout:644 vout_set:1270 iin:-1 vin:-1 input_power:98 fan_speed:8940 temp0:454 temp1:466 temp2:380 status:0
09-04 08:03:53 power enable:1 errors:0 iout:9000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:160 fan_speed:8850 temp0:452 temp1:466 temp2:378 status:0
09-04 08:03:54 power enable:1 errors:0 iout:9000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:160 fan_speed:8880 temp0:453 temp1:464 temp2:381 status:0
09-04 08:03:55 power enable:1 errors:0 iout:9000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:160 fan_speed:8880 temp0:456 temp1:464 temp2:377 status:0
09-04 08:03:56 power enable:1 errors:0 iout:9000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:157 fan_speed:8940 temp0:452 temp1:466 temp2:380 status:0
09-04 08:03:57 power enable:1 errors:0 iout:9000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:157 fan_speed:8850 temp0:454 temp1:465 temp2:377 status:0
09-04 08:03:58 power enable:1 errors:0 iout:9000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:155 fan_speed:8940 temp0:453 temp1:464 temp2:380 status:0
09-04 08:03:59 power enable:1 errors:0 iout:9000 vout:1271 vout_set:1270 iin:-1 vin:-1 input_power:155 fan_speed:8880 temp0:453 temp1:467 temp2:379 status:0
09-04 08:04:24 1067,837,56|495,835,56|505,825,60|2070,2100|38,23%,183|1273,129
09-04 08:04:59 1067,837,53|26,835,53|26,825,56|690,780|41,21%,183|1273,125

09-04 08:05:19 Error code: 560, reason: Slot0 loss balance

09-04 08:05:33 1067,837,51|3,835,51|3,825,54|330,390|37,0%,211|1273,123
09-04 08:05:35 09-04 08:05:35 Restart cgminer as as No cgminer

09-04 08:06:04 0,0,42|0,0,42|0,0,45|7170,7200|38,2%,210|1273,23
09-04 08:06:36 0,0,33|0,0,32|0,0,34|7170,7170|35,0%,210|1273,230

09-04 08:13:32 7157,606,57|7742,606,57|9292,606,57|2490,2490|36,37%,184|1269,2461

09-04 08:13:44 Error code: 210, reason: Power error status: 0x0000->0x0001

09-04 08:48:47 power enable:1 errors:0 iout:228000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:3155 fan_speed:8880 temp0:366 temp1:378 temp2:318 status:0
09-04 08:48:48 power enable:1 errors:0 iout:228000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:3153 fan_speed:8970 temp0:362 temp1:379 temp2:319 status:0
09-04 08:48:49 power enable:1 errors:0 iout:229000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:3169 fan_speed:8910 temp0:366 temp1:380 temp2:317 status:0
09-04 08:48:50 power enable:1 errors:0 iout:229000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:3167 fan_speed:8970 temp0:361 temp1:380 temp2:321 status:0
09-04 08:48:51 power enable:1 errors:0 iout:229000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:3166 fan_speed:8910 temp0:365 temp1:379 temp2:317 status:0
09-04 08:48:52 power enable:1 errors:0 iout:229000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:3166 fan_speed:9000 temp0:365 temp1:382 temp2:319 status:0
09-04 08:48:53 power enable:1 errors:0 iout:229000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:3169 fan_speed:8910 temp0:362 temp1:381 temp2:318 status:0
09-04 08:48:54 power enable:1 errors:0 iout:230000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:3183 fan_speed:8970 temp0:364 temp1:381 temp2:319 status:0
09-04 08:48:56 power enable:1 errors:0 iout:230000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:3180 fan_speed:9000 temp0:363 temp1:383 temp2:321 status:0
09-04 08:48:57 power enable:1 errors:1 iout:0 vout:2 vout_set:1268 iin:-1 vin:-1 input_power:29 fan_speed:8970 temp0:369 temp1:384 temp2:321 status:0
09-04 08:48:58 power enable:1 errors:0 iout:0 vout:0 vout_set:1268 iin:-1 vin:-1 input_power:32 fan_speed:8880 temp0:369 temp1:385 temp2:321 status:20000
09-04 08:48:58 power enable:1 errors:0 iout:0 vout:0 vout_set:1268 iin:-1 vin:-1 input_power:32 fan_speed:8880 temp0:369 temp1:385 temp2:321 status:20000
09-04 08:48:59 power enable:1 errors:0 iout:9000 vout:115 vout_set:1268 iin:-1 vin:-1 input_power:45 fan_speed:9000 temp0:369 temp1:382 temp2:323 status:0
09-04 08:49:00 power enable:1 errors:0 iout:9000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:157 fan_speed:8970 temp0:366 temp1:385 temp2:320 status:0
09-04 08:49:01 power enable:1 errors:0 iout:9000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:157 fan_speed:8880 temp0:367 temp1:384 temp2:321 status:0
09-04 08:49:02 power enable:1 errors:0 iout:9000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:155 fan_speed:8880 temp0:370 temp1:384 temp2:323 status:0
09-04 08:49:03 power enable:1 errors:0 iout:9000 vout:1269 vout_set:1268 iin:-1 vin:-1 input_power:155 fan_speed:8940 temp0:368 temp1:387 temp2:321 status:0
09-04 08:49:04 power enable:1 errors:0 iout:9000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:155 fan_speed:8880 temp0:365 temp1:385 temp2:321 status:0
09-04 08:49:06 power enable:1 errors:0 iout:9000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:153 fan_speed:8880 temp0:369 temp1:386 temp2:319 status:0

09-04 08:49:06 Error code: 561, reason: Slot1 loss balance

09-04 08:49:07 power enable:1 errors:0 iout:9000 vout:1268 vout_set:1268 iin:-1 vin:-1 input_power:153 fan_speed:8970 temp0:370 temp1:381 temp2:320 status:0
09-04 08:49:15 09-04 08:49:15 Restart cgminer as as No cgminer
09-04 08:49:15 5503,797,59|5127,792,59|4028,782,62|3630,3630|32,2%,211|1268,138
09-04 08:49:47 0,0,43|0,0,43|0,0,45|7140,7170|33,0%,210|1269,228

09-04 09:32:15 19761,838,68|18657,832,66|15943,828,72|4200,4230|35,27%,182|1270,3360

09-04 09:32:23 Error code: 210, reason: Power error status: 0x0000->0x0001

power name 21 vender:1 hw: sw:102218.009 sn:62Aa193153292

09-04 09:32:13 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3360 fan_speed:8910 temp0:372 temp1:393 temp2:282 status:0

09-04 09:32:22 power enable:1 errors:0 iout:243000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:3360 fan_speed:8940 temp0:371 temp1:391 temp2:284 status:0

09-04 09:32:23 power enable:1 errors:1 iout:0 vout:945 vout_set:1270 iin:-1 vin:-1 input_power:23 fan_speed:8850 temp0:371 temp1:393 temp2:286 status:0

09-04 09:32:24 power enable:1 errors:0 iout:0 vout:0 vout_set:1270 iin:-1 vin:-1 input_power:23 fan_speed:8850 temp0:374 temp1:392 temp2:284 status:20000

09-04 09:32:33 power enable:1 errors:0 iout:9000 vout:1270 vout_set:1270 iin:-1 vin:-1 input_power:142 fan_speed:8820 temp0:371 temp1:393 temp2:281 status:0

09-04 09:32:48 1899,838,58|1338,832,56|842,828,62|2640,2640|34,32%,182|1273,131

09-04 09:32:52 Error code: 560, reason: Slot0 loss balance

09-04 09:33:00 09-04 09:33:00 Restart cgminer as as No cgminer

09-04 09:33:19 0,0,47|0,0,45|0,0,50|7170,7170|32,2%,209|1273,230

Источник

FIX: Windows Defender Protection definition update failed

One common issue comes with a variation of the error codes and accompanied by the Protection definition update failed message.

Today we’ll try to help you address this. In case you’re stuck with the error at hand, make sure to check the steps we provided below.

How do I fix the Protection definition update failed error?

1. Delete temporary files

The corruption within the system files, especially the ones concerning update distribution and storage is a rather common occurrence.

In this scenario, the previous iteration of the Windows Defender virus definition might be corrupted. In order to address this, we recommend clearing all temporary files and restarting the update procedure.

Windows Defender usually updates its definition automatically on a frequent basis and stores it in a dedicated folder. Deleting the content of the folder might help, as well.

After this, just restart your PC and make sure that it is connected to the internet. Windows Defender should do the rest.

2. Restart the Windows Defender service

On the other hand, if the Defender itself shows signs of stalling or misbehaves in an unusual manner, there are additional steps to take.

Even though Windows Defender is the built-in part of the Windows 10 shell, it can be disabled, and it also automatically turns off in presence of a third-party antivirus.

Now, even if you uninstalled the third-party antivirus prior to the occurrence of the update error, we encourage you to install one.

3. Install a third-party antivirus software

The worst thing that can happen to you while you’re using the Internet is being infected with malware or virus that will screw things over, steal your data, or cause other errors.

Therefore, you can’t rely solely on your Windows Defender to protect you, especially since the tool is ill-equipped to keep harmful software away.

Additionally, you’ll encounter errors such as the Windows Defender Protection definition update failed or the error code 2145107924.

To avoid such things from occurring, you should install trustworthy third-party antivirus software that utilizes machine learning and other security methods to protect you.

ESET Internet Security

Enjoy an error-free powerful security software that will fend off viruses of all kinds.

4. Update Defender manually

Furthermore, updates aren’t Windows Update exclusives. Namely, you can download the recent definition for Windows 10 manually and install it just like any other program.

We all know how Windows Update for Windows 10 frequently causes issues of different kinds. That makes this nothing new.

5. Run the SFC scan

If the built-in, essential part of Windows 10 won’t work as intended, you can’t reinstall it. What you can do is run the System File Checker and hope for the best.

This built-in system utility runs through the elevated Command Prompt. Its main purpose is to check for corruption within the system files. Once it gets what’s wrong, SFC will try to repair the affected files.

6. Reset your PC

Finally, if you’re still unable to resolve the issue at hand, we can go as far as recommending to reset your PC to factory settings.

It might seem discouraging at the first glimpse, but your files and apps won’t get affected whatsoever. In addition, the procedure is simple and quick – much better than the last resort.

This is, of course, a clean system reinstallation. After you reset your PC to factory values, the Windows Defender update error should be gone.

That’s it. We hope at least one of the aforementioned solutions was helpful in addressing the Protection Definition update failed error in Windows 10.

We also recommend checking out this article containing antivirus software with lifetime license. Take a look at the products and choose one that fits you best.

In case you’re aware of some alternatives or have a question regarding the ones we enlisted, make sure to tell us in the comments section below.

Frequently Asked Questions

If you wish to update your Windows Defender definitions, you can do it in multiple ways. Take a closer look at this detailed article dedicated to updating protection definitions and see for yourself.

There could be multiple causes. Learn more about the problem and how to fix it in this quick article dedicated to the Windows Defender not scanning issue.

This thorough article dedicated to Windows Defender update issues covers the problem and gives some simple and easy-to-follow fixes.

Источник

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

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

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

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:

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.

Источник