Win7 Enterprise clients reporting “Not Genuine”, 0xc004f200, when they’ve been working for years

Topic

New Reply

Blame KB 971033, which shouldn’t even get installed on KMS-controlled machines. For some unknown reason, earlier today, Microsoft suddenly started pus
[See the full post at: Win7 Enterprise clients reporting “Not Genuine”, 0xc004f200, when they’ve been working for years]

5 users thanked author for this post.

GreatAndPowerfulTech, abbodi86, Elly, PhotM, OscarCP

Reply | Quote

Replies

While this has been spotted only, and so far, by some of those running Enterprise versions of Windows 7, this is also why I believe home users like me should never install Windows patches as soon as they are released (with the possible exception of patching a vulnerability to some malware that shows up and is known to pose an immediate and dire threat), but should wait for a while first (in my case, usually for three weeks, sometimes even longer). And professional administrators in charge of networks, I understand, test the patches first in some “trial” machines, to see if they are OK or not, before releasing them to the networked machines. Most home users, because they cannot do that, then better wait.

Group B, Windows 7 Pro SP1, x64.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

You’re welcome. I thought it could be a good hint to Retweet my finding from @jonathan_job as most may be suspecting January updates after all the events again.

@tweet_alqamar

Reply | Quote

It’s been reported on MAK licensed machines as well.

 

Reply | Quote

The fix’s “33PXH-7Y6KF-2VJC9-XBBR8-HVTHH” looks suspiciously like a Windows 7 activation code.

If so, shouldn’t anyone else trying that fix should be using their own activation code?

Hanlon's Razor: Never attribute to malice that which can be adequately explained by stupidity.

Reply | Quote

@karlston ahh no alas its just an install Key for KMS machines and useful for troublesome installs that ask for a key i.e. Win8.1 most editions has an annoying habit occasionally (just copy the relevant Key and insert in to a PID.txt file and throw it in to the Sources folder): https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v=ws.11) perfectly legit. No keys to the Win7 Kingdom there alas 😉

1 user thanked author for this post.

Karlston

Reply | Quote

New here it started occuring to our machines, we replaced the key with our Enterprise key and it’s been resolved for now.

Reply | Quote

For some unknown reason, earlier today, Microsoft suddenly started pushing the eight-month-old KB 971033 — an “update for Windows Activation Technologies” that was released on April 17.

Seem to recall this little Bundle of Joy has been round long before April 2018. Have they reissued/revamped it and its heading our way again I wonder?? I haven’t seen it in a few years on clean installs either in Stealth Mode or presented in WUD. Any way its on my little list of definitely avoid as even with a Genuine Key its another potential source of problems best avoided, and sounds like its creating its own Brand of Mayhem currently in the Corporate World.
Well we are off to a good start with Win7 Patches already, sounds like its going to be a turbulent last 12 Months ahead before EOL alas. 🙁

Reply | Quote

A six-digit KB# gives an idea how old the original is. Just another of the re-re-re-reissues.

1 user thanked author for this post.

BobbyB

Reply | Quote

Well-known scenario: KMS Server running Windows 2016 and KMS Enterprise client having installed KB971033 which does internet checks.
KB971033 was never downloaded by the Enterprise tools, but installed manually by users going directly on the internet to update or less likely, installed manually.
This issue was never encountered on Windows Server KMS running Windows 2012 R2 or earlier and is due to a change in the licensing checking mechanism built in Windows 2016.
I was under the impression that KB971033 is expired and is no longer presented to be downloaded, at least to Enterprise clients.

EDIT: I suspect the current issue is encountered by those who skipped Windows Server 2016 for KMS and moved directly to Windows 2019. Otherwise it would be old news.

5 users thanked author for this post.

Bill C., GreatAndPowerfulTech, woody, abbodi86, BobbyB

Reply | Quote

The issue which happened before was caused by having KB971033 installed, which do activation checks online
the problem was, Microsoft validation servers was not updated at that time to recognize the new KMS data from Windows 10, 2016, or 2012 R2 host servers

https://support.microsoft.com/en-us/help/4032981/powershell-script-for-windows-7-non-genuine-issue-is-available

they supposed had fixed that and servers were updated, and they also removed the genuine Legit Check site
https://www.microsoft.com/genuine/validate
so, KB971033 became not effective on Windows 7 Enterprise (although it still should not be installed)

5 users thanked author for this post.

Bill C., Microfix, PhotM, ch100, Kirsty

Reply | Quote

Just noticed in the article mentioned by Woody at https://support.microsoft.com/en-us/help/971033/description-of-the-update-for-windows-activation-technologies

Applies to: Windows 7 Home BasicWindows 7 Home PremiumWindows 7 ProfessionalWindows 7 Ultimate

This would explain why it is no longer offered to the Enterprise version. Offering it previously on Windows Update to Win 7 Enterprise can be considered a bug in this context.

4 users thanked author for this post.

Bill C., abbodi86, Microfix, BobbyB

Reply | Quote

Yep, I’m Win 7 Pro sp1 x64 and it was offered to me by Windows Update some time ago. I don’t remember when but probably a year or so ago. I never installed it and it’s been sitting in hidden updates ever since. I recall some discussion on this site that there was no need to install it on machines like mine. I’m assuming there is still no need to install it.

If it’s not installed, does that mean a computer is immune to the current issue?

Reply | Quote

DrBonzo wrote:

If it’s not installed, does that mean a computer is immune to the current issue?

There is no “current” issue. This has been ongoing for at least 3 years and affects KMS licensing clients.
If you don’t know what that means, it does not apply to you.
And try to avoid KB971033 if you don’t have activation issues.

1 user thanked author for this post.

BobbyB

Reply | Quote

My reason for asking the question is that I’ll bet other folks here have this question.

As far as “If you don’t know what that means, it does not apply to you.”, at the risk of seeming argumentative, that’s not necessarily the case. I know a number of people who when they retired opted for their workplace computer instead of the gold watch. They have no idea how their computer was set up or what kind of licensing they have. It turns out, though, that some have KMS and some don’t. So, yeah, it can most definitely affect them.

2 users thanked author for this post.

lanceboil, wdburt1

Reply | Quote

KMS activation has to be re-activated at least every 180 days.
Otherwise the OS becomes non-activated.
This is enterprise style of activation which should not apply to end users, or at least to non-professional end-users who do not use a central KMS server to provide activation.
If those acquaintances of yours use computers which do not have the required activation for any reason, I am afraid that this is beyond the scope of my post.

Reply | Quote

Believe me, if you don’t know what “KMS” means, you don’t want to know…. 🙂

3 users thanked author for this post.

ch100, columbia2011, abbodi86

Reply | Quote

This is only affects clients which have KB971033, but appears to be caused by installing KB4480960 on a KMS. KB4480960 should be avoided until MS has a fix.

Reply | Quote

Actually, take that back. We didn’t have KB4480960 on our KMS server or client that got the error. Still seems to be related to KB4480960 somehow given timing and MS reporting (https://support.microsoft.com/en-us/help/4480960/windows-server-2008-kb4480960)

After installing this update, some users are reporting the KMS Activation error, “Not Genuine”, 0xc004f200 on Windows 7 devices.

Going through the listed steps fixes it (did uninstall KB971033, didn’t try without it). Note the setup key listed there is for Win7 Enterprise.

1 user thanked author for this post.

ch100

Reply | Quote

The issue with Windows Server 2008 R2 is new and may explain why it comes up only now for some administrators. It is likely that the January 2019 update aligns the implementation of the KMS Server in Windows Server 2008 R2 with the implementation previously done in Windows Server 2016.
Bottom line is that any machine managed by KMS Server for activation should not have KB971033 installed.
See the PowerShell provided by Microsoft for cleanup if simple uninstall does not clear the issue. Woody has provided the URL where the PowerShell script can be found.

Reply | Quote

Hasn’t happened to any of our Win7 machines, nor did KB971033 appear on our 2012 WSUS. I have not approved KB4480960 nor am I likely to.

Reply | Quote

KB971033 is specific to Windows 7. Possibly Server 2008 R2 also.

Reply | Quote

It seems that the issue with KMS activation has something to do with the January 2019 updates in combination with the Activation Update. MS has confirmed it without further details. See
Update KB971033/KB4480960/KB4480970 bricks Windows 7 Genuine (0xc004f200)

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

4 users thanked author for this post.

Microfix, ch100, woody, geekdom

Reply | Quote

I also see that there’s a PowerShell script that’s supposed to solve the problem:

PowerShell script for Windows 7 “non-genuine” issue is available

Dated June 28, 2017.

 

2 users thanked author for this post.

Microfix, ch100

Reply | Quote

Windows 7 Pro x64….KB971033 was installed on my machine 05/12/14. Should I be uninstalling this ?

Reply | Quote

Yes, uninstall it. Then hide it if it shows back up in Windows Update.

4 users thanked author for this post.

Steve, BobbyB, Microfix, ch100

Reply | Quote

I uninstalled it and it showed right back up and I hid it. I guess my next question would be, without this installed and seeing that it has been installed for almost 41/2 years and no trouble, since it checks for genuine Windows, without it, is it going to come back on me and tell me I’m not activated because I don’t have it ?

Reply | Quote

You should not have any trouble without it.

4 users thanked author for this post.

BobbyB, Bill C., Microfix, ch100

Reply | Quote

Thank You..Breathing sigh of relief.

Reply | Quote

Back in the days of the Windows updates to avoid list for GWX or telemetry (pre-rollup, but post-GWX) one of the MVPs recommended uninstalling KB971033. Since that person’s advice has always proven to be very worthwhile, I uninstalled it back then and hid it.

When I checked back then, and verified tonight, my machine had that update installed on the day (4/26/2011) of the original install from the Win7Pro-64_SP1 DVD I bought after I built my machine.

I always believed (especially post-GWX) that activation technology might be leveraged or altered to disable a Win7 install.

That may not be what is happening here, but the trust is long gone.

Reply | Quote

https://support.microsoft.com/en-us/help/4487266/activation-failures-and-not-genuine-notifications-on-vl-win-7-kms-clie

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.

so the issue was again with AVS servers 🙂

4 users thanked author for this post.

Microfix, woody, ch100, gborn

Reply | Quote

Looks like MS reverted the change on their servers:
“… 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.”

https://support.microsoft.com/en-ca/help/4487266/activation-failures-and-not-genuine-notifications-on-vl-win-7-kms-clie

1 user thanked author for this post.

woody

Reply | Quote