If your SonicDICOM PACS on-premises version does not start, this may be due to recent changes in your Windows environment. In particular, we have identified two common causes and provide step-by-step instructions to resolve them.

What You Should Try First

1. Check if Windows Defender is Blocking DICOMApp

Why This Happens:
After a Windows Update, Windows Defender may mistakenly identify DICOMApp (the core executable of SonicDICOM PACS) as a threat and block it. This prevents the application from starting correctly.

How to fix:
1) Open Windows Security > Virus & threat protection > Protection history.
2) Look for any entries labeled "Threat found" and click to view details.
3) Under "Affected items", confirm the path to the blocked file, PACSManager.exe. It looks like:
C:\Program Files\SonicDICOM PACS\PACSManager.exe
4) If the file path is correct and the application is safe, click "Actions" in the bottom-right.
5) Select "Allow on device".
6) Launch DICOMApp and click "Start" to see if it starts correctly.

2. Extend Windows Service Timeout

How to fix:
1) Open Command Prompt as Administrator.
2) Run the following command:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control" /v "ServicesPipeTimeout" /t "REG_DWORD" /d 90000 /f

This sets the timeout to 90,000 milliseconds (90 seconds).
3) Restart the server.
4) Launch DICOMApp and confirm whether it starts properly.

Still Have Trouble?

If you’ve followed both solutions and the application still won’t start, please let us know on Contact Form: https://sonicdicom.com/contact-us/
We will be happy to support you.

SonicDICOM Team