If you lock it this insanity will just migrate to another or new thread. oem-user isn't going away, this is his third or forth ID since 7 RTM'd
At least show the whole thing Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0x00000000 HealthStatus: PASS Event Time Stamp: 2:1:2010 18:42 WAT Activex: Registered WAT Admin Service: Registered HWID Data--> HWID Hash Current: NgAAAAEABAABAAEAAAADAAAAAgABAAEAonYIwYzpVPLos9LBEDNGmF6LmoiY6XR38fo2GNbH OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table NameOEMID ValueOEMTableID Value APICACRSYSAPIC0946 FACPACRSYSACRPRDCT HPETACRSYSOEMHPET MCFGACRSYSOEMMCFG SLICACRSYSACRPRDCT OEMBACRSYSOEMB0946 ASF!AMD SB600ASF SSDTA M I POWERNOW
I never had another something I do not listen to me here longer yen you have my info @ pn please make it.. thank you yen
Yen, please don't close this thread. You will agree with me that the issue of WAT is important to us in this forum. However, discussion at this time lacks proper focus and directions. I'm sure that with the official implementation of WAT, this thread will get constructive.
how are you doing miss you still need MGAdiag 2.0 beta pm me!! and the link to blacklisted keys Ok back to things at hand I have 2 dx 4200 one has the x64 driver on it and it show that the watermark remover is installed but other wise passed File Scan Data--> File Mismatch: C:\Windows\system32\en-us\user32.dll.mui[6.1.7600.16385] OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table NameOEMID ValueOEMTableID Value APICACRSYSAPIC0946 FACPACRSYSACRPRDCT HPETACRSYSOEMHPET MCFGACRSYSOEMMCFG SLIC_ASUS_Notebook OEMBACRSYSOEMB0946 ASF!AMD SB600ASF SSDTA M I POWERNOW
Why? You get the same result with new MGADiag 1.9.0019.0... Code: Windows Activation Technologies--> HrOffline: N/A HrOnline: N/A HealthStatus: N/A Event Time Stamp: N/A WAT Activex: Not Registered - 0x80040154 WAT Admin Service: Not Registered - 0x80040154 OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table NameOEMID ValueOEMTableID Value APICACRSYSAPIC1329 FACPACRSYSFACP1329 HPETACRSYSOEMHPET0 MCFGACRSYSOEMMCFG WDRTACRSYSNV-WDRT SLICACRSYSACRPRDCT OEMBACRSYSOEMB1329 NVHDACRSYSNVHDCP SSDTDpgPmmCpuPm
Soo... all this fuzz about "WAT update that does not do anything" is because "signatures" are not avilable yet. Lets see what 16th will bring
OK, what the MDL gurus say, should we install WAT of wait a bit and see what happens? In my case bios-mod. Cheers
so it looks like it detects the hashs of known files and repairs them via sfc /scannow on specific files and replaces them with original files from the store and tells you to reboot, so the replaced files can take affect.
You can just wait until it comes on WU and by then im sure we will know already what is detected and what not.