Then we started hearing rumors that manually uninstalling KB 3004394 would, in fact, cause more problems. 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." On Thursday morning, Microsoft pulled the patch.
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.
And if you guessed that the bad patch may not even show up on customers' systems, you get the giant whoopee cushion. If you guessed that the aberrant patch is KB 3004394, you get the big prize. If you guessed that all of those problems were caused by a bad Black Tuesday patch, you win the small prize. Looking around the Internet and answering my email, I see at least a hundred posts from people who are being told their copy of Windows 7 is disingenuous when, in fact, they know it's genuine. I could go on - there are dozens more, in the Activation section alone, all in the same vein - but you get the gist of it.
I really hope it works guys!!!!! Check out other tutorials on this: _ Really Thanks for Watching GUys!!!! Leave a Like and SUbscribe!!! Additional Tags (Dont Mind this): Windows, windows 7, error, not, genuine, windows is not genuine, fix, build, 7600, 7601, problem, working, method, Windows Genuine Advantage, Microsoft Windows (Operating System), Computer, Tutorial, Desktop, laptop, Windows 7 not genuine, windows 7 not genuine virus, windows 7 not genuine upgrade to windows 10, windows 7 not genuine build 7600, windows 7 not genuine fix build 7601, windows 7 not genuine error, windows 7 not genuine crack, windows 7 not genuine 2015, windows 7 not genuine windows 7 build 7601 not genuine fix, windows 7 build 7601 product key, windows 7 genuine build 7601, windows is not genuine,windows genuine check, ‘slmgr’ is not recognized as an internal or external command, windows genuine.
I also show you how to fix the problem this limist has been exceed maximum times and also the command is not recognised. I just type in the code slmgr -rearm in cmd, and that should do the work. So, in Windows 7, due to the KB971033 Update, the windows which were not previously original, had this problem, saying this copy is not genuine. I really wanted to do this because I myself had this problem for a while and I finally found a proper fix. Hey Guys!!! In this video, I am doing a quick tutorial on how to fix the message saying that ” THIS COPY OF WINDOWS IS NOT GENUINE BUILD 7601″.