Windows Migration Notes

PingPlotter 5 does more for you and asks less from you, but some aspects of the tool operate differently than previous versions. Significant differences are explained here to help you get up to speed as fast as possible.

FeaturePrevious VersionsVersion 5+
Alerts Complex single page alert setup in the options menu. Setup in the options menu. Management happens through a separate window. Alerts presented in the context of the target they are applied to. Management integrated with control panel. More...
Running as a service Service interaction required Session 0. Manual configuration is necessary for operation. Session 0 connection not required. Configuration happens automatically during install process if option is selected. More...
Auto-saving data Memory management is required. Necessary to configure auto-save intervals. Auto-saving happens automatically. Options are available to specify what gets auto-saved. More...
Target bar Includes all the right functionality. Design could be easier on the eyes. Controls are pleasantly arranged. Redundant information is removed. More...
Workspaces Explicitly choose when to operate in a workspace. A default workspace is always running. Additional workspaces can be set up at-will. More...

Moving to Version 5

You can install PingPlotter 5 on the same machine as an older version. Running both versions side-by-side gives you a chance to evaluate the new version without compromising your existing operation. If you find a barrier preventing full Version 5 adoption, please tell us about it. The program is constantly improving and your feedback helps prioritize development.

Migration Assistant

If Version 4 is installed on your machine, the migration assistant launches the first time you start Version 5. It checks your Version 4 settings and presents a report about what will and what won't migrate. Click Import Now to move the settings into Version 5. If you choose not to import, you can launch the migration assistant at any time through the Migration menu option. To remove the migration option, uninstall any pre-V5 versions of PingPlotter.

Known Issues


The majority of alert functionality from previous version is available but, issues related to launching .exe's, email send frequency, MOS conditions, and logging to file exist in Version 5.

The "Launch an executable" alert action is available and supported on V5, but has some security implications that need to be considered. Because of this, we've moved this action to an extension that works in both PingPlotter Standard and Pro. To get this extension, visit the extensions page.

The MOS alert condition is not yet supported. If you rely on this, please let us know.

The email alert had "max email frequency in minutes" and "how many minutes to wait before sending" options. These were legacy options that predated the "when alert conditions start (and end)", which are better for this purpose.

Log file event action is way different and will display a migration warning saying that it migrated but is broken and need manually fixed. The current "Log To File" alert supports only a small list of variables - please contact us if you rely on this alert and find the V5 one inadequate after testing it.


Version 5's migration assistant imports version 4 workspaces but not version 3 workspaces.

Version 3 workspaces don't import directly to V5. Version 4 workspaces should import to V5 easily and well. If you're still using PingPlotter 3, though, and need to import your workspace to V5, please install V4 and import it, then save and load that in V5.


All packet types except "UDP target port" are supported in version 5. Advanced packet cargo options are not supported in this version, and TCP packets may experience WinPcap related issues in Windows 10.

Changing packet types on named configurations beyond the first one might cause some control alignment problems. Close / reopen the options dialog after adding a named configuration (or changing packet type) to work around this problem.

The seldom-used "UDP target port" packet type is not currently supported in V5. You can target your Unix-style packets more deliberately in V5 than in V4, but not in a way that looks for an explicit response. If you rely on this packet type, please let us know what protocol you're using so we prioritize appropriately.

If you're using TCP packets, be aware that WinPcap is marginally compatible with Windows 10. This is not a PingPlotter-specific issue. See our knowledge base for detail on potential solutions.

The advanced packet cargo -> file option is not supported. Variables in the advanced cargo option -> string value are not supported (even though the settings are stored there). We will be addressing this soon.


Scripts for previous versions are not ported to v5 yet. The migration assistant does not import template variables.

Scripting support is partially implemented, but the available scripts have not been ported to V5. The migration assistant will notify you which ones you're using that we don't support. See our extensions page for more details.

Template variables are completely different in V5, and haven't made their way into every piece of PingPlotter. See the manual's variable substitution page for more details.

Route changes

Route changes can be tracked by double-clicking the time-graph or with the new auto focus mode. Route change masks are not supported in this version. details...

The appropriate route is always visible when you specifically focus on a time period by double-clicking the time-graph (or if you use the new sweet Focus: Auto mode). We don't yet have a way to merge routes, exclude route changes you don't care to see, or to see a list of all the route changes. Better route change management is still on the way.

Route changes are handled quite differently in V5, and we're not quite all the way to the final state yet. The V4 route masks are not supported in V5, and are not imported.

Web interface

Version 5's web interface covers core functionality, but some features from previous versions are unavailable. details...

The web interface is not quite as good as the PingPlotter 4 one (although it's better in some ways, too). We recommend installing as a service if you're interested in using the web interface.

The login screen uses basic authentication (and the related popup login) rather than a cookie-based login like PingPlotter 4.

The port needs to be added to the allowed list by and administrative user. We strongly suggest running as a Windows Service if you're using the web interface - if you do that, it should "just work" with whatever port you pick.

If you're not running as a service, you'll have to adjust some permissions to get this working. To adjust permissions, launch a command prompt as an administrator and enter:
netsh http add urlacl url=http://+:7464/ user=%USERNAME% listen=yes
Adjust the port and username as appropriate for your needs.

If you've customized your web interface by editing the .asp or .js files in PingPlotter 4, the PingPlotter 5 one has different capabilities and implementation - your changes probably won't port over.

If you're using IIS for a web server, PingPlotter 5 does not yet support IIS. We will be improving this and adding documentation and capabilites to allow SSL and other industrial strength capabilities.


A handful of issues related to other features exist in Version 5. details...

Sharing of collected data and screenshots through the "Send email" menu option is not available. A more robust option is currently in the works, but for now, the best way to accomplish the goal is exporting images or .pp2 files and manually attaching to an email.

Auto-save has been completely re-imagined in PingPlotter 5. See the manual page for more details.

Whois Lookups not yet working. We're hoping to make this more useful in v5 than v4.

There is currently no way to have PingPlotter V5 auto-save images. If you're using an automated system that uses auto-save images, there are some options here in the current version, but we will be adding more parity with V4 shortly on this feature.

Sending data or target from MultiPing does not yet work.