Windows virus and threat protection blocking qspy.exe

[KJC]

Has anyone experienced this problem and if so, how have you resolved it?
Windows 10, version 22H2 x64 Base Systems 2022-10

[Quantum Leaps]

The issue has been already reported and has been (hopefully) resolved. The Microsoft Threat Protection issues the diagnostics:

This program provides remote access to the computer it is installed on.

The qspy.exe executable has been created with the same MinGW compiler that ships in the QTools collection for Windows. The complete source code for qspy is provided (directory qtools\qspy) and anybody can build the qspy.exe executable from sources on their local machine (directory qtools\qspy\win32).

Microsoft Threat Protection apparently does not like the non-Microsoft executable that accesses the network. The resolution that seems to make the Microsoft Threat Protection happy is to build qspy.exe with the Microsoft Visual Studio (2022 Community Edition was actually used).

The QP-bundle for Windows 7.3.0a has been updated to include the executables generated with VS 2022 (qspy.exe, qclean.exe, and qfsgen.exe). Also, the QTools release 7.3.0 on GitHub has been updated to include the "clean" executables.

Please download the updated Windows installer (qp-windows_7.3.0a.exe) and re-install it. (The recommended procedure is to first uninstall the pervious version and then cleanly install the new one). Please report to this discussion forum if you still experience any problems.

--MMS

[KJC]

Miro, Thanks for the explanation and it all makes sense.

[KJC]

Miro,

We have recompiled the QSPY program using your project file from qtools and cannot get it to connect to a COM Port. We used the community version of MSVS on a Windows 10 machine. The error we get when connecting to a port is shown below. Also, we have tried the POSIX version and also cannot get it to connect to a port. Do you have any suggestions?

thanks

[Harry Rostovtsev]

Not sure this is the issue but have you tried capitalizing "COM15" (instead of com15)? I've never tried using lowercase for comports.

[KJC]

It produces the same result.

The standard out of box build works with both.

[KJC]

It produces the same result.

The standard out of box build works with both.

[Quantum Leaps]

Hi KJC,
Typically, QSPY generates the <COMMS> error... message when another instance of QSPY is already running on the same machine. Please check (e.g., in the Windows Task Manager).

Also, could you check your locally built qspy.exe with VirusTotal.com?
--MMS

[KJC]

We managed to get the qspy application allowed by Microsoft defender. Also, I'll look into the instance issue. thx