Yes, it will *work*...but you have not answered the question. His question is basically whether there will be activation (or stability) issues in the future when running Windows Update, namely with files that CHEW has modified being replaced by future updated ones via WU... Example: CHEW modifies the Win7 OS. Windows Update attempts to update something that CHEW has modified, or overwrites files that CHEW has modified. The end result is either an unstable system, or broken "activation"... That is what I believe Alex32 is getting at. Hopefully a future WU would not disable CHEW and drop you straight into RFM...
An uninstaller/backup tool is in the works, possibly as soon as 0.8. If you can't wait, then you can follow these instructions to manually uninstall Chew-WGA: Using 7-Zip, open your install.wim file from your Windows 7 installation disk under the sources folder. Navigate to the Windows\System32\en-US folder within the archive. Now extract the following files to %SystemRoot%\System32\en-US (and %SystemRoot%\SysWOW64\en-US if you are using x64): calc.exe.mui, mspaint.exe.mui, notepad.exe.mui, shell32.dll.mui, sppcommdlg.dll.mui, systemcpl.dll.mui, user32.dll.mui Next, extract "Program Files\Windows Photo Viewer\en-US\photoviewer.dll.mui" and "Program files\Windows NT\Accessories\en-US\wordpad.exe.mui" and replace the files on your system in the corresponding folders. Next, extract the "Windows\System32\slui.exe", "Windows\System32\slmgr.vbs", "Windows\SysWOW64\slmgr.vbs", "Windows\System32\winver.exe", and "Windows\SysWOW64\winver.exe" and overwrite the corresponding files on your hard drive. If you have trouble with access denied errors, then run the following commands on your locked targets and try again: Code: TAKEOWN /F "target filename here" CACLS "target filename here" /C /G "%username%":F MOVE /Y "target filename here" "backup folder location here" Regarding registry changes, you can extract "Windows\system32\config\SOFTWARE" from your install.wim file. Then open regedit, select the root of the HKEY_LOCAL_MACHINE branch. Then click File->Load Hive->and select the "SOFTWARE" file you just extracted from install.wim. Then regedit will ask you for a "key name" for this hive. Type "SOFTWARE2" and click OK. You will then see a new key under HKEY_LOCAL_MACHINE called SOFTWARE2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE2\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform. Then right click on the "Activation" subkey, and choose "Export" from the context menu. Name it "activation.reg" and save it anywhere you like. Next double click on the "Plugins" key under SoftwareProtectionPlatform. Then right click on "Modules", choose "Export" and save the file as "modules.reg". Now navigate to HKEY_LOCAL_MACHINE\SOFTWARE2, and go to File -> Unload Hive. You will be prompted with a question, "Are you sure you want to unload the current key and all of its subkeys?" Click YES. Notice how the SOFTWARE2 key is gone now? Okay. Close regedit, and navigate on your hard drive to where you saved "activation.reg" and "modules.reg". Open each of these files in notepad or any text editor, and do a text replace changing all "SOFTWARE2" references to "SOFTWARE". Save the files. Now you can import them. To do this, just double click on each reg file. When prompted with "Are you sure you want to continue?", click Yes. Next, go to your DOS prompt (elevated) and run the following commands: Code: REG ADD "HKLM\SYSTEM\CurrentControlSet\services\sppsvc" /t REG_DWORD /v Start /d 0x1 /f sc config sppuinotify start= auto If you followed these instructions carefully, then restart your computer and everything will be back to how it was before.
I do not anticipate any problems with system stability in the future, but technically, this is experimental software, not intended for application on a system for long term use. With that said, the only things that could potentially (although however unlikely) cause a stability issue, would be the activation client core or the software protection platform plug-in modules. 92% of the files that are modified are basically harmless changes and future WU's are unlikely to tamper with the same resources that Chew-WGA has modified, and therefore I doubt there would be any sort of conflict, unless a hotfix is designed to directly target Chew-WGA users, in which case, nothing would be stopping you from re-running the patch (aside from moral issues, lol). If Windows Updates "repair" the patched files, it should not cause any instability as far as I know unless the hotfix itself is unstable.
It is unlikely unless MS decides to intentionally update their software protection platform at certain intervals in an attempt to detect and disable newer hacks and loaders...which would not be out of the question for them. It would seem logical to me that the software protection platform would be something that MS would update from time to time to combat new hacktivation techniques (e.x. CHEW and loaders) in the name of protecting their customers from "counterfeit" software vendors. One can only hope they do not...or do not modify things in a way that will intentionally cause stability issues for people running hacks.
Serious pirates should use common sense when downloading and installing Windows Updates, and should disable the updates that they don't actually need. As far as WU "improving" the SPP, most of the file changes will be with EXE and DLL programs themselves, and not so much their MUI resources. Also, some of the registry changes that Chew-WGA makes are to keys and values that were intentionally placed there by M$ with the open option to disable nags - the same keys and values that are adjusted upon legitimate activation I suspect.
Well of course, I wish everyone would use common sense, but that is not the world we live in, unfortunately (I can cite many examples, but will refrain due to space limitations ). Anyway, just wanted to ask a few questions here for myself. I mean no disrespect towards the work that you do, as it is needed for all those people who cannot get loaders to work, or get their BIOS modded... Just trying to clarify things a bit...
No problem, and I'm not offended. I enjoy answering questions. Besides, I expect people to be skeptical.
Just want to say a big thank to anemeros. Keep on working hard..and thy 4 your answers. I wish I could be more active on this forum but I dont have intnet at home now (thankfully ive dwnloaded windows 7 rtm just before) and I'm now on a mobile phone... I'm only 16 and modded my AMI bios..lol.. Waiting 4 new chew 4 testing.. Its a pleasure 4 me..lol
Chew-WGA worked for me in a Win7 Ultimate install in Virtualbox. The 1st and 3rd lines said fail but it did activate and continues so after reboots. Can translate into Spanish if desired.
Just to give an update, I've been working hard on Chew-WGA 0.8, and the latest thing I've finished with it is the automatic creation of a system restore point, so that uninstallation will be easy in the event that a problem arises.
Anyone interested in Chew-WGA being implemented for their language, please PM me. So far, I've finished English, German, and French for version 0.8.
Fails in Hyper-V First off, thanks for putting your time into this tool. I can't get Windows 7 64 RTM to be activated in a Hyper-V environment. I have no problems getting W7 to be activated on a physical machine, but when I use any loader in the Hyper-V image it hangs on boot up. When I saw Chew-WGA I was excited because I thought for sure it would work as it's not using a boot loader. When I run your tool it gives me a 100% but when I reboot (after setting the clock forward by a few months) it comes up as not genuine. I am at a loss... Any help would be appreciated. Thanks.
hi all, i have windows 7 ultimate x64 installed and i tried chew wga 0.7. i still have unactivated windows, although i got 100 % success. here: Log created on pet 04.09.2009 at 18:13:38,34 [OKAY] = previously patched or not applicable. [PASS] = successfully patched this session. [FAIL] = was not patched for some reason. Success Rate: 100.0% / Failure Rate: 0.0% * [OKAY] Multi-User Windows USER API Client * [OKAY] My System CPL Resources * [OKAY] Windows Shell Common DLL * [OKAY] Notepad Genuine Check * [OKAY] Calculator Genuine Check * [OKAY] MS-Paint Genuine Check * [OKAY] Version Reporter Applet * [PASS] Windows Activation Client Core * [OKAY] Software Licensing UI API * [OKAY] Software Licensing Management Tool * [OKAY] Digital Licenses Enforcement * [PASS] Windows Activation Schedule * [OKAY] Windows Activation Interval * [OKAY] Windows Activation Notice * [OKAY] Software Protection Plug-Ins * [PASS] Windows Send Feedback Tool any suggestions? p.s. i have hp probook 4170s
This is a software error that occurs when the resource cache isn't being updated. It has already been noted and repaired for version 0.8. In the meantime, you may want to uninstall Chew-WGA using the directions posted in this thread, and then run it again. When it finishes, go to the command prompt and run "%SystemRoot%\System32\mcbuilder.exe" and hopefully that will solve your problem.
chew-wga cused slmgr error. How to fix? I ran the chew-wga on two of windows 7 boxes and both showing the same problem: slmgr gave out script error. I ended up with reinstalling the win7 to get rid of the error. My question is when problem occurred, how to fix the problem. I did try to restore the system with previous created restore points, but none helped. Thanks.
Thanks for the response and your time and effort anemeros. What does mcbuilder do? When is version 0.8 being released? Thanks again, Cutha