Windows 10, latest updates. Run PRTG Network Monitor installer as administrator (downloaded today). Setup gets to "Updating Windows Firewall Settings" and opens a cmd window to netsh.exe Nothing further happens. Malwarebytes and Windows Defender are running, but neither is being activated by the installer. Whitelisted PRTG Administrator.exe Ran a malware/virus scan. All good. Waited about an hour, ended the Setup/Uninstall task and closed the netsh window. Now cannot uninstall, either. Gets to the same point and opens netsh.exe and stops. Deleted all the PRTG folders and files. Tried again. Same results. Thank you
Article Comments
I don't know the difference. I don't have access to the other computers without signing in for access to folders/files and just used "run as administrator" to install PRTG, so I suppose that makes me a local administrator.
At this point, the PRTG software looks like more than I wanted and can grasp ... I just wanted to monitor the traffic on my cable modem and router graphically to show what was bothering my network recently (sudden slowdowns and data drops, for example). I have a small home network (three computers, a tablet, three phones, two printers, three Roku devices, a LaCrosse weather station with five sensors).
Since this is far more than I need, can you tell me how to uninstall it? The uninstall gets 'stuck' in the same place as the install (at "Updating Windows Firewall Settings" with the command prompt netsh.exe with no activity showing and no response to the keyboard by the console).
I'm very reluctant to restart my computer with a failed installation, so a hand-removal solution would be welcome (what to delete and what registry entries to remove).
Thank you, Dennis
Dennis
May, 2020 - Permalink
Hi Dennis,
I'm sorry to hear that your experience was unfulfilled. If you want to uninstall PRTG, please check this article to receive all places where PRTG stores data: https://helpdesk.paessler.com/en/support/solutions/articles/7600006351163-how-and-where-does-prtg-store-its-data
May, 2020 - Permalink
Hi there,
Was the used user a "normal" administrator or the local administrator? If you tried it with a normal admin, please try again with the local administrator.
May, 2020 - Permalink