You say that, but I just had to reinstall Windows following installation of WAT. Hazar, Yen and others did their best to provide various fixes, but to no avail, I'm afraid.
Did you try Daz loader? I'm still surprise though that some PC losses activation when indeed the signature servers for WAT is not yet running. But then U don't have to worry, switch over to Daz, so many people I know with Daz loader hasn't been invalidated. On your new install, used Daz loader and you will have nothing to worry about. Bear in mind that Chew-WGA and RemoveWAT has got too much publicity and since it modifies your system, it's easier for WAT to detect, but certainly not Daz loader
In my opinion qwerta369's error was not related to WAT whatsoever... looked more like a 'user' screw up.... I see lots of people starting to panic because of the WAT announcement, un-installing loader, installing other loader, install removewat, perform a bios mod etc etc.... just relax, sit back comfortably and let it come as it comes If WAT actually detects and disables some of the loaders / removewat techniques a new fix will surface...remember, "The fallen shall rise again!!!"
H-K, did you actually read the article?? Every week? the article mentions it checks every 90 days for updated signatures to detect cracks and patches
The time-delay between a check can go down of course... Seems like WAT is just another paper tiger. We'll see if there are massive reports of loaders not working anymore. 1 case (not working) out of thousands (working) isn't really significant, statistically spoken
This is just simply crazy. Why would M$ continue to verify if your copy windows is genuine every 90days? This is nonsense, and an afront to people who actually paid for the license.
Just for fun I gave a try to the Update for Microsoft Windows WAT (KB71033) found at the first page of this thread. I use a Gigabyte motherboard, a modded Bios with HP SlLIC 2.1, cert HP and Samsung SLP Key. Still genuine at reboot, made an WU to get latest defs for Windows Defender... still ok. I suppose the WAT servers are not set up yet. Of course I have previously imaging my Windows 7 partition.. Who knows...
Hey guy, why are you coming back with a new ID?? You have been preaching the doom day on 22 October last year and coming back with the same game again???
Hi Elle. Unfortunately, FreeStyler has not actually read my posts properly. Easier to just assume stupidity on my part, evidently. In a nutshell: October 2009 - flashed SLIC 2.1 modded bios, installed W7, installed matching cert, used leaked product key. Windows activated, all was fine and has been ever since. Last night - I installed WAT. This morning W7 has a fit about not being genuine. Hazar on here provided a couple of tools to try, Yen advised on some file deletions and to reinstall Fujitsu certs and to replace the product key. I completed all these steps, however W7 remained "not genuine". I think Hazar may be right when he said: Which would explain why any action I tried to reverse WAT's detection was ineffective. The only "user screw up", was my installing WAT.
According to my Event Logs, this is what happens when WAT is run Code: Genuine validation initiated. Health check initiated. Health check failure: hr = 0x8004FE22, HealthStatus: 0x0002000000000000 Healing process initiated. Healing process completed successfully. Genuine validation result: hrOffline = 0x0004FE01, hrOnline = 0x00000000 Genuine validation schedule created/changed. Interval: 129600 minutes SLUI notification schedule modified. Schedule type: 1 Genuine validation data sent to AVS successfully.
It is just one report of a problem, does not mean much in the scope of wheather or not WAT was the cause of the problem. Many people by now must have installed it and there are not massive reports of deactivation of a bios mod. I have seen cases where legitimate (purchased) corporate installs with correct enterprise keys used in Windows XP have become unactivated by a trojan, worm or viruses. Not saying that is what happened to you, but it is another possibility to consider as well.