Windows 7 is suddenly telling users it isn't genuine -- and it has nothing to do with Windows being stolen.
- Windows Genuine but getting message not genuine
- I'm being told my copy of Windows is not genuine, but it is.
- Windows 7 Message re Validity
- Windows Activation Issues
- "This computer is not running a genuine version of windows" I know this version is genuine. How do I fix?
- "Windows 7 Build 7601 This copy of Windows is not genuine." Purchased hard copy of Windows from retail store.
- I receive error "This copy of Windows is not genuine"
- Windows installed latest updates, and now says my version of Windows isn't genuine?
- This computer is not running genuine windows
- Why is my OS no longer Valid?
- Windows keeps claiming my genuine copy is non-genuine.
- Validation Code: 0x8004FE21
- "This computer is not running genuine windows" What is this? How do I fix it?
- Genuine Windows Problem (0x8004fe21)
- Windows 7 "not genuine" message after 3 years without a problem
- Another "This computer is not running genuine Windows"
- Windows 7 build 7601 not genuine
- 'This computer is not running genuine windows' message
- Windows 7 Build 7601 this copy of windows is not genuine - need help
- Why do I get this message "This computer is not running genuine Windows."
If you guessed that all of those problems were caused by a bad Black Tuesday patch, you win the small prize. If you guessed that the aberrant patch is KB 3004394, you get the big prize. And if you guessed that the bad patch may not even show up on customers' systems, you get the giant whoopee cushion. Let's give Microsoft a big Bronx cheer.
Windows users started screaming about KB 3004394 within hours of it being rolled out of the Automatic Update chute last Tuesday: Bogus UAC prompts, MMC plug-ins refused to start, Windows Defender wouldn't start, Microsoft Security Essentials wouldn't install, VirtualBox wouldn't work, the AMD Catalyst Omega driver wouldn't install, and other Windows Updates wouldn't install after KB 3004394 infected those machines.
On Thursday morning, Microsoft pulled the patch. On Thursday afternoon, Microsoft started advising in the Answers Forum that people infected with KB 3004394 should manually remove the patch, although the KB 3004394 article admonished, "The ability to remove Windows Updates through Control Panel may no longer function on some Windows 7 SP1-based and Windows Server 2008 R2 SP1-based computers after KB 3004394 is installed."
Then we started hearing rumors that manually uninstalling KB 3004394 would, in fact, cause more problems.
Late Thursday night, Microsoft released its "Silver Bullet" patch, KB 3024777, which nullified KB 3004394 (I'm tempted to say "uninstalled" but it isn't clear whether the bad patch is literally uninstalled). In addition, the Silver Bullet patch removed all mention of KB 3004394 and KB 3024777 from the list of installed updates.
- Download and install KB 3024777.
- Reboot. Then, for the heck of it, reboot again.
- Click Start, right-click Computer, choose Properties, and look at the bottom to see if you've been activated. If you haven't, click the link to Activate Windows Now. Reboot again.
No comments:
Post a Comment