How to Set High CPU Priority for SoftdriveServer.exe (Windows IFEO Registry)

Overview

This article explains how to configure Windows to automatically launch a process with a higher CPU priority using Image File Execution Options (IFEO).

This is commonly used in Softdrive environments to prioritize services like SoftdriveServer.exe to improve performance during CPU contention.


Applies To

  • Windows 10
  • Windows 11
  • Softdrive virtual desktops

Prerequisites

  • Administrator access to the virtual machine
  • Access to Registry Editor (regedit)
  • Exact process name (e.g., SoftdriveServer.exe)

Procedure

1. Open Registry Editor

  • Select Start
  • Type regedit
  • Press Enter

2. Navigate to IFEO Path

Paste the following into the address bar:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options

3. Create Process Key

  • Right-click Image File Execution Options
  • Select New → Key
  • Name the key exactly:
SoftdriveServer.exe

4. Create PerfOptions Subkey

  • Right-click SoftdriveServer.exe
  • Select New → Key
  • Name it:
PerfOptions

5. Configure CPU Priority

  • Select the PerfOptions key
  • Right-click → New → DWORD (32-bit) Value
  • Name:
CpuPriorityClass
  • Set value to:
3

6. Restart Process or Reboot

  • Restart the service or
  • Reboot the virtual machine

Changes apply the next time the process starts.


Priority Values Reference

ValuePriority Level
1Idle
2Normal
3High
4Realtime (Not Recommended)
5Below Normal
6Above Normal

Validation / Expected Result

  • Open Task Manager
  • Go to the Details tab
  • Locate SoftdriveServer.exe
  • Confirm Priority = High

Troubleshooting

Priority not applied

  • Confirm process name matches exactly: SoftdriveServer.exe

No change after configuration

  • Restart the service or reboot the VM

System instability

  • Do not use Realtime priority (value = 4)

Best Practices

  • Only prioritize critical services (e.g., SoftdriveServer.exe)
  • Avoid applying High priority to multiple processes
  • Monitor CPU usage after changes to confirm impact