Answered by:
"Not genuine windows" after December Windows Updates on VHS 2011

Question
-
Since I installed December's Windows updates on my WHS 2011 I am receiving "This computer is not running genuine Windows." with 0x8004fe21 displayed in the bottom of message box. This message appears shortly after the Launchpad connects to the home server from a client computer (a genuine Windows 7 in this case.) My home server IS a genuine windows install & it is still showing as "Windows is activated" in the server's system properties page.
I am not running ANY additional software on the WHS 2011 and have not even touched any of the add-in's. It is about as plain an installation as you can get.
I am seeking suggested solutions.
Friday, December 12, 2014 4:41 AM
Answers
-
This is a side-effect of the buggy KB3004394 update of December. Many users report this issue on the Internet. Uninstall this update and all will be ok.
Luc.
- Marked as answer by Olaf Engelke Monday, December 15, 2014 2:23 PM
Friday, December 12, 2014 9:10 AM
All replies
-
An additional question:
Is the Launchpad program (or is it the Dashboard) trying to say that the client computer (Windows 7) or the server (WHS 2011) is no longer a genuine Windows? Again, they are, and the system properties of both computers still show "Windows is activated."
Friday, December 12, 2014 5:33 AM -
Hi,
Please open Dashboard, navigate to Computer tab and check the Status of the Windows 7 client computer. Did it show as Online? Or any related warning?
à Since I installed December's Windows updates on my WHS 2011 I am receiving "This computer is not running genuine Windows." with 0x8004fe21 displayed in the bottom of message box.
Would you please provide a screenshot of this error message that you can get? It may help me to understand better.
Meanwhile, please refer to following article and check if can help you.
This computer is not running genuine windows 0x8004fe21
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
In addition, follow the path: %programdata%\microsoft\windows server\logs and check relevant dashboard log files if find more clues.
By the way. If it’s possible, for a test, would you please temporarily un-install this update and check if this issue still exists?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Friday, December 12, 2014 8:17 AM -
This is a side-effect of the buggy KB3004394 update of December. Many users report this issue on the Internet. Uninstall this update and all will be ok.
Luc.
- Marked as answer by Olaf Engelke Monday, December 15, 2014 2:23 PM
Friday, December 12, 2014 9:10 AM -
This issue is addressed by:
This windows update seems to have resolved the problem caused for me by KB3004394.
A lot of wasted time and anxiety. When will MS learn that, "Locks are for honest people," as the pirates will always find a way around it eventually and - as just demonstrated - it just creates fragility in the software purchased honestly.
Friday, December 12, 2014 10:56 PM