@dexta, As far as i can make out, you dont have WAT installed. otherwise you would have been flagged non-genuine because of the file mismatches and the remaining rearm count of 4...lol. or am i wrong?
"A problem is preventing Windows from accurately checking the license for this computer. Error code: 0x80070002. # The issue may occur when there are issues related to network connectivity. # This error may occur if there is a content mismatch in the DataStore folder."
Not that this is conclusive prrof of anything, but just my latest experiment. Used an untouched win7 RTM iso x86 and installed it on a system. After install, I used DAZ loader default, with Acer settings. Installed WAT, and MGA tool showed genuine, as well asonline verification. The system it is on has an offbrand motherboard and bios from 2002 where the bios had never been touched, so in this case, it appears that at least for now, bios/mb date does not play into anything at all.
BIOS build date may play an issue, but like I said above, I loaded a system using a loader, and untouched ISO, and it had a BIOS date of 2002.
I agree. WAT is still in its early stage, so we can only speculate what it can and may do in the future. It really depends on M$ how they will implement WAT and how it will evolve. If bios date becomes a criteria, perhaps the next thing we'll see would be bios date mods.
All the loader is doing is adding the SLIC data to the memory on boot (including cert data), it does not modify any other pre-loaded BIOS info, and it does not modify the BIOS build date.
Do 100% of installations with the dell or lenevo keys fail validation? I wonder if they really blacklisted those keys or if the problems with them are due to earlier versions of loaders or possibly using vista certs instead of newer onces (when available). Anyway, I wonder if all of these validations people are running to test their mod or loader are not just sending MS the information they need to create stronger signature files. Maybe people would be better served if they just validated when they need to to download a file or something.
dell key working fine here, btw for me more than 30+ systems all bios mods and all fine all pass and all genuine
I am starting to think that it isn't the key that is triggering deactivation on the dell and possibly lenevo key, I believe I have seen people posting successful results with both keys. So what is the common denominator for the ones that fail? I am thinking that most are early loaders and some bios mods where the OEM information and branding don't match up.
that wouldnt work either my pc has AMD branding with HP slic and the key is the dell key and it works fine. i try the lenovo key and it fails...
Seems the 0x80070002 error not too much to worry about right now - pobably just a mismatch in file checking rather than an invalid WAT response. BTW some real Jurassic Park boards getting past WAT!!