I can confirm that v5.61-3293 Beta has no issue on my system.
Unzipped the file and ran the executable after overwriting the INI file with my usual settings.
See result in attached file.
Thanks Martin once again :shy:
Mmh ok, maybe other people are getting false vulnerable reports for other reasons. But that's a good amount of users tho...
I'm wondering why, in first place, a Detection tool need to have an exclusive access to communicate with IME and work properly.
Ah, this would be nice of course...
Exactly this, thanks for your confirmation!
There actually is a warning when you use the FWUpdate tool, about "closing any other programs"... And being an update it's understandable.
But there isn't anything similar when launching the Detection Tool.
So lots of users using software for...
I'm not sure this is a bug, but this seems the appropriate section to post in.
It might be useful to other users and to Martin himself.
My setup-related info:
- Windows 10 EDU 1709 Build 16299.19
- Asus ROG Maximus IX Formula
- Intel 7700k
- HWiNFO64 v5.60
Some days ago Intel...
Hello Martin, thanks for your reply :)
Good guess, that's partially true.
I have solved my problem, at least regarding the HWiNFO part. Here what I've done:
as I wrote in my previous post, I have other scheduled tasks working fine on login.
And, since you have confirmed me that HWiNFO is...
I am using:
- Windows 10, Version 1607, build 14393.82
- HWiNFO64, Version 5.34, build 2930
Some days ago I edited TimeBroker service start type (using regedit), as follows:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc] "Start"=dword:00000003 (Manual)...