How to install software on a Windows VPS without crashing running services

Check actual RAM usage via PowerShell:

Get-CimInstance Win32_OperatingSystem | Select-Object @{
  Name='Free_RAM_MB'; Expression={[math]::Round($_.FreePhysicalMemory/1024)}
}, @{
  Name='Total_RAM_MB'; Expression={[math]::Round($_.TotalVisibleMemorySize/1024)}
}

If Free_RAM_MB is below 500 MB, do not start the install yet. You will force heavy paging and drag the live services down.

Identify processes consuming memory unnecessarily:

Get-Process | Sort-Object -Property WorkingSet64 -Descending |
  Select-Object -First 10 Name, @{Name='RAM_MB';Expression={[math]::Round($_.WorkingSet64/1MB,1)}}

Look for non-essential processes — background updaters, orphaned old RDP sessions, open browsers. Kill anything non-critical via Stop-Process -Id <PID>.

Clear the Windows Update cache if it has grown bloated:

Stop-Service -Name wuauserv -Force
Remove-Item -Path "C:\Windows\SoftwareDistribution\Download\*" -Recurse -Force
Start-Service -Name wuauserv

The Windows Update cache frequently piles up several GB and consumes I/O while the service is active. Clearing it gives the disk breathing room during the install.

Add the installer folder and the target directory as temporary exclusions:

Add-MpPreference -ExclusionPath "C:\Users\Administrator\Downloads\installer"
Add-MpPreference -ExclusionPath "C:\Program Files\MyProgram"
Add-MpPreference -ExclusionProcess "setup.exe"

Replace the paths with the actual ones for your case. The process-level exclusion covers installers that extract into variable temporary folders.

Confirm the exclusions were applied:

Get-MpPreference | Select-Object ExclusionPath, ExclusionProcess

The output should list the paths you added. If it comes back empty, check that PowerShell is running as Administrator.

Start the installer with Below Normal priority:

Start-Process -FilePath "C:\Users\Administrator\Downloads\setup.exe" `
  -ArgumentList "/S" `
  -WindowStyle Hidden `
  -PriorityClass BelowNormal

The /S flag is the silent install switch for NSIS (common on Windows installers). For MSI use msiexec /i package.msi /qn /norestart. For Inno Setup use /VERYSILENT.

If the installer is interactive (needs clicks), open it normally and adjust the priority afterwards via Task Manager:

$proc = Get-Process -Name setup -ErrorAction SilentlyContinue
if ($proc) {
  $proc.PriorityClass = 'BelowNormal'
}

In extreme cases where the install may take a while and the server has constant load, use 'Idle' instead of 'BelowNormal' — but be aware the install can take 5-10x longer.

Monitor the impact on critical services in another PowerShell terminal:

while ($true) {
  $cpu = (Get-Counter '\Processor(_Total)\% Processor Time').CounterSamples.CookedValue
  $ram = (Get-CimInstance Win32_OperatingSystem).FreePhysicalMemory / 1024
  Write-Host ("CPU: {0:N1}% | Free RAM: {1:N0} MB" -f $cpu, $ram)
  Start-Sleep -Seconds 5
}

If free RAM drops below 200 MB or CPU stays at 100% sustained for more than 30 seconds, consider pausing (Suspend) non-critical installer processes via Suspend-Process (PSTools module) or aborting and trying outside peak hours.

Check whether Winget is available:

winget --version

If it returns a version (e.g. v1.7.10661), it is installed. If it errors out, Winget is not available on that Windows release — skip to the next section.

Search for the package you want:

winget search "program name"

The ID column is the unique identifier used for install. Use the exact ID, not the friendly name.

Install with automatic agreement acceptance and silent mode:

winget install --id Microsoft.PowerShell `
  --accept-package-agreements `
  --accept-source-agreements `
  --silent

Winget itself uses little RAM and delegates the heavy lifting to the package’s native installer — which should still run during low-load hours on a tight VPS.

Confirm all essential services are still active:

Get-Service -Name @('W3SVC','MSSQLSERVER','MyAppService') |
  Select-Object Name, Status, StartType

Replace the list with the services you noted at the start. They should all be Running. If any are Stopped, start them with Start-Service -Name <Name> and investigate the cause in Get-EventLog -LogName System -Newest 50.

Check whether the install left orphaned processes consuming RAM:

Get-Process | Where-Object { $_.ProcessName -match 'setup|install|msiexec' }

Ideally the output is empty. If there are leftover processes, kill them with Stop-Process — installers sometimes leave worker processes running after they finish.

Test the newly installed program in minimal mode before configuring it — open, check the version, close. That confirms the install was clean before you invest time in real configuration.