Diagnose.exe alert with every launch and closure of PiTool?

I’ve recently setup my 8KX VR play space and installed PiTool Version: v1.0.1.266, which seems to be the latest version on the web site (for non-FR). With every launch of PiTool I get a windows security pop-up asking if I want to allow Diagnose.exe to make changes to my computer. It seems a bit janky, especially since the “verified publisher” of this Diagnose.exe executable is some name provided only in Chinese characters…

Is this part of the Pimax Pitool experience? Should it be allowed to run, or not (the headset seems to connect better when it does, but I can’t swear to that). Is there any way to allow it to run (assuming it should) without popping up that security alert?

10 Likes

same here. 202020202

1 Like

Yeah, have the same problem here. Also annoying is the close confirm message for PiTool blocking the shutdown process of Windows.

2 Likes

Diagnose.exe is part of pitool. Not sure though why it is being ran during pitool Launch.

I only get asked about it in Windows Security when I have ran it in Help tab.

Haven’t tested new pitool yet.

I get that from Pitool and Steam on Windows shutdown.

That it used to only be launched from the help tab, probably to get information to help support troubleshoot problems, would seem to indicate that it’s okay to say “No” to the question of allowing it to run or make changes to the system.

It’s unfortunate that stuff like this is still making it through QA (or that people are still recommending running older versions of Pitool)…

It can also be launched if an error comes up.

My Zotac Gpu overclocking software also triggers windows security on every boot as well. Both are safe. I am sure there is a way for the user to get rid of the Windows harrassment on something you know is safe.

Main reason folks are recommending older versions is due to some of the performance changes from versions. I keep moving forward.

Same popup here. When I choose not to give it elevated access, nothing really works (Pi Service does not run in background). Only the PiTool interface (blue and white) shows up. :unamused:

2 Likes

Interesting seems Devs have changed something big. @Alex.liu @pimaxquorra can yous forward this to appropriate department.

3 Likes

I also had the diagnose.exe alerts too.
Also Dirt Rally 1 could not launch into oculus mode directly from pitool anymore. I don’t have oculus home installed and used the suggested LibOVRRT64_1.dll and libOVRRT32_1.dll in the game folder. Via openvr I need to have Parallel reprojections enabled. This is too much of a performance hit on my old gtx970. Now I have reverted back to pitool 260.

2 Likes

Hello,

We will forward this case to the dev team, and try to ask @SweViver to take a look at it.

Sincerely.

2 Likes

Yes same here, it never happened before with previous versions of PiTool that I recall

1 Like

This change seems to be a part of PiTool which Im not in control of.
The Diagnose tool checks for DisplayPort signal strength and other potential issues, and as far as I can tell, the PiTool team has made some changes to the routine. Let me check with Bill and Alex regarding this!

6 Likes

Hi SweViver,

The Diagnose.exe has always trigger UAC when ran from pitool. So it seems they just need to address this part of the pitool suite.

Indeed. Personally I have a bad habit of completely disabling UAC the first thing I do when installing Windows :slight_smile: So I haven’t really seen that UAC is triggered until quite recently on my new build.

2 Likes

I just checked and the prompt for the latest PiTool is actually for PiTool.exe, not Diagnose.exe

2 Likes

Okay this is a very important detail.

1 Like

Is the PiTool still connecting to random Chinese servers and transmitting the user actions?

1 Like

Good Question. That’s why I don’t use PiMaxExperience

You mean you exit and don’t use pitool to launch? And as such do not use PE as it runs on top of pitool.