Calculate multiple critical paths
| Registry value | calculate multiple critical paths |
| Group Policy | Calculate multiple critical paths |
| German version | Mehrere kritische Wege berechnen |
| Intune settings catalog | Calculate multiple critical paths (User) |
| Scope | User · HKCU |
| ADMX | proj16.admx · L_PjCalcMultipleCriticalPaths |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\ms project\options\calculation | |
| calculate multiple critical paths | Enabled = 1 · Disabled = 0 |
Not configured = the value does not exist – the application default applies and users may change the setting.
PowerShell
Check the current value (read-only)
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calculation"
foreach ($name in @('calculate multiple critical paths')) {
try { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
catch { '{0}: not configured' -f $name }
}Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.
Enable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calculation"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'calculate multiple critical paths' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # Enabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Disable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calculation"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'calculate multiple critical paths' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # Disabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Reset to Not configured
# --- Settings --- $root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>' $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calculation" Remove-ItemProperty -Path $key -Name 'calculate multiple critical paths' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Calculate multiple critical paths (User)
Settings catalog → Add settings → search for the name above.
Intune Settings Catalog Viewer ↗
Alternative: custom profile (OMA-URI)
| OMA-URI | ./User/Vendor/MSFT/Policy/Config/proj16v2~Policy~L_Proj~L_ProjectOptions~L_PjCalculation~L_PjCalcProjectFile/L_PjCalcMultipleCriticalPaths |
| Data type | String |
| Value | <enabled/> · <disabled/> |
Cloud Policy
Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Calculate multiple critical paths. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
Specifies that Project should calculate and display a critical path for each independent network of tasks within the project.
If you enable this setting, Project will calculate multiple critical paths.
If you disable or do not configure this setting, the user's default setting is used.
Same category: Microsoft Project 2016 › Project Options › Calculation › Calculation options for 'Project1'
- Updating task status updates resource statusauto track resources
- Move start of remaining parts before status date forward to status datemoveremaining
- And move end of completed parts forward to status dateandmovecompleted
- Move end of completed parts after status date back to status datemovecompleted
- And move start of remaining parts back to status dateandmoveremaining
- Edits to total task % complete will be spread to the status dateedits to total task %complete will be spread to the status date
- Inserted projects are calculated like summary tasksinserted projects are calculated like summary tasks
- Actual costs are always calculated by Microsoft Projectactual costs are always calculated by microsoft office project
- Edits to total actual cost will be spread to the status dateedits to total actual cost will be spread to the status date
- Default fixed costs accrualdefault fixed costs accrual
- Tasks are critical if slack is less than or equal toshow as critical if slack
All policies in this category · All 140 policies of proj16.admx