Fix WinRM and install .NET Framework

WinRM is how some deploy tools talk to Windows. .NET Framework is a separate Windows feature. Run the steps below from an elevated PowerShell session on the VPS.

Step 1: Open an elevated prompt

Right-click Windows PowerShell and choose Run as administrator. If you are on Server Core, you are already at a prompt — just confirm the window is elevated.

Step 2: Enable WinRM

This turns on the WinRM service, creates a listener, and adds a firewall exception for trusted management.

Enable-PSRemoting -Force

• Confirm the Windows Remote Management service is Running.
• Only allow WinRM from addresses you trust. Do not leave HTTP WinRM open to the whole internet.

Step 3: Configure WinRM (recommended)

If the output says WinRM is not configured properly, apply the default configuration and follow the on-screen prompts.

winrm quickconfig

• This enables the WinRM service and creates a firewall exception.
• Follow the on-screen prompts to complete the configuration.

Step 4: Verify WinRM is running

Get-Service WinRM
winrm enumerate winrm/config/listener

1. The State should be Running.
2. You should see a listener on HTTP (5985) or HTTPS (5986).

Step 5: Trust the client

On your laptop, add the VPS to TrustedHosts or use HTTPS with a certificate.

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "YOUR_VPS_IP" -Concatenate

Replace YOUR_VPS_IP with the address from the client area.

Step 6: Install .NET Framework

Use Server Manager → Add Roles and Features, or install from PowerShell:

Install-WindowsFeature NET-Framework-45-Core

Reboot if Windows asks. Add extra .NET packs only if the app you are installing requires them.

If install still fails

Check Windows Update, disk space, and that the evaluation or license is not expired. Open a ticket with the exact error text if the feature store itself is corrupt.