Error at hooking API message when updating v3.9.0.4 Pro

[dgcabz]

I cannot update Tweaking.com v3.9.0.4. I have tried with v0.5, 0.6 and now 0.7. I have the Pro version. I am on Windows 7 Home Premium. I have tried uninstalling/reinstalling, turning off Norton, in safe mode (which worked temporarily until my PC went back to normal mode), even using Tweaking.com to repair but nothing has worked. The error message I receive after updating which I am told is "successful" and then opening Tweaking.com is "Error at hooking API 'NtProtectVirtualMemory' Dumping first 32 bytes. Please see screenshot with the rest of the numbers it gives me. Version 3.9.0.4 works perfectly okay so sticking with this for now without updating. Thanks.

[dgcabz]

...and it doesn't update with version 3.9.0.9 either. Attached is the screenshot of the error message.

[Boggin]

I've passed this onto Shane - waiting for a reply.

[Julian]

Have you tried uninstalling then doing a reinstall? If you back up your settings. Config file you should have all your previous settings let me know 

[dgcabz]

Yes, I have tried this several times now with each new update. I have also uninstalled v3.9.0.4 and installed each newer version manually as they have been released. I still get the same error message making the newer version(s) of Tweaking.com unusable. On reinstalling version 3.9.0.4 Pro it still works fine on my PC and without the error message. I have been using Tweaking.com for years and never encountered any problems. I am beginning to wonder if it is my PC rather than the programme itself.

[dgcabz]

Sorry Julian - forgot to say, and in case it helps, I also see the "Error at hooking API 'NtProtectVirtualMemory' Dumping first 32 bytes" message when uninstalling each of the versions post v3.9.0.4 (i.e. from version .5 - .9) after trying to see if a newer version update fixes the issue. I am back to version 3.9.0.4 which works fine and without the error messages on an install and an uninstall. Many thanks.

David

[dgcabz]

....and still getting the same error when updating to version 3.9.10 today. Error message attached. Back to version 3.9.0.4 which is working.

[Boggin]

I've given Shane a Bump about this as still waiting for a reply from my earlier email to him about your problem.