It might even though other people are saying "No". My guess is that it will however check bios mods but as long as you have everything matching up ex; Asus Motherboard + Asus Certificate + Asus OEM Slp Key. My guess is that microsoft might check that like they say they will and see if there is a mismatch like an Asus motherboard with a Dell Slic 2.1 inserted or a Dell Slic on a Dell MoBo with a Dell Cert but an HP Slp key. As for what exactly this will do, we will just have to wait for the release come Tuesday and see what happens lol.
i hope after feb. 16 a new tool will come out from our friends to help us retain our loader status. as of now im using DAZ's loader and still its ok. machine: HP CQ40-310 AU Activation: Activated using Daz Loader 1.7.5 Activation Mode: Loader Mode. Bios Modification Status: BIOS untouched (NO SLIC) Last Windows Update: 2/11/2010 Phil Time. Status: Still active. Waiting for Feb 16.
According to Daz it should be ok after Feb 16 + he says he has some other technique to get around it if he has too for everyone so I would not worry about it dude.
Code: @echo off set wat="%windir%\System32\Wat takeown /a /f %wat%\*" icacls %wat%\*" /grant *S-1-1-0:F icacls %wat%\WatAdminSvc.exe" /deny *S-1-1-0:(X) icacls %wat%\WatUX.exe" /deny *S-1-1-0:(X) del %wat%\WatWeb.dll" del %wat%\npWatWeb.dll" exit
sam what about mobo's that there are not slic's for like asrock or others. i mean what if a company used a mobo that was not there's like say dell using a asus mobo in the system. if ms checks this and see's a asus mobo with the dell cert and key they will mismatch. i have seen is the past more than one company using the same exact model mobo. like dell, hp and lenovo. i have seen all three of these a long while back with the same mobo model in them all were made by asus. do you really think they will kill these as well? i have 6 systems with the same asrock mobo using a asus slic and cert and asus key so what happens being a asrock board. know what i mean? imo i dont think they could target specific mobo's without killing a LOT more systems then they want to from dell and others.
It seems to me that this WAT update is mostly a scare tactic, I predict several thousand false positives within the first week it comes online. Then Prohibition V2
thanks sam.. yeah, i know daz can make a way.. i already told my friends to stay calm, this is just a scare tactic.. just like KB977074 update which has a problem. we thought its the new wat, until we searched for it. Most of my friends had a panic because of that.. but now we are rest assured about the DAZ loader
If Microsoft's focus is "not to change anything for legitimate users", then BIOS mods should not be affected. Why? OEMs reuse the same certificate and SLP key across a wide range of systems equipped with many different motherboards. It would be very difficult to create a whitelist of authorized boards. And if the OEM started using a new motherboard, it would be unfeasible for them to wait for Microsoft to "certify" that board for SLIC use. It would be ineffective to try and target non-legitimate users while avoiding accidents on genuine systems.
see thats exactly my point. like i said a dell using a asus or other brand mobo. and to top it off diff revisions of that mobo. i have seen that from dell especially where they started with one mobo say rev a then months later due to some change they switched to a updated model of that board say rev b etc..