As Altered Pro is not a mainstream appliatiion, it's doubtful anyone here knows how it interacts with Windows and Windows processes. I would think that any questions regarding that app would need to be directed to its company. JMO.
Unless I missed it, the Ryzen 9 9950X is not on the list of supported cpu's
Also as I see it, if you are using the free version, you get only 20 minutes of morphing per day.
Altered | Professional AI Voice Changer Software and Services
As far as Windows processes in general,
PER AI, process priority is
not a fixed attribute—it’s part of a dynamic scheduling system. So even if you explicitly set a process to
HIGH, there are several conditions where Windows (or the process itself) will effectively “reset” it.
1) Process restart (most common)
- Any priority you set via Task Manager, PowerShell, or WMI is per-process instance only.
- If the process:
- restarts
- crashes and relaunches
- is spawned as a new child process
→ it returns to its default priority class.
This is the #1 reason people think priority is “resetting.”
2) System reboot / logoff
- All processes revert to defaults after reboot.
- Windows does not persist priority settings across sessions.
3) Task Scheduler behavior
- Tasks started via Task Scheduler do NOT run at Normal by default.
- They run at Below Normal priority (value ~7) unless explicitly changed.
So even if you set HIGH later, if the task:
- re-triggers
- is restarted by scheduler
…it will come back at Below Normal again.
4) Windows dynamic scheduler adjustments (thread-level)
- Windows uses dynamic priority boosting/decay internally.
- Even within a HIGH class process:
- thread priorities can fluctuate
- CPU scheduling may reduce effective execution priority
Important: this usually doesn’t change the
class label (HIGH), but can make it behave like it dropped.
5) Application-level overrides
Some applications:
- explicitly call SetPriorityClass() internally
- or spawn worker processes with their own priority
Result:
- your manual HIGH setting gets overwritten shortly after
(Common with games, services, and some background agents.)
6) Service / parent-child process inheritance
- Child processes don’t always inherit modified priority
- Services started by SCM often revert to defined defaults
Why PowerShell / Task Scheduler setups “don’t stick”
Typical pattern:
Get-Process myapp | % { $_.PriorityClass = 'High' }
Problems:
- Runs before process exists → does nothing
- Runs once, but process restarts later → lost
- Scheduler launches app separately → overrides priority
- Timing race (very common)
How to PREVENT priority reset (reliably)
Method 1 — Start the process with priority (best)
Instead of fixing it after launch,
launch it correctly:
CMD
start "" /HIGH "C:\Path\app.exe"
PowerShell
Start-Process "C:\Path\app.exe" -Priority High
This is the cleanest and most reliable approach.
Method 2 — Task Scheduler + proper configuration
If using Task Scheduler:
Critical fixes:
- Do NOT launch the EXE directly
- Launch PowerShell instead:
Start-Process "C:\Path\app.exe" -Priority High
- In task settings:
- Run with highest privileges
- Use trigger: At logon or startup
- Add delay if needed (important!)
This avoids the default Below-Normal issue.
Method 3 — Watchdog script (for stubborn apps)
If the app resets its own priority:
while ($true) {
Get-Process "myapp" -ErrorAction SilentlyContinue |
ForEach-Object { $_.PriorityClass = 'High' }
Start-Sleep -Seconds 5
}
Run via Task Scheduler.
Use cautiously—can cause instability if abused.
Method 4 — IFEO registry (advanced, persistent)
Set default priority via:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<app.exe>\PerfOptions
Value:
CpuPriorityClass = 3 (High)
Pros:
- Persistent
- Applies on every launch
Cons:
- Global (affects all launches)
- Requires admin + care
Important reality check
- Windows intentionally does not support permanent HIGH priority as a normal feature.
- This is by design to:
- prevent starvation of system processes
- maintain responsiveness
If something keeps dropping priority, it’s usually:
- restarting
- managed by the app
- or being relaunched by Task Scheduler
—not Windows “randomly undoing it.”
Best practice summary
If you want it to
stick:
- Start the process with HIGH (don’t modify after)
- Avoid launching EXEs directly from Task Scheduler
- Add startup delay if needed
- Use IFEO only for stubborn cases
Don’t rely on one-time PowerShell fixes
