Platform 15 Beta 3 (Feb 06, 2018). Please donate.
300+ real apps, *new* Startup Sentinel (Apr 20, 2018)
Over 960 million app downloads
I'm getting this: https://i.imgur.com/ubA3UVm.jpg when I run CPUZ 1.84 Portable. This does NOT happen on CPUZ 1.83 portable. My system is Win7 SP1 64bit
I can run CPU-Z Portable and CPU-Z directly on Windows 7 x64 without issue. You can try running cpuz_x64.exe directly within the CPU-ZPortable\App\CPU-Z directly to ensure it isn't a problem with our launcher. Something could be wrong with your Windows instance, there could be malware infecting files written to TEMP, or something else could be up. But the app itself works on Windows 7 x64 without showing that error here. Once you run the EXE directly and see the same error, you can ask the publisher for additional assistance if you'd like.
Sometimes, the impossible can become possible, if you're awesome!
Hmm, I have to investigate further. Thanks
Can you upload \App\CPU-Z\cpuz_x64.exe to VirusTotal and post back with a link to the info it gives you?
Here's what I got when I uploaded this file from my copy of CPU-Z Portable 1.84:
Note that if you go to the "Details" tab and scroll down it says "Signed file, valid signature" and has the following list of signers: "CPUID", "DigiCert EV Code Signing CA (SHA2)" & "DigiCert".
Do you think it could be related to Spectre (CVE-2017-5715) microcode vulnerabilty in validation page? Could it be because I don't have the Spectre/Meltdown patches installed?
Spectre and meltdown are both vulnerabilities that allow code running in a lower privilege state to view memory that shouldn't be accessible without higher privileges. While technically this could be used, for instance, by malware running under user privileges to capture your administrator password, which might then allow it to elevate itself to run with admin privileges and do more damage, you would already have to have malware on your system, and if it's running already, it wouldn't need admin privileges to infect a Portable App unless you've installed that app in a folder with restricted permissions (e.g. Program Files) which can cause other issues with Portable Apps. Besides, if someone had written malware able to catch your admin password via Spectre, detect CPU-Z and infect it, they'd probably be able to trick Windows into thinking you'd already given it permission to use it, or at least they could detect the window asking for permission and simulate a mouse click.
More likely, you picked up some malware, and it infected CPU-Z hoping that you would give it more privileges.
Deleted CPUZ portable and reinstalled it, so no malware. Same thing. I've contacted CPUZ devs about this issue cause when I install the program from their site I get it too, so it isn't the portable version doing it
My point about malware was that there may be some already on your system that is detecting when you try to run CPU-Z and infecting it (trying to gain higher privileges) before CPU-Z finishes starting up. It may be something else. I don't know. But since it could be caused by malware, I would recommend you scan your system. (I'd use Malwarebytes Anti-Malware.)
I disagree that it is malware, cause using CPUZ 1.83 does NOT result in this issue. Only when using CPUZ 1.84 does it crop up. If I then downgrade back to 1.83 the issue stops. And CPUZ 1.84 loads fine and after about 20 secs it throws that message, I close the message CPUZ continues running and working perfectly fine.
To be 1000% sure, I ran Malware Bytes, came up clean
The only other things I can think of off the top of my head that might cause such an error are if you haven't installed certain updates that let Windows accept digital signatures signed with newer hashing algorithms, or if Windows doesn't trust the certificate because your clock is wrong, and it thinks it's not valid yet/anymore.
There are probably other things that it could be, but I'm not sure what at the moment. Contacting the developers of CPU-Z might be more beneficial. If it's not one of those two issues, then I hope they can help.
Also, when you get it figured out, can you make a point to post back to this thread to let us know how? Then this thread could prove useful to others experiencing the same, or similar issues.
Yep, I'll post what they say if/when they respond. I contacted them several days ago, nearly a week actually, and still haven't heard from them.