{"id":8230,"date":"2019-01-10T07:35:13","date_gmt":"2019-01-10T06:35:13","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8230"},"modified":"2019-04-11T13:38:05","modified_gmt":"2019-04-11T11:38:05","slug":"update-kb971033-bricks-windows-7-genuine-0xc004f200","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/01\/10\/update-kb971033-bricks-windows-7-genuine-0xc004f200\/","title":{"rendered":"Update KB971033\/KB4480960\/KB4480970 bricks Windows 7 Genuine (0xc004f200)"},"content":{"rendered":"

\"win7\"[German<\/a>]New day, new problem: Microsoft probably released the old update KB971033 again the night before. As it looks, Windows 7 is no longer activated after installing the update and is reported as not genuine. Addendum:<\/strong> It's related to Windows 7 January 7, 2019 Update KB4480960 (security-only) or KB4480970 (Monthly Rollup).<\/p>\n

<\/p>\n

\"\"I just stumbled across the topic at askwoody.com<\/a>, where it hit enterprise clients with Windows 7. <\/p>\n

Update KB971033 for Windows 7<\/h2>\n

The description for update KB971033<\/a> was last updated on April 17, 2018 and deals with the topic Windows Activation Technologies for Windows 7. There is a new activation update there to ensure that Windows 7 can be activated.<\/p>\n

Update re-released, breaks on clients<\/h2>\n

Woody Leonhard wrote<\/a> that night that Microsoft has re-released the KB971033 update for unknown reasons. Since then, admins have complained about Windows 7 clients that are no longer activated. On reddit there is this thread<\/a> which describes the drama..<\/p>\n

\n

PSA: Windows 7 Genuine Advantage – KB971033. Make sure you don't have it!<\/p>\n

Woke up this morning to find a few thousand Windows 7 VDI machines reporting that Windows 7 wasn't genuine. After much troubleshooting we found that KB971033 (should not have been installed in a KMS environment in the first place) was installed on these machines. Until today having this KB installed hasn't been an issue, it appears a change to how Microsoft's activation servers respond to a standard KMS key being sent to them may be to blame. <\/p>\n

Removing the update, deleting the KMS cache and activation data from the PC's and re-activating against KMS resolved the issue.<\/p>\n<\/blockquote>\n

The thread starter found suddenly a few thousand Windows 7 VDI machines that reported that Windows 7 was not genuine. After many tests, he found that KB971033 (which should not have been installed at all in a KMS environment) was installed on these machines and causes this issue.  <\/p>\n

The thread starter writes that installing this KB has not been a problem so far. It seems that a change in the response of Microsoft's activation servers to a default KMS key sent to them could be to blame. Removing the update, deleting the KMS cache and activation data from the PCs, and reactivating against KMS fixed the problem. A user has posted the following fix script:<\/p>\n

wusa \/uninstall \/kb:971033 \/quiet\nnet stop sppsvc \/y\ndel %windir%\\system32\\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 \/ah\ndel %windir%\\system32\\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 \/ah\ndel %windir%\\ServiceProfiles\\NetworkService\\AppData\\Roaming\\Microsoft\\SoftwareProtectionPlatform\\tokens.dat\ndel %windir%\\ServiceProfiles\\NetworkService\\AppData\\Roaming\\Microsoft\\SoftwareProtectionPlatform\\cache\\cache.dat\nnet start sppsvc\ncscript %windir%\\system32\\slmgr.vbs \/ipk 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH\ncscript %windir%\\system32\\slmgr.vbs \/ato\n<\/pre>\n
Another reddit.com tread addresses<\/a> the same issue. Somebody affected? Addendum:<\/strong> Microsoft has confirmed the error in KB articles 4480960<\/a> (security only) and 4480970<\/a> (Monthly Rollup) for Windows 7 and is investigating it.<\/p>\n","protected":false},"excerpt":{"rendered":"
[German]New day, new problem: Microsoft probably released the old update KB971033 again the night before. As it looks, Windows 7 is no longer activated after installing the update and is reported as not genuine. Addendum: It's related to Windows 7 … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,1218],"tags":[1778,1777,195,17],"class_list":["post-8230","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-virtualization","tag-error-0xc004f200","tag-kb971033","tag-update","tag-windows-7"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=8230"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8230\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=8230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=8230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=8230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}