The copy of Windows is not original: it is the new bug that causes the latest Microsoft patch for Windows 7
What a job Microsoft is doing with updates. Yesterday we saw how the latest update released by Microsoft for Windows 7 was causing problems in shared resources and today we know that that same patch is generating new problems for users of Windows 7 when activating your copy of Windows.
This is a patch that came to fix bugs and improve system performance as a cumulative update right at the start of 2019, but it seems that not even with the change Things are going well this year for Microsoft, at least as far as updates are concerned.
An error that Microsoft is already aware of (they have added it to the known problems in that patch) and that, in fact, they are already investigating. An error with the patch that after installing the update, some users are experiencing a KMS activation error with the number 0xc004f200. This alerts you that the copy of Windows 7 you want to activate on your device is not original
Unlike the previous case, this problem seems to be widespread, so much so that from Reddit, and in the absence of official communication, They already offer a solution that involves uninstalling the KB971033 patch and restarting the computer.
"Later on you have to enter Command Prompt but with administrator permissions and write this series of instructions: "
- net stop sppsvc
- del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ah
- del %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ah
- del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
- del %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.dat
- net start sppsvc
- slmgr /ipk 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
- slmgr /ato
The only caution is that in the penultimate step, where it asks to enter the passkey, we have to use the correct passkey for the version of Windows we are using . Here you can find more information about it.
Of course at Microsoft they would have to take measures so that this type of situation, already habitual, does not continue to be repeated. _Have you had this problem?_ If so, can you tell us about your experience in the comments
Source | Windows Latest
