Version 0.7 works flawlessly for me. Hazar's loader never worked, others gave me blue screen. Thnx anemeros
Okay, an update... Rohan tested Chew-WGA 0.8, and it failed on his Windows 7 Starter (on a Pentium III, lol). I figure, if I can get it to run smoothly on a P3 with Win7 Starter, then it should work on anything, right? Anyway, I've been tracking down some bugs and repairing code all night (it's now nearly 5:30AM), so I'm going to sleep on it, dream of it, and finish it in the morning... and by "morning", of course I mean 1 or 2pm when I wake up. LOL Regarding the uninstaller I promised (UnChew), I now have all the components I need to finish it, but the priority right now is 0.8. The uninstaller will most likely be a separate utility, unless I figure out a clean way of incorporating it into Chew-WGA itself.
@anemeros. Chew 0.6 and Chew 0.7 didnt work for my system so I am waiting Chew-WGA 0.8. I think you are member of demonoid.com. I saw you there.
Yep, I am a member of demonoid. Sorry 0.7 didn't work for you. Lots of bugs have been sorted out for 0.8. I have it working now on Starter x86 and Ultimate x64. Details coming very soon!
So hoping that with the new version of chew-wga, aka 0.8 the genuine image altogether will be present,(that will be cool).. And also that it will automatically unlock the files that will patched... Just to let u know 0.7 works fine on clean install..+ pluspatch to be always genuine with mgadiag.exe even till yr 2099...it fool window that it is always on trial..
just an idea...i'm curious to learn where is it the phone algo (like in office 2007) to try to modify it.
Q. Does Chew-WGA actually replace or patch windows files? And if that is the case wouldn't that protentially cause a future issue with windows updates replacing these files with never versions. (not nessasary with the intention to null Chew, just in the normal run of things).
Indeed, when updates come out, there may be a big problem with this. This is a good patch but I reckon people should head over to loaders nearer October 22nd. But stay here for now. You're safe with Chew.
I'm not sure of any good way, short of hacking the systemcpl.dll file directly, to achieve this. It already does attempt this, but there was a problem with the code which caused it to be inconsistent. This has been resolved. Thanks for the good report.
I thought I was nearly done with it about a week ago, but then realized when I learned more about Windows 7 system file protections, that I had my work cut out for me. For some users, particularly on Multi-User Windows API Client, My System CPL Resources, and Windows Shell Common DLL, it would fail consistently. Anyway, I'm working on it every day for at least 45 minutes, so hopefully there will be something to show for it this week, if all goes well.
Yes, I can see this. Updates only work on specific files, not EVERY Windows file. So the only way an update could kill Chew, is if it specifically targeted the files Chew changes... and I'm sure we'd get warning about this specific update soon enough... (I WOULD be concerned about a service pack however, as these DO tend to change most files.)