Author Topic: Error at hooking API "NtProtectVirtualMemory" so cannot update Tweaking.com  (Read 16668 times)

0 Members and 1 Guest are viewing this topic.

Offline dgcabz

  • Newbie
  • *
  • Join Date: Aug 2016
  • Posts: 7
  • Karma: 0
    • View Profile
Trying this again. I have had this problem since August and my previous request for help looks like it has been archived. I cannot update Tweaking.com v3.9.0.4. I have tried with versions 0.5 to 0.12. 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 (version 3.9.0.4) to repair but nothing has worked. The error message I receive after updating which I am always told is "successful", is "Error at hooking API 'NtProtectVirtualMemory' Dumping first 32 bytes". Please see screenshot with the rest of the numbers it gives me in case this is helpful. Version 3.9.0.4 works perfectly okay so I have reverted back to this for now and without updating. On uninstalling the newer versions I have tried, I see the same error message despite it stating "uninstall successful". Thanks.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
I've passed this onto Shane.

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
The program exe is protected, so if there are any debuggers running it can cause that error. Also if your system files are messed up that can happen as the protection is calling a windows API.

Have you ran system file checker on your system yet?

Shane

Offline dgcabz

  • Newbie
  • *
  • Join Date: Aug 2016
  • Posts: 7
  • Karma: 0
    • View Profile
Thanks Shane. I ran System File Checker but it did not solve the problem. I am not aware of any debuggers running but I will look into this in more detail.