Avast blocks hardwareproviders.sys even thought i made an exeption?

[Digit4lSpace]

and stuff

[Sergio]

Yes, some anti-viruses are false positives because of the specific method used to get the temperature of the processor. Could you please send me a screenshot (for example upload it here https://imgur.com/) of the antivirus message. Maybe it can help make me a request to Avast to exclude false positives.

It's hard for me to tell you any specific actions regarding Avast, because I have not used it. But try adding these folders as an exceptions:
1) C:\Program Files\fpsVR
2) \steam\steamapps\common\fpsVR\CPU Temperature
The second folder (where fpsVR is installed) uses these files as a source for copying to the first folder (where the work files of the service that polls the temperature of the processor are located)
Maybe this will help:
https://wiki.nus.edu.sg/display/DA/Add+folder+exclusion+-+Avast+Antivirus

[Sergio]

It looks just like this one
https://www.reddit.com/r/SignalRGB/comments/119fbbh/installed_tried_to_run_slapped_down_by_avast/
hardwareproviders.sys is same driver as winring0x64.sys mentioned in topic by this link

I will try to get in touch with Avast.

To add to the exception did you make a change in the settings exactly what is written in this window? ("turn off vulnerable drivers blocking in Settings")

[Ēarendel]

Sus. This did not happen before latest update.

[Ēarendel]

I will not make this change to allow vulnerable drivers uploading into kernel memory, it might expose to other threats at the expense of this item.

[Sergio]

There does seem to be a vulnerability in the driver that Avast didn't notice before.
I got a reply from Avast and it seems that thanks to this there is hope that I will make a fix that will remove this problem. Give me a few days and I will make a test version of an update that will probably fix it.

[Digit4lSpace]

Originally posted by Sergio:

There does seem to be a vulnerability in the driver that Avast didn't notice before.
I got a reply from Avast and it seems that thanks to this there is hope that I will make a fix that will remove this problem. Give me a few days and I will make a test version of an update that will probably fix it.

Great!

[Sergio]

Originally posted by DigitalSpace:

Originally posted by Sergio:

There does seem to be a vulnerability in the driver that Avast didn't notice before.
I got a reply from Avast and it seems that thanks to this there is hope that I will make a fix that will remove this problem. Give me a few days and I will make a test version of an update that will probably fix it.

Great!

Test update added as a beta "testing" branch:
1. Right click fpsVR in the list in your Games Library
2. Go to Properties
3. Go to Betas tab
4. Pick "testing" in the first drop-down menu.

If there is no such branch, wait or restart Steam, it will appear eventually.

After installing the update, when you start fpsVR, Steam must reinstall the fpsVR service which polls the CPU, so Steam may started fpsVR with a delay, and may also ask for an elevated rights (but it may not be).

Please let me know the result.

[Digit4lSpace]

Originally posted by Sergio:

Originally posted by DigitalSpace:

Great!

Test update added as a beta "testing" branch:
1. Right click fpsVR in the list in your Games Library
2. Go to Properties
3. Go to Betas tab
4. Pick "testing" in the first drop-down menu.

If there is no such branch, wait or restart Steam, it will appear eventually.

After installing the update, when you start fpsVR, Steam must reinstall the fpsVR service which polls the CPU, so Steam may started fpsVR with a delay, and may also ask for an elevated rights (but it may not be).

Please let me know the result.

Still getting the warning :/

[Sergio]

Originally posted by DigitalSpace:

Still getting the warning :/

Yes, I'm already aware of it, another person informed me.
I will try to contact Avast support again. I'll let you know when there is an update.

[Digit4lSpace]

Originally posted by Sergio:

Originally posted by DigitalSpace:

Still getting the warning :/

Yes, I'm already aware of it, another person informed me.
I will try to contact Avast support again. I'll let you know when there is an update.

thank you for being so active in the discussions btw xD

[Sergio]

The situation is this:
potentially the driver yes has a vulnerability, but fpsVR closed it before and closes it now via access rights already after the driver is launched, which means the vulnerability exists for about 1ms or less, it is impossible to use as vulnerability.
Avast just intercepts the driver installation and startup calls, so it sees that the permissions are empty and thinks quite logically that there is a vulnerability. And kill it before fpsVR changes permissions.
And in short I can't fix it now how it should be done. I need to write a new kernel-mode driver, and it's not easy, and a lot of other stuff.
BUT
I'll fix it in a different way, I think for now so that if the driver because of anitivirus failed to run three times (That is, the message from the antivirus will appear three times, to give the user to decide whether or not he wants to add exceptions, and if he did not understand that it was, all right then it's fine), then after this fpsvr will not try run this driver at all and will not be this message from the antivirus.
What do you think? Would you be satisfied with that solution? (Yes the CPU temperature of fpsVR will not display)

[Digit4lSpace]

Originally posted by Sergio:

The situation is this:
potentially the driver yes has a vulnerability, but fpsVR closed it before and closes it now via access rights already after the driver is launched, which means the vulnerability exists for about 1ms or less, which is fantastic to use.
Avast just intercepts the driver installation and startup calls, so it sees that the permissions are empty and thinks quite logically that there is a vulnerability. And kill it before fpsVR changes permissions.
And in short I can't fix it now how it should be done. I need to write a new kernel-mode driver, and it's not easy, and a lot of other stuff.
BUT
I'll fix it in a different way, I think for now so that if the driver because of anitivirus failed to run three times (That is, the message from the antivirus will appear three times, to give the user to decide whether or not he wants to add exceptions, and if he did not understand that it was, all right then it's fine), then after this fpsvr will not try run this driver at all and will not be this message from the antivirus.
What do you think? Would you be satisfied with that solution? (Yes the CPU temperature of fpsVR will not display)

I don't mind if just a single thing is gone, i only really care about the fps of the game i'm playing in vr which has worked perfectly.

[Sergio]

On the "testing" branch posted a version in which after two attempts the third time fpsVR will not try to start the CPU polling service.

Update: Also already in beta
https://steamcommunity.com/games/908520/announcements/detail/3644012994605683472?l=en

Update 2: Released in main branch
https://steamcommunity.com/games/908520/announcements/detail/3645139528235509542

[Digit4lSpace]

Originally posted by Sergio:

On the "testing" branch posted a version in which after two attempts the third time fpsVR will not try to start the CPU polling service.

Update: Also already in beta
https://steamcommunity.com/games/908520/announcements/detail/3644012994605683472?l=en

Update 2: Released in main branch
https://steamcommunity.com/games/908520/announcements/detail/3645139528235509542

i am now on the regular branch and i haven't seen any warnings since like april

[Digit4lSpace]

or my bad, since the update 2 lol