Jump to content

Emsisoft behaviour blocker problem with hwinfo64


Da Phu
 Share

Recommended Posts

I a problem with HWInfo64 V5.84-3450. The problem is Emsisoft Behavior Blocker have some issue with HWInfo64 that caused the software to lag when it is minimized and closed. Excluding HWInfo64 from monitoring fixed all the lag from minimizing and closing. 

Another similar thread created in 2016: 

 

Link to comment
Share on other sites

4 hours ago, SumTingWong said:

Log sent via PM. 

I've looked over the log, and I don't see any obvious reason for the issue. I'll take a look and see if I can reproduce the issue in a test environment.

 

1 minute ago, SumTingWong said:

Official site: https://www.hwinfo.com

Official download site: https://www.hwinfo.com/download.php

OK, thank you.

Link to comment
Share on other sites

It is slower to minimize when not excluded from EAM, however in my test setup the difference in time it takes to minimize is only a second or two. I don't think I noticed it being slow to close, but it's possible the difference between excluded and not excluded wasn't enough for me to notice it.

Do you launch it in "Sensors only" mode, or have you changed any of the default settings for HWinfo? Did you install it, or use the portable version?

Link to comment
Share on other sites

30 minutes ago, GT500 said:

It is slower to minimize when not excluded from EAM, however in my test setup the difference in time it takes to minimize is only a second or two. I don't think I noticed it being slow to close, but it's possible the difference between excluded and not excluded wasn't enough for me to notice it.

Do you launch it in "Sensors only" mode, or have you changed any of the default settings for HWinfo? Did you install it, or use the portable version?

It feels like 5 to 10 seconds delayed when it is minimized and closed. I launched it with sensors only, default settings, and no portable version. I think there's something in the real time monitoring interfered HWInfo64, and I think there could be more interfered as well. 

Link to comment
Share on other sites

On 6/13/2018 at 8:15 PM, GT500 said:

It is slower to minimize when not excluded from EAM, however in my test setup the difference in time it takes to minimize is only a second or two. I don't think I noticed it being slow to close, but it's possible the difference between excluded and not excluded wasn't enough for me to notice it.

Do you launch it in "Sensors only" mode, or have you changed any of the default settings for HWinfo? Did you install it, or use the portable version?

Hey, I am back. Do I have to add HWInfo64 into exclusion permanently? 

Link to comment
Share on other sites

On 6/13/2018 at 8:31 PM, SumTingWong said:

I think there's something in the real time monitoring interfered HWInfo64, and I think there could be more interfered as well.

It's probably just not responding well to our hooking method (some programs have issue with other applications injecting code into them).

I just tested again, and the delay is only 2 seconds for me when minimizing or closing HWinfo without exclusions. Possibly because there's nothing else on the test system (just drivers and a few web browsers).

 

20 hours ago, Jerky McDilerino said:

Do I have to add HWInfo64 into exclusion permanently?

I recommend doing that for now. If it's the same issue that MPC-HC has, then it won't be easy to fix, however I will let QA know so that they can look into it.

Link to comment
Share on other sites

On 6/15/2018 at 6:42 PM, GT500 said:

It's probably just not responding well to our hooking method (some programs have issue with other applications injecting code into them).

I just tested again, and the delay is only 2 seconds for me when minimizing or closing HWinfo without exclusions. Possibly because there's nothing else on the test system (just drivers and a few web browsers).

 

I recommend doing that for now. If it's the same issue that MPC-HC has, then it won't be easy to fix, however I will let QA know so that they can look into it.

Okay. Any update from the QA team? 

Link to comment
Share on other sites

On 6/18/2018 at 10:17 PM, GT500 said:

I've been told that for now the recommended way to work around the issue is to exclude HWinfo64. It's easy to reproduce, so if we need any debug information we should be able to generate it internally.

Are they still working on fixing the issue with HWInfo64? 

Link to comment
Share on other sites

11 hours ago, Jerky McDilerino said:

Are they still working on fixing the issue with HWInfo64?

They didn't specifically say, however I got the impression that it will be a difficult issue to fix, and it might take a while for them to do so.

Link to comment
Share on other sites

On 6/20/2018 at 7:01 PM, GT500 said:

They didn't specifically say, however I got the impression that it will be a difficult issue to fix, and it might take a while for them to do so.

Oh okay. Any updates regarding to this issue? 

Link to comment
Share on other sites

Our developers don't usually tell me when issues are fixed, unless it's something the QA team can't test themselves, so I most likely won't know to contact you.

We do have a blog feed for beta updates if you'd like to monitor it:
https://blog.emsisoft.com/en/category/emsisoft-news/beta-updates/

And there's an RSS feed for it as well:
https://blog.emsisoft.com/en/category/emsisoft-news/beta-updates/feed/

And then there's one for general product updates (most stable updates, but sometimes betas as well):
https://blog.emsisoft.com/en/category/emsisoft-news/product-updates/

And it has its own RSS feed:
https://blog.emsisoft.com/en/category/emsisoft-news/product-updates/feed/

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...