I recently installed the latest version of Speccy (v1.33). As soon as I start to use the program my Windows 7 starts complaining and generates an error / starts complaining that the driver called “cpuz158_x64.sys” is not “digitally signed”. And that the driver is not installed. Surprisingly Speccy seems to function well after this. Or can Speccy function without this dirver ? Don’t know what to make of it.
We have seen similar before with Win 11 and cpu###_64.sys, but I think that yours is the first report with Win 7.
One suggestion was that if the memory integrity feature of Windows 11 Pro is turned on then it can prevent the unsigned cpu###_64.sys from being loaded.
I suspect that something similar may be happening with Win7, always remembering that Win7 is no longer supported so odd things may start to happen with it now.
Previously when that loading error occured it would crash Speccy altogether, so it looks like that may have been worked around now.
As for if it will affect the functioning of Speccy I’m not sure.
Speccy is obviously trying to load it for a reason, so if it can’t then some of the information it would normally display for your system may not be shown.
Have you noticed anything missing that you would expect to be shown?
Is this a driver installed by Speccy or does it come from Windows itself ?
The driver is placed in the folder "c:\windows\temp" and then the error shows up. The name of the driver is “CPUz158_x64.sys” (see also above).
What is this driver supposed to do ? (if this comes with Speccy) Does Speccy need & install a driver like this ?
Np, as far as I can see there is no (visible) change in the GUI of the program. All information seems to be as it should be. I’ll see if this may change in the (near) future but up to now all seems to be OK. Not even an additional error.
Don’t know what to make of it.
It is part of “Cpuz” a utility that reads some of the system information for your machine.
It seems that Speccy is also using it if it can do so, but if not then Speccy will query Windows itself.
I suspect that the cpuz###.sys file may be included as part of the Speccy installl nowadays.
(I can’t say for sure because I have had Cpu-z on my machine at various times as well as Speccy so I could have got it from then).
Companies do share code and files.
As do most programmers/coders, there is a lot of already written stuff posted out there that you can re-use in your own programming.
Particularly if they are part of the Gen Digital group now then segments of their code and even full utility files can end up being used by Piriform/CCleaner products.
After all why write a new bunch of new coding if someone has already done it and will share?
What can the developers of Speccy say about CPUZ and how the program is being used ? Is this pulled in REAL TIME from that website or is it included in the installation package ? Perhaps a newer version of CPUZ doesn’t cause an error ?
Was this version also included in the previous version of Speccy ? Using that version no error ever was generated.
This also could be related to the fact that I very recently re-installed Windows 7. I regularly re-install Windows to get rid of A LOT OF “clutter” in the Windows registry. I still can try a few things. E.g. run Tweaking’s Windows Repair.
Is there a difference in the way the different versions of Windows check for, check the digital signatures and install the driver (for Speccy ?).