I have debated the issue with the BIOS mods being the best solution. (Assuming that you have successfully modded the BIOS.) It would be so simple to deactivate the BIOS mods via an update from MS that compares your motherboard with the known OEM motherboards. If A=A, then genuine. RemoveWAT appears to be easy picking for MS because it is a low hanging fruit. SFC /scannow will kill it. This is a simple script that MS can include in its update. It does this now with MRT. Then why has MS not done so? It is all in the timing. I am guessing that MS will not take action until after the Release Candidate expires. This would eliminate people from flocking back to the RC, XP, Vista??, or Apple. This is what I call a bad business decision. To go from a revenue source (Win7) to no revenue.
Ding Ding Ding! We have a winner! lol That is basically the exact same reasoning I gave in the other thread... And that is very valid reasoning. Like I said, MS will wait until the time when it best suits them to handle the BIOS mod situation. They will play their hand very strategically...
You are correct. However, SFC will undo enough changes from the RWAT that causes the users to have to reapply the patch again. Or you could just eliminate the SFC all together. But for now, RemoveWAT is an alternative for those who need it. BTW, to restore the rearm count back to 4 so you can rearm Windows 7 again and again was first done by Napalum. It took me longer because I didn't know how to bypass the security.
I disagree about Microsoft disabling all systems with SLIC 2.1 from a BIOS revision date of 2008 (2007 or earlier is more realistic). I brought my Sony NW Series VGN-NW265F/B laptop from Black Friday 2009 with Windows 7 Home Premium preinstalled at Best Buy and EVEREST ULTIMATE EDITION tells me that my System BIOS date is 5/09/08 (SLIC 2.1 under ACPI). It would be a huge mess for Microsoft if they disabled thousands of laptops with a similar BIOS revision date as mine. It is using the same Windows 7 Home Premium Sony OEM key listed on this site. So for those people with BIOS revision dates in 2008 are still safe from having their Windows 7 deactivated. Is there a BIOS revision date changer software or a BIOS revision date spoofer software? That would be the next best thing because it is pretty scary typing "msinfo32" in run and it shows my BIOS version/date.
I picked the date of 2008 as a rough example, you may very well be correct that 2007 is a more reasonable year... Anyway, sorry for disrupting your harmonious thread Hazar ...back to the RemoveWAT discussion!
Well I would up purchasing a retail license key so I guess it doesn't matter to me anymore. I am still interested for my friend who'll be getting my OEM key (non-activated) though...I know he'd rather not have to bother activating his copy unless he really has to
I am new and still using xp, so I am dizzy with all of this loaders, slic, certs, bios. The only thing thar I want to know if this tool does not touch the bios of my mobo, and if it works. Thanks. Or do you recommend me other tool.
Hazar can you tell me if this is normal and I can continue to ignore these requests, or do I need to do something about it and re-run remove wat. I installed remove wat v2.1 on a fresh install of Window 7 Ultimate x64 no problem and everything seemed to have worked fine, then about a week ago I got 2 reminders to activate Windows 7, both within a couple of days. I ignored this and am still able to update, since then I have had several more requests to activate. Here's details from my system information page. OS Name Microsoft Windows 7 Ultimate Version 6.1.7600 Build 7600 System Type x64-based PC Hardware Abstraction Layer Version = "6.1.7600.16397" BIOS Version/Date Phoenix Technologies, LTD ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701, 02/10/2008 Thanks.
How to Verify Activation? I've run EVEREST Ultimate Edition and checked under Operating System. Here it lists the date the OS was installed and "Product Activation(WPA)". The value for activation is: Required (5 Days remaining) Which, based on the OS install date, would be a 30 day trial period and counting down as I've watched for several days now. Has anyone else seen this or used WAT beyond 30 days? YadaCode
Thanks for the info...do you have EVEREST? If so can you see the "trial" period starting to count down again?
[Hazar] So I'm clear on what to expect... When the trial period expires I should not experience any nags or notices? The user above indicated he received nags and needed to uninstall and reinstall WAT. Were his steps unnecessary? FYI - I use a lot of VM's both Virtual PC and Hyper-V. On one of the machines I set the system date a year in the future and then installed the OS and applied WAT. When running Everest there is no sign of any type of count down and Everest says the OS install date is a year in the future. Is there any advantage in doing this or it just "looks" better...more reassuring? Great work my friend! Please accept my comments as "help" and not being critical.
What you see/change in everest would be pureley aesthetic, and not have any real effect. Also, the person above was probably using 2.0, or it got reset by an update so needed to be reapplied. P.S. It's easy to see you're not being critical, I'm really down to earth about these sort of things
Hi YadaCode If you want the registration to "look" more authentic I suggest you try Chew WGA. Hazar is helping with the release of Chew WGA V1.0. You will also see "Windows is activated" at the bottom of the Properties screen. Both RemoveWAT and Chew WGA have worked for me and are excellent tools. Big thanks Hazar!
That won't help with what he wants. He is just asking about everest. Also, RemoveWAT is a bit different to chew in the way it works. I am actually onboard for the next release of chew, just for now, I reccomend to use this. I am not updating it for now, because I am working on chew. Believe me, the new chew will be a lot better than this It's approach is a lot better than previous versions. I will probably be involved in the programming or providing information on it
It may be a weird question, but what actually is "the approach"? I guess the patching process is changing hex strings in windows files to get windows thinking it's activated, or to let it "forget" it even has to be activated. But what are the different ways of doing that? And why are some approaches better than others? So what makes chew 1 better than previous versions and remove wat?