New Question
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Download >>


What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more


Top Tags

View all Tags

Updating from Version 7, 8, 9, or 12? Read this important message!



Your Vote:



There are some important things to consider when you update from versions 7, 8, 9 and 12 to the latest PRTG version. Please see below.

auto-update prtg prtg12 prtg9 update

Created on May 9, 2012 9:20:19 AM by  Dirk Paessler [Founder Paessler AG] (10,848) 3 4

Last change on Jun 17, 2016 11:57:22 AM by  Gerald Schoch [Paessler Support]

1 Reply

Accepted Answer



Your Vote:



This article applies to PRTG Network Monitor 13 or later

Updating From PRTG 7, 8, 9 or PRTG 12

Please read the following sections carefully before updating from PRTG version 7, 8, 9, or 12 to the latest PRTG version.

Important note: We strongly recommend that you perform a clean install of the latest PRTG version instead of updating from an existing PRTG 7, 8, 9, or 12!

Direct updates from PRTG versions prior to to the latest version do not work! You have to perform intermediate updates first.

For details, please see PRTG Manual: Update From Previous Versions

If You Have 10,000 Sensors or More

If you have 10,000 or more sensors and your "PRTG Core Server" process already consumes more than 2 GB of RAM (you can use PRTG to find out), you should consider reducing the intervals and time frames of the cached graph data.

You can change this setting in the Memory tab of the PRTG Server Administrator. For all three graphs, please choose the setting that uses least RAM memory. For details, please see the manual section PRTG Server Administrator in your PRTG installation with version 8 or 9.

Why? For optimal support of international languages PRTG as of version 12 internally works with UTF strings which use 2 bytes per string character instead of 1 byte in version 9. This causes about 15% more memory usage for the PRTG Core server.

Discontinued Sensors

Existing instances of the following sensor types will stop working as of PRTG V13 and must be replaced with their successor sensor types!

  • VMware Host Server (SOAP)
  • VMware Virtual Machine (SOAP)
  • Xen Virtual Machine

If your configuration contains these sensor types, they will stop monitoring after upgrading to the latest PRTG version. We recommend that you pause them to keep their historic data. In order to continue monitoring, please add the sensors anew (e.g. using the auto-discovery).

Please Install .NET 4.0

We strongly recommend that you install .NET 4.0 on systems that run the core server (and the remote probes, if you use those). Otherwise the following features will not work:

  • VMware auto-discovery and monitoring
  • Citrix XenServer auto-discovery and monitoring
  • Windows Last Update Sensor
  • Several other sensor types

Changed Geo Maps Provider

When you update to the latest PRTG version, the provider for geographical maps will automatically be switched from Google Maps to MapQuest (using Open Street Map data). You can switch back later at any time.

Windows 2000 and 2003 Not Supported

Systems running Windows 2000 or Windows 2003 are not supported anymore. This means:

  • you cannot install PRTG on systems running Windows 2000,
  • you cannot officially monitor Windows 2000 systems (for example, via WMI), and
  • you cannot install PRTG on Windows 2003 systems.

Especially the WMI Service Sensor will show an error message when monitoring Windows 2000 systems under the latest PRTG version. The message is as follows: Unknown Error in: "Win32_Process"

For a workaround, please see How can I monitor a Windows service on Windows 2000?

When Updating From PRTG 8

There May be an Extended Downtime While Updating

When updating from version 8 of PRTG, the update process might take longer than usual, due to data base and configuration file conversions. This might cause a downtime of your monitoring of 30 minutes or longer.

Note: To update from PRTG 8 to the current PRTG version, you have to update to PRTG 9 first as an intermediate step.

When Updating From PRTG 7

Please update to the latest version 8 and then to PRTG 9 first. Then run PRTG for a short while and install the latest version afterwards.

Fixing Corrupt Updates

The issue that affects most upgraded installations is that the services and executables are not properly replaced. To fix an upgraded PRTG installation that does not start again, proceed with the following steps:

  1. Uninstall PRTG completely.
  2. Open a PowerShell with administrative privileges and run the following command that will remove all PRTG services:
    Get-Service -Name PRTG | ForEach-Object { sc.exe delete $_.Name }
  3. Reinstall PRTG with the new setup.

Monitoring data and configuration will be preserved. Note that PRTG might restart without further notice. After that, PRTG starts with no further problems.


For more information when updating from a version earlier than V9, please see PRTG Manual: Update From Previous Versions

Created on May 9, 2012 9:23:36 AM by  Dirk Paessler [Founder Paessler AG] (10,848) 3 4

Last change on Jun 17, 2016 11:56:25 AM by  Gerald Schoch [Paessler Support]

Please log in or register to enter your reply.

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.