Windows 10 News and info | Forum
July 20, 2019, Loading... *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: This is a clean Ad-free Forum and protected by StopForumSpam, Project Honeypot, Botscout and AbuseIPDB | This forum does not use audio ads, popups, or other annoyances. New member registration currently disabled.
 
  Website   Home   Windows 8 Website GDPR Help Login Register  
By continuing to use the site or forum, you agree to the use of cookies, find out more by reading our GDPR policy.
Pages: [1]
  Print  
Share this topic on Del.icio.usShare this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on MySpaceShare this topic on RedditShare this topic on StumbleUponShare this topic on TechnoratiShare this topic on TwitterShare this topic on YahooShare this topic on Google buzz
Author Topic: Windows 7 KMS Activation Issues Caused by Microsoft Mistake, Not an Update  (Read 58 times)
javajolt
Administrator
Hero Member
*****
Offline Offline

Gender: Male
United States United States

Posts: 30238


I Do Windows


WWW Email
« on: January 14, 2019, 11:48:20 AM »
ReplyReply

On January 8th, 2019, Windows 7 machines that were activated through Key Management Service (KMS) started receiving a "Windows is not genuine" notification indicating that the Windows license was not valid. It turns out this problem was not caused by a January 2019 Patch Tuesday update, but rather by a change on Microsoft's activation servers.

In a support article released on January 10th, Microsoft explains that the activation issue was caused by a code change on their Microsoft Activation and Validation servers

Quote
A recent update to the Microsoft Activation and Validation unintentionally caused a "not genuine" error on volume-licensed Windows 7 clients that had KB 971033 installed. The change was introduced at 10:00:00 UTC on January 8, 2019, and was reverted at 4:30:00 UTC on January 9, 2019.

Note This timing coincides with the release of the 1B January 2019 updates (KB 4480960 and KB 4480970) that were released on Tuesday, January 8, 2019. These events are not related.

Windows 7 devices that have KB 971033 installed but did not experience this issue between the time of the change (10:00:00 UTC, January 8, 2019) and the time of the reversion of that change (4:30:00 UTC, January 9, 2019) should not experience the issue that is described in this article.


This code change affected Windows 7 machines that had the KB971033 update installed and were activated by KMS. The supported versions of Windows 7 that can be activated by KMS are:

■ Windows 7 Professional

■ Windows 7 Professional N

■ Windows 7 Professional E

■ Windows 7 Enterprise

■ Windows 7 Enterprise N

■ Windows 7 Enterprise E

For any machines that were affected, they would have seen warnings that state "Windows is not genuine", "This copy of Windows is not genuine", or 0xC004F200 errors.



Microsoft suggests that users uninstall the KB971033 update from any Windows 7 machines that are activated through KMS.

"We strongly recommend that you uninstall KB 971033 from all volume-licensed Windows 7-based devices," states Microsoft's support page. "This includes devices that are not currently affected by the issue that is mentioned in the "Symptoms" section."

If KB971033 is installed on a computer, users can uninstall it by issuing one of the following commands from an elevated command prompt.

Quote
wusa /uninstall /kb:971033

or

dism /online /Remove-Package /PackageName:Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~amd64~~7.1.7600.16395


Once you remove the update, you should restart the computer.

After the computer is uninstalled and the update has been confirmed to be removed, users should reactivate through KMS using the following commands.

Quote
net stop sppuinotify

sc config sppuinotify start= disabled

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

cscript c:\windows\system32\slmgr.vbs /ipk [edition-specific KMS client key]

cscript c:\windows\system32\slmgr.vbs /ato

sc config sppuinotify start= demand


For a list of KMS client keys that should be used, please see Microsoft's support page.

source
Logged



Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2017, Simple Machines

Google visited last this page April 11, 2019, 06:13:55 PM