Title
Create new category
Edit page index title
Edit category
Edit link
Why Does OPSWAT Central Management Not Start After Successful Installation?
Central Management version 7.3x
This article applies to all OPSWAT Central Management 7.3x + releases deployed on Windows systems.
After installing Central Management , the installation completes successfully but the application does not become accessible.
This issue can occur when the PowerShell Execution Policy is restricted by machine or group policy settings.
Root Cause
The PowerShell Execution Policy on the system is set to AllSigned at the Machine Policy level.
Central Management requires the execution policy to be set to RemoteSigned, which is also the default policy on a standard Windows Server installation.
When the policy is restricted to AllSigned, required scripts may fail to execute, preventing the application from starting properly even though the service is running.
Verification
- Open Windows PowerShell or Windows Terminal
- Run as Administrator
- Execute the following command:
Get-ExecutionPolicy -List
- Review the output
- If MachinePolicy is set to AllSigned, this is likely the cause of the issue
Resolution
Change the PowerShell Execution Policy to RemoteSigned.
Option 1: Change Execution Policy via PowerShell
- Open Windows Terminal or PowerShell as Administrator
- Run the following commands:
Get-ExecutionPolicy -List
cd "C:\Program Files\OPSWAT\Central"
Set-ExecutionPolicy RemoteSigned
Confirm the policy change when prompted
- Reinstall the Central Management product
Option 2: Configure via Group Policy Editor (If PowerShell Change Does Not Apply)
If the execution policy is enforced by Group Policy, update it using the Local Group Policy Editor.
- Press Win + R and type:
gpedit.msc
- Navigate to:
Computer Configuration
> Administrative Templates
> Windows Components
> Windows PowerShell
- Locate and open Turn on Script Execution
- Set the policy to Enabled
- Select Allow local scripts and remote signed scripts
- Click Apply and OK
- Run the following command to refresh policies:
gpupdate /force
- Reinstall the Central Management product
If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
