image

Fix for Predator Sense failing to open on Windows 10

12346»

FAQ & Answers

  • TheAlb4troZTheAlb4troZ Member Posts: 1 New User
    edited July 2020
    hi guys , i did the C:\Windows\SysWOW64>lodctr /R and run as administrator but my error code is 2. Any help ?
    Edit: i did it again then rebooted , now it works , thanks for help!
  • xapimxapim ACE Posts: 6,163 Pathfinder
    TheAlb4troZ you shouldnt try on safe mode if your getting the same theres something wrong with your windows install


    https://www.userbenchmark.com/UserRun/11532543

    UserBenchmarks: Game 43%, Desk 61%, Work 40%
    CPU: Intel Core i5-7300HQ - 63.5%
    GPU: Nvidia GTX 1050-Ti (Mobile) - 41.9%
    SSD: WDC WDS200T2B0B-00YS70 2TB - 71.4%
    HDD: WD WD10SPZX-00HKTT0 1TB - 93.7%
    RAM: Kingston HyperX DDR4 2666 C15 2x16GB - 76.8%
    MBD: Acer Predator G3-572

    I'm not an Acer employee. (just here to help in the best way i can)
    If my answer fixed you issue please accept it for any other users who search for it would find it quickly thanks :)
    If you want to learn more about undervolting/optimizing windows join the Predator fb group and youtube channel:

    Owner/Admin (HOTEL HERO/Red-Sand/Opoka Opoka)
    https://www.facebook.com/groups/1969145569968592/
    https://www.youtube.com/channel/UCNJwGUHxSJ8FKqAhnOqQuAw
    Acer support:
    https://www.acer.com/ac/en/US/content/service-contact
    http://www.acer.com/worldwide/support/  


  • McDadddyMcDadddy Member Posts: 1 New User
    daydozer said:
    Hey folks,

    I've been irritated by this for a while and tried all the "fixes" in the various forum threads. Im a software engineer so I decide to actually troubleshoot it.

    When launching predator sense I scrubbed the event logs and found failures to reference perfmon counters.



    This indicates that there is an issue with perfcounters in windows. If you see these events immediately after opening predator sense you know you have the same issue.

    To fix this issue, close out of all predator instances in task manager:

    Then open an administrator command prompt.

    For 32bit windows change directories to c:\windows\system32

    For 64bit windows change directories to c:\windows\SysWow64

    Then run the following command to rebuild perfmon counter libraries (this will rebuild both Microsoft and 3rd party counter libraries)

    lodctr /R

    Note it has to be a capital R or you will get an error.

    You should get this result:



     Once that is done you should now be able to run PredatorSense.

    Voila!



    Please let me know if this helps anyone!

    Thanks!

    Thank you soooo much
  • Aman1998Aman1998 Member Posts: 1 New User
    daydozer said:
    Hey folks,

    I've been irritated by this for a while and tried all the "fixes" in the various forum threads. Im a software engineer so I decide to actually troubleshoot it.

    When launching predator sense I scrubbed the event logs and found failures to reference perfmon counters.



    This indicates that there is an issue with perfcounters in windows. If you see these events immediately after opening predator sense you know you have the same issue.

    To fix this issue, close out of all predator instances in task manager:

    Then open an administrator command prompt.

    For 32bit windows change directories to c:\windows\system32

    For 64bit windows change directories to c:\windows\SysWow64

    Then run the following command to rebuild perfmon counter libraries (this will rebuild both Microsoft and 3rd party counter libraries)

    lodctr /R

    Note it has to be a capital R or you will get an error.

    You should get this result:



     Once that is done you should now be able to run PredatorSense.

    Voila!



    Please let me know if this helps anyone!

    Thanks!

    Thank man...it really worked for me.
    Thanks it really worked😁✌️
  • EpicBuntyEpicBunty Member Posts: 25 Troubleshooter
    Hey it worked!! Finally!! Thanks a lot buddy. Also is there any way to resolve all those errors? They just increased!

    And lastly @xapim bruh whats up with your replies are u trolling or what
  • xapimxapim ACE Posts: 6,163 Pathfinder
    EpicBunty ......??? dunno what u mean


    https://www.userbenchmark.com/UserRun/11532543

    UserBenchmarks: Game 43%, Desk 61%, Work 40%
    CPU: Intel Core i5-7300HQ - 63.5%
    GPU: Nvidia GTX 1050-Ti (Mobile) - 41.9%
    SSD: WDC WDS200T2B0B-00YS70 2TB - 71.4%
    HDD: WD WD10SPZX-00HKTT0 1TB - 93.7%
    RAM: Kingston HyperX DDR4 2666 C15 2x16GB - 76.8%
    MBD: Acer Predator G3-572

    I'm not an Acer employee. (just here to help in the best way i can)
    If my answer fixed you issue please accept it for any other users who search for it would find it quickly thanks :)
    If you want to learn more about undervolting/optimizing windows join the Predator fb group and youtube channel:

    Owner/Admin (HOTEL HERO/Red-Sand/Opoka Opoka)
    https://www.facebook.com/groups/1969145569968592/
    https://www.youtube.com/channel/UCNJwGUHxSJ8FKqAhnOqQuAw
    Acer support:
    https://www.acer.com/ac/en/US/content/service-contact
    http://www.acer.com/worldwide/support/  


  • dannynowthendannynowthen Member Posts: 3 New User
    daydozer said:  
    Hey folks,

    I've been irritated by this for a while and tried all the "fixes" in the various forum threads. Im a software engineer so I decide to actually troubleshoot it.

    When launching predator sense I scrubbed the event logs and found failures to reference perfmon counters.



    This indicates that there is an issue with perfcounters in windows. If you see these events immediately after opening predator sense you know you have the same issue.

    To fix this issue, close out of all predator instances in task manager:

    Then open an administrator command prompt.

    For 32bit windows change directories to c:\windows\system32

    For 64bit windows change directories to c:\windows\SysWow64

    Then run the following command to rebuild perfmon counter libraries (this will rebuild both Microsoft and 3rd party counter libraries)

    lodctr /R

    Note it has to be a capital R or you will get an error.

    You should get this result:



     Once that is done you should now be able to run PredatorSense.

    Voila!



    Please let me know if this helps anyone!

    Thanks!

    Hi Daydozer - THANK YOU!! I solved it using your method! Thanks!
    A couple of alterations to your answer did it for me (I'm not a software engineer) so for anyone else of a similar level to me:
    I did all the closing down steps then went to Start, right clicked and opened Windows Powershell (Admin)
    I typed in cd c:\windows\SysWow64
    Then put in lodctr /R
    I got the error message like others have and I just put lodctr /R back in and it all went okay :)
    Clicked on my PredS icon and it started first time.
    Lifesaver!!
This discussion has been closed.

Who's Online620

Akagami029
Akagami029
Athwart
Athwart
Danieltm95
Danieltm95
FREW
FREW
gillis8361
gillis8361
Kevro14
Kevro14
Pelegolas
Pelegolas
+613 Guests

Join in, share your experience!

It looks like you're new here. If you want to get involved, click one of these buttons!

New Here?

So, what are the rules of this place? Check out our Acer Community User Agreement. Register to get all the benefits of being a member! Get social and introduce yourself in our Welcome Forum, or learn about our ACE Program and What's Happening at Acer.

Assistance by Acer


Drivers &
Manuals

Acer
Answers

Get Product Information
( only)

Acer Support
Videos