Windows 10 isn't the only Windows version experiencing issues after receiving cumulative updates. Latest January security patch has also brought troubles for those on Windows 7. The update has reportedly resulted in several issues, including file share and connection issues. It is also giving some users0xc004f200 "not genuine" error. However, Microsoft says that at least this Windows 7 activation bug isn't caused by the latest update.

If you are also seeing this Windows 7 activation error after installing the latest updates (January patchKB4480970), Microsoft has acknowledged the problem and offered a workaround. The company writes:

Some users are reporting activation failures and "Not genuine" notifications starting around January 8, 2019, or later, on volume-licensed Windows 7 KMS clients. Notifications may state:

"Windows is not genuine."“Your computer might be running a counterfeit copy of Windows.”On screen errors and logged events reference “xC004F200 (non-genuine).”

Microsoft assures that this is NOT a problem associated with the latest security patch and the "timing of this issue" just coincides with the release of the January updates (KB4480960 and KB4480970) that were released earlier this week.

"A recent update to theMicrosoft Activation and Validationunintentionallycaused a "not genuine" error on volume-licensed Windows 7 clients that hadKB971033installed," Microsoft says. "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."

How to fix Windows 7 activation bugxC004F200 (non-genuine)

Microsoft says that Windows 7 devices that have installed KB971033 butdid not experience this activation issue between 10:00 UTC, January 8 and 4:30 UTC,January 9 should not experience theissue in the future. But if you do experience this problem and haveKB971033 installed, you can follow any of these steps to uninstall the update.

In theInstalled Updatesitem in Control Panel (Control Panel>Windows Update>View update history>Installed Updates),right-clickUpdate for Microsoft Windows (KB971033), and then selectUninstall.Run the following command in a Command Prompt window as administrator:wusa/uninstall /kb:971033Run the following command in a Command Prompt window as administrator:dism /online /Remove-Package /PackageName:Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~amd64~~7.1.7600.16395

After you have uninstalledKB 971033, rebuild the activation-related files and then reactivate the systemby running the following commands in a Command Prompt window as admin (for specific details, head over to this official post):

net stop sppuinotifysc config sppuinotify start= disablednet stop sppsvcdel %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0 /ahdel %windir%\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0 /ahdel %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.datdel %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\cache\cache.datnet start sppsvccscript c:\windows\system32\slmgr.vbs /ipk <edition-specific KMS client key>cscript c:\windows\system32\slmgr.vbs /atosc config sppuinotify start= demand

Along with the activation error that Microsoft says isn't related to the latest January update, the company has acknowledged two more issues with Windows 7 that do seem to have resulted from the latest patch. These include:

Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.After you apply this update, the network interface controller may stop working on some client software configurations. This occurs because of an issue related to a missing file, oem<number>.inf. The exact problematic configurations are currently unknown.

To resolve these Windows 7 issues, Microsoft has offered the following workarounds:

Fix for the first issue:

To locate the network device, launch devmgmt.msc. It may appear underOther Devices.To automatically rediscover the NIC and install drivers, selectScan for Hardware Changesfrom theActionmenu.Alternatively, install the drivers for the network device by right-clicking the device and choosingUpdate.Then chooseSearch automatically for updated driver softwareorBrowse my computer for driver software.

Workaround to fix the second issue (network interface controller)

To work around this issue use either a local account that is not part of the local “Administrators” group or any domain user (including domain administrators).

The company says it recommends theseworkarounds until a fix is made available in a future release. For more details,head over to the official postthat explains both what fixes the latest update has brought and the associated known issues.

- Relevant:After Multiple Disasters, Microsoft Has Finally Decided to Use Its Insiders to Test Cumulative Updates