Hi Both latest versions of loaders are killed on my machines. Both on fresh installs not in VM but ran on hardware. Ten minutes later Window snot genuine appears. So either these loaders are in the signatures or the servers are on. Ah well might be the mods for me or over to technet for cheapo keys. Cheers Edit RemoveWAT still working all genuine here again
Nicely said.. and as to what i keep on saying... just wait and see.. dont update since it is still voluntary... wait until THE GUYZ found a better solution.. of if you want to go genuine.. then buy one.. this solves all the problem.. though i doubt.. even the genuine users of windows 7 do encounter WAT errors... go check the microsoft forums about genuine advantage.. you will see lots of complains..
This thread is flying 95 pages and still one day left till the servers are online. Tomorow it will reach 150 if it goes like this. P.S. those guests (77 right now), whats their problem? Did they see a bear dancing or what
well... IMHO i think that it's pretty hard that M$ will try for this kind of approach. I think that WATU will stick for the easiest way, and working against things that they ( and WE ) already have seen on the WEB since longtime... Detecting Frankenbuilds, RemoveWAT and ChewWGA is not so hard for M$, and most of the GrubLoader too, cause they're still using a standard name and ( FIRST OF ALL ) they have a plain text string with the SLIC info bundled into them. They declared that "they wanna fight the spreading of pre-activated copies of Win7 on the net" , and we all know that 99,99% of them are using some old Loader or one of the other things i wrote above. So I think that encrypting the GRLDR (for developer that didn't already do it...) should be the first thing to think to do, cause using casual names, or lenght, it's not surely enough to avoid an easy detection by M$. Just my 2c. Clay
95 pages in this thread for one f***** MS Update! I cant believe it. Boys come on, take one beer, hardmod your BIOS and all will be good. I hope I dont have to read that some of our members (or guests) are making suicide. LOL
All speculation but interesting nevertheless - MS has two primary goals - to prove to legit buyers their product is safe and their money is well spent (thus the hype) and secondly to thwart the 'freeloaders' (no pun intended) offering AIO purchases - The WATU spyware thing won't be too aggressive at first anyways - they will feel their way for fear of 'non-genuine-ising" legit systems...so perhaps there will be a further 95 pages to this thread every 90 day update??
ii agree defo futher 90 page for the 90 day update but rembember to start with 90 day they could reduce that if they wanted to
the WAT Update runs a check and repair weekly to ensure that the licensing files are properly repaired. didnt know it run a weekly repair thats queit worrying and also i read this sumwere is this possible?? If you run Windows you need to pay for it's use. What I can not understand is why MS thinks that a certified copy would need to be rechecked every 90 or fewer days to see if it is still certified???? All it will take is some blackhat to write a virus/Trojan the makes it look like a copy is not certified and all hell will break out. Change a few DLL check sums here and there should do it. What is MS thinking?
OK... the last idea. The most simple idea! IMO it's not a good way to detect a loader by a specific byte sequence (signature, I mean detect the loader itself). I would try to detect them by their result! -WAT will search for the SLIC at physical memory and figure what SLIC it is. -WAT will write back the unmodified bootsector (will restore the original boot chain) and reboot -WATwill search for the SLIC at physical memory and figure what SLIC it is.--> WAT doesn't find a SLIC anymore, or a old SLIC2.0-->non genuine--> WAT restores the modified bootsector again. System is now non genuine and the bootsector and loader is running again. Also people that are running grub only would be save, because the SLIC would remain when WAT tries to reboot with the unmodified bootsector--> genuine AND WAT will restore the modified bootsector as well--->grub is working... Simple, easy, will detect all loaders....but not disable!!!
You're wrong, Loader is always there As sayed yesterday....Windowas was a while Genuine then the Popup Massage cam up with ....not genuine blabla (no reboot make, slic table always present)- Second With Mod Bios and wrong Cert / Keys Windows always not genuine ät a while. Only with Matched Combo of Slic / Cert / Key the Sytem stays Genuine.
Also, by MS allowing these hacks to go on for months is a brilliant business strategy. Allow people to use the OS for months, they get used to it, then flag their PC as non genuine. What happens is alot of novice users will rush to purchase a legit key which in turn creates a huge surge in sales. Very brilliant. There already are many people saying they are going to buy keys and WAT is not even released yet. Think about how many people have had their PCs soft modded by a friend. Many of these people are the ones that are going to go legit. The hardcore users will always find a way but the ones that rely on others will give up. MS already has a good handle on what kind of results they will get from WAT. They have probably tested almost all the soft mods out there on their own PCs and have tested many bios mods too. They know what will work and what won't.
And how about a boot cd with modified (slic'ed) grub which chainloads the "unmodified" hdd bootsector ???
SO does anyone have a gigabyte oem key then? 'cause im using acers and its valid(without the update though).
The boot order set at bios is prior to anything else...it should work....but kinda uncool to have a disk in the drive all the time..... Tomorrow will be the day..nice to have got replies about my theories..the first one isn't working, the second one hard to realise, but the last one.......could ban the loader on CD.......
I dont see any gigabyte key. But if you have a Dell Slic with Dell Cert & OEM Key everything is fine (Tested on my own Gigabyte MB)
I didnt find it either. Very strange that a cert leaker without a key...well if i do get busted ill just reflash it with dell(just like you)