What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

PowerShell 32-bit or 64-bit and Execution Policy



If I run PowerShell notifications or EXE sensors with Powershell scripts, which PowerShell version is used by PRTG (32-bit, 64-bit) and how do I have to configure the PowerShell Execution Policy?

32bit-to-64-bit exe-script-sensor executionpolicy powershell script security

Created on May 25, 2011 8:19:17 AM by  Tobias Lange [Paessler Support]

Last change on Mar 10, 2022 3:08:43 PM by  Frank Hadasch [Paessler Support] (0) 1

1 Reply

Accepted Answer



This article applies as of PRTG 22

PowerShell 32-Bit and 64-Bit and Execution Policy

Even on a 64-bit Windows system, PRTG starts the 32-bit version of PowerShell. Because of that, the Execution Policy of the 32-bit PowerShell must be correctly set. It is independent from the 64-bit Execution Policy.

Find the 32-bit version of Windows PowerShell here: %SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe

Execute the following command from a Windows command line to enable PowerShell scripting: %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe "Set-ExecutionPolicy RemoteSigned"

For information about signing PowerShell scripts and the Execution Policy for scripts, see the following external resources:


Created on May 25, 2011 8:35:47 AM by  Tobias Lange [Paessler Support]

Last change on Jan 2, 2023 2:24:08 PM by  Brandy Greger [Paessler Support]

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.