Applies to:
@RISK 6.x and Up, Professional and Industrial Editions
@RISK for Project 4.x

@RISK opens the wrong version of Microsoft Project (or won’t open Project unless it’s already running)

 

Issue
If you have multiple versions of Microsoft Project installed, @RISK may open the wrong one, or fail to open Project unless you start Project manually first.

Cause
@RISK uses a registry setting to determine which version of Project to launch. When multiple versions are installed, this setting may be missing or pointing to the wrong executable.

Solution: Set the Project version in the Windows Registry

If you are comfortable editing the registry, you can explicitly tell @RISK which Project version to open.

Step 1: Find the correct Winproj.exe path

Make sure Microsoft Project is not running, then locate the executable and note its full path. Examples:

• C:\Program Files\Microsoft Office\OFFICE11\Winproj.exe

• C:\Program Files (x86)\Microsoft Office\OFFICE14\Winproj.exe

Step 2: Open the Registry Editor

• Click Start → Run

• Type REGEDIT and click OK
  (Or search for Registry Editor in newer Windows versions)

Step 3: Navigate to the Palisade key

• On 64-bit Windows:
  HKEY_LOCAL_MACHINE\Software\WOW6432Node\Palisade

• On 32-bit Windows:
  HKEY_LOCAL_MACHINE\Software\Palisade

In the right pane you’ll see several string values such as Main Directory and System Directory.

Step 4: Create or edit the Project Path value

• If Project Path exists:
  Double-click it and replace the value with the full path to Winproj.exe

• If it does not exist:

  • Right-click → New » String Value

  • Name it Project Path (with a space)

  • Double-click it and paste the full path to Winproj.exe

Step 5: Test

Launch @RISK.

• If the correct version of Project opens, you’re done

• If not, recheck and adjust the path

Alternative (no registry editing)

If you are using @RISK for Project 4.x, simply open your preferred version of Microsoft Project before launching @RISK.