Use Hazar method. Search previous pages to find a solution. Someone else also had a problem like you.
It won't work now i think. Hazar asked to disconnect from the net, install the update and then run the commands to block access of those files. But it looks they have already done their job for GeekSquad.
Sorry if this issue has already been addressed but this thread's pretty long now at 64 pages. Has anyone who'd done a BIOS mod and activated Windows 7 Ultimate passed the authentication thing? I'm referring to hardmodded systems with no loaders BUT using SLICs, SLPs, product keys and certificates not from their motherboards / notebooks' manufacturers. My previous systems where I'd installed and activated Windows 7 Ultimate successfully and painlessly all had their BIOS updated with manufacturer relevant information but I'm on a Zotac motherboard based system now running Dell SLIC, SLP, product key and certificate.
We just need to wait for 2 more days when the update is officially released so we can be sure the call-home servers are up and running. Right now some say the update didn't change anything and some have become non-genuine.
Yup, i'm one of them, i installed update already and became non-genuine, and then i used REMOVEWAT and non-genuine messages disappeared, is there any chance of them returning still? btw, in services, 'watadmin' from update is still there? :S could this effect my copy in any way still ?
Dell XPS M1530 with modded bios (Dell) and non-Dell key called not genuine 20 hours after installation of WAT. This may be worse than we think, no key found to reactivate and Hazar's method did not work. Didn't try REMOVEWAT.
you installed update? I m wonder, why you download & install? why not uncheck box "Update for Microsoft Windows (KB971033)? :confuse
After installing the update and applying Hazar's latest fix all seems well. Many thanks Hazar WatAdminSvc on mine is reporting: <Failed to Read Description. Error Code: 5 > (7 Ult. x86 with an early loader)
Also, @anemeros sure, your team may have done all this fancy work for Chew7 and I'm really happy for you. People wanted a fix, and they wanted a fix now, and I thought it was a good idea. You can say what you like about it, seems to work for me. If they require them in the future, we're just gonna work around it. Perhaps people can block WatAdminSvc with their firewall so it returns genuine. There's no ends of solutions that me and the other community members are willing to think of and provide, and put simply, anything they do, we can put back
Absolutely! I don't see your effort as a rushed stab in the dark at all, quite the contrary. AFAICS this should do the job nicely but that said, we can of course only wait and see... always the old cat n mouse game and many ways to skin a rabbit! Alot to be said for immunisation, and any effort is muchly appreciated
hazar you are right @ anemeros WAT can perform a check of the integrity of ACL (this is very easy to do) for example to systemcpl.dll After checking the change of ACLs , can change/modify the vulnerable point (user32.dll) User32.dll is a big problem and the party is over (chess game) good luck
user32 is just a gui library (patched to remove watermark). no ACL editing going on there. Do you mean MD5?
It's me again! Nice thread....... I have said WAT isn't on yet....well I haven't checked if it connects to somewhere or if there are some servers already running at M$.....I meant to refer to WAT is too early it's probably not (fully) working... Mr. Sievert and Mr. Alex Kochis have been fired!! Sievert a long time ago, Kochis a few months...... You are quoting politics of a fired person. In fact M$ has changed its politics on piracy.... M$ was very very soft about. They will now reduce the amount of pirated (I don't like that word) OSes..for sure. The successor of Kochies will fight against piracy..I guess that's the reason why Kochis was fired....he was too friendly.. I guess WAT will start to act 'strong'. It will be an optional update to avoid much agitation. I guess checks that are easy to perform (biosdate, SMBIOS info) and an definitive attribute to detect a bios that cannot be officially SLICed will be used to mark the OS non genuine. Also a memory resistant task can analyse the boot process at reboot. What is the difference between every loader and a SLICed bios???? At a SLICEd bios the SLIC is mapped to physical memory BEFORE the bios calls the boot device!!! This would kill any loader...encryption??? LOL...
To be honest, Microsoft don't actually care about piracy (they make the big money on the OEMs like Dell and Acer) Microsoft's partners DO CARE, and their biggest worry is unscrupulous system builders SLICing some BIOS on a computer and giving it to a customer, having to pay no money for a license. Of course, Microsoft has to act on this.
Piracy = publicity. I reckon M$ revel in the hype that is caused by news of new WAT updates. Just like when 7 officialy launched back in october. The funny thing is that rather than making us all go reaching for the cash and paying for a valid license, all these press releases do is lay down the gauntlet for communities such as ours to find another way of circumventing their anti piracy technologies. So the new WAT guy is trying to come down hard on all the pirates.......... Well he is new to his job and has to make a good impression for old Billy boy does'nt he ? Ironically isnt that punishing the people that actually pointed out the flaws in the OS that the boffins at M$ could'nt ? IMO, its all hype and gives us something good to discuss about. I mean come on everyone........ M$ have only just after 17, yes 17 years finally managed to close a security loop-hole present in all windows OS's. Do we really think they can shut the door on all WAT workarounds just 4 months after the official release of windows 7....................Me thinks not !!
Memory is very important We must remember that happened with SP1 for VISTA. timerstop x32 and x64 ---> disabled paradox (widely used emulator driver) ---> disabled Emulators (softmod) were not affected but that's probably why it has appeared WAT @ hazar A single watermark and spoils everything user32.dll is very vulnerable because their permits acl the md5 is falsifiable but not acl files good luck
After reading my posts you'll get the feeling that WAT will kill everything...that's not meant to be.... I want members to think about, not to get agitated. How many OSes will be affected is up to M$. They can decide about. There are technically many possibilities to find 'pirated' OSes..that's what I want to say. At the past M$ hasn't realised what's possible... You may decide to install WAT. What will be your intention to install it? You know for sure if your OS is 'pirated' or not! Do you want W7 for free? Do you want to play with WAT? Just to have a look if your OS is save? Are you curious about if WAT is able to detect what you have done? Well...I like to play..... To all that don't care about M$ and want a 'free' OS..don't install WAT.... I cannot join the game at 16/17 of February I''ll be absent.....