The URL describes the signing policy up to Windows 1803. Radar.exe contains device drivers embedded as resources (those would need to be signed and they are not the type of drivers that would meet the stringent requirements of the current signing process). The chances of getting the drivers signed is close to zero. in windows 1903, there is nothing in the list. The following screenshot is the radar.exe working well status. I uploaded the application to dropbox, and this is the virus scan result ( ) Or I am not sure if I can re-sign it by myself to make it workable in windows 10 1903 I wonder if we can set exception just for this tool, radar.exe. However, the changes will apply to all windows applications, which is unsecured. Some threads shared that using "bcdedit -set TESTSIGNING ON/OFF" or "bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS/DDISABLE_INTEGRITY_CHECKS" to disable the signature. I got some information that the driver of the tool was obsoleted and windows applied more powerful Somebody used the same tool and met the same issue. The company of the tool was corrupted 3 years ago, and there has no update for 3 years. It can't show the network traffic data any more. Now my windows was forced to update from 1709 to 1903 two week ago even if I don't want to do that, the tool failed to work from that time. It worked very well on my windows 10 version 1709. I always used a tool named radar.exe which is used to monitor network traffic for every single process.
0 Comments
Leave a Reply. |