EVictory

I have been waiting for multiple days for a response to my post. Can you offer any help as to why Privacy is blocking all local network access? I just confirmed before writing this latest post that the problem still exists. If Privacy is turned ON, I cannot access the local LAN subnet. With Privacy OFF, everything is accessible.

192.168.200.0/24 The entire local subnet. I have numerous home automation in static IPs (192.168.200.20, 192.168.200.21, 192.168.200.22, 192.168.200.23, 192.168.200.24, 192.168.200.25, 192.168.200.26, 192.168.200.27, 192.168.200.28, 192.168.200.29, 192.168.200.30, etc.). I have an active directory server setup on 192.168.200.10. This server has multiple shared folders available to clients. Several of these folder shares are mapped to drive letters on my home computers. With the Privacy VPN turned ON, I cannot access any of the folder shares nor any of the home automation device's web portals. I also cannot PING any of these IPs either. If I turn the Privacy VPN OFF, I can then access all folder shares and access all home automation devices. Is there a whitelist in Privacy? -Emile

Sorry, I have been unavailable for a few days. Attached is the logs zip file. -Emile mbst-grab-results.zip

Yes

I have noticed lately that anytime Malwarebytes Privacy is ON, I cannot access resources on my local network. I have several drive maps that do not work when privacy is ON. Also, I cannot access my home automation equipment via its local IP addresses. This is a show stopper for me. If I cannot have access to my local network available, I will NOT be able to use Privacy. Is there anyway to open local network traffic with Privacy ON?

All, After searching the Internet regarding this software, I found multiple reports of the installer being reported as infected from other anti-virus vendors. The reports seem to indicate that this company's free installers contained infections but that the paid software, once installed, was clean. I have been using this software for about a year now. Before purchasing it, I tried the free version. The infected file is the installer for the trial version as the paid installer has a different filename. There was another EXE installer in the same folder that appeared to be the 32-bit version. This second EXE was not infected. I deleted both of these installer files. I have a local repository where I store the installation files of software I purchase. I have booth the 'free' version and the 'paid' version installers of PowerISO stored there. It turns out that the free version installers on my NAS are infected. I deleted them. My finding is consistent with the Internet search results above. Thanks for all the help. -Emile

PowerISO7-x64.zipCli, Sorry, I just read the instructions more fully. I zipped the detected EXE file and have uploaded it here. -Emile

Cli, I have ran the Support Tool and sent the resulting zip file via reply email. The email asked that I 'attach the detected file'. However, the detected file is an EXE file which means I cannot attach it to an email nor can I upload in this forum. How do I send you the detected EXE file? -Emile

Attached is the Scan Report where poweriso7-x64.exe was detected as suspicious. The.log

My first Malwarebytes Premium scan detected the file C:\USERS\XXXXX\APPDATA\ROAMING\POWERISO\UPGRADE\POWERISO7-X64.EXE as Generic.Malware/Suspicious. I believe this file is part of the PowerISO software that I have purchased and installed on my computer. This program is all about working with ISO files (creating them, burning them to DVD, USB Flash Drive, etc. How do I tell if this file is truly infected or ai false-positive? -Emile