Eset and Task manager conflict or bug?

[forumwt 19]

Seems app does not see or for some reason can't use GPU anymore, I talk about Premiere Pro.
So solution is only to install windows without Eset for now  And i will do it now because i have no more time to experiment with this, cleary i can see that some problems is with Eset update and that is all what i can say.

[Wrogg 5]

For those of you getting error 2. rebuild on command prompt not Powershell.

Edited May 3, 2022 by Wrogg

[Andrew3000 4]

It happens to me too

[itman 1,659]

Running these four commands from elevated command prompt window did the trick for me:

cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

[Tp6ojNfYgWweHa 2]

Run CMD as administrator, lodctr / R and so far everything looks OK

[cofer123 14]

12 minutes ago, itman said:

Running these four commands from elevated command prompt window did the trick for me:

cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

The question now is whether an ESET update will break it again or, preferably, if a future ESET update will fix this issue for other people that will not realize how to manually fix it.

[New_Style_xd 69]

I will leave my update disabled for a while. I'm afraid mine will have the same problem.

[New_Style_xd 69]

Well I was curious I went to update the eset when the modules were just installed look what happened to my GPU all disappeared.

I found that it was because of the update of the eset modules.

[New_Style_xd 69]

Checked here, the modules that were updated today were:

The problem must be among some of these.

[itman 1,659]

1 hour ago, New_Style_xd said:

I found that it was because of the update of the eset modules.

Good find!

[New_Style_xd 69]

All that's left for me now is to wait for ESET to fix this problem.
will it take too long?
I'm afraid of losing performance on my machine since I use a lot of GPU.

[New_Style_xd 69]

I'm doing a test using a sandbox to increase the use of the GPU and the processor and HD.
As the image below shows that the GPU does not go beyond 0%. before updating ESET the GPU will do its part of the processing.
What I noticed is that now I don't have any help from the GPU because the ESET update removed the GPU as I said in the comments above.
What will be the solution that eset will give for the GPU to work again. because all this happened after recent updates.

[Tonyset 4]

Hello all, even I had noticed the same problem, I solved with the

"Rebuild the counters "

Quote

cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

regards

[New_Style_xd 69]

14 minutos atrás, Tonyset disse:

Olá a todos, até eu tinha notado ou mesmo problema, resolvi com o

"Rebuild os contadores"

consideraa

I'll wait for a fix from ESET, because I don't like to do pale stuff. It could be a problem in the near future.
But thanks for your help, I'll be waiting for ESET to fix it.

Edited May 4, 2022 by New_Style_xd

[cofer123 14]

7 hours ago, New_Style_xd said:

I'll wait for a fix from ESET, because I don't like to do pale stuff. It could be a problem in the near future.
But thanks for your help, I'll be waiting for ESET to fix it.

A fix would be nice. An acknowledgement that the issue exists would be even nicer.

[peteyt 393]

25 minutes ago, cofer123 said:

A fix would be nice. An acknowledgement that the issue exists would be even nicer.

It does appear that the issue is related to eset @Marcos

[xxJackxx 85]

I am not having this problem so it is probably more complicated than them just claiming responsibility and/or releasing a fix.  ESET products may well be a factor but not the only one.

[URBAN0 14]

15 hours ago, New_Style_xd said:

Well I was curious I went to update the eset when the modules were just installed look what happened to my GPU all disappeared.

I found that it was because of the update of the eset modules.

Yes I  just know this the same thing on 3 of my systems.

Edited May 4, 2022 by URBAN0

[AnthonyQ 48]

Just checked, I have the same issue. GPU is missing in Task Manager. I have not experienced this problem previously when I used other AVs.

This problem is critical and needs immediate attention from the development team.

[Marcos 5,074]

8 minutes ago, AnthonyQ said:

This problem is critical and needs immediate attention from the development team.

You can run " lodctr /R" as an administrator twice, just in case, to get it fixed while the issue is being investigated.

[AnthonyQ 48]

17 minutes ago, Marcos said:

You can run " lodctr /R" as an administrator twice, just in case, to get it fixed while the issue is being investigated.

I run it just once and it works. 🙂 Nonetheless, a fix is urgently needed. 

[facingthesea 0]

Same problem here😑

 

[Marcos 5,074]

Let us know please should the issue recur after being fixed by running "lodctr /R".

[New_Style_xd 69]

3 hours ago, cofer123 said:

A fix would be nice. An acknowledgement that the issue exists would be even nicer.

What you say I completely agree with.
Imagine these commands that are asking us all to put ourselves and see how it turned out.

I don't agree with this, because imagine several clients that I do maintenance on their computers and I recommend ESET's AV to my clients. everyone with a problem will I have to go to each one's house and use this command?

this is absurd and unrealistic. the fix has to come from ESET to solve the problems all at once

[New_Style_xd 69]

When eset solves this problem, please let me know here on the forum, thanks

Edited May 4, 2022 by New_Style_xd