docs/install/windows-release-channels.md
You can switch between different Netdata release channels on Windows based on your needs. This guide covers the process with step-by-step instructions.
Unlike Linux systems where Netdata has multiple install types (native packages, static builds, Docker, etc.), Windows only has one install type: the MSI installer.
This simplifies the switching process significantly:
| Channel | Download URL | Update Frequency | Recommended For |
|---|---|---|---|
| Stable | https://github.com/netdata/netdata/releases/latest/download/netdata-x64.msi | Major and patch releases | Production systems, most users |
| Nightly | https://github.com/netdata/netdata-nightlies/releases/latest/download/netdata-x64.msi | Daily builds | Testing, early adopters, bleeding-edge features |
Choose Stable Channel If:
Choose Nightly Channel If:
Update Frequency: Stable releases occur every few weeks to months, while Nightly builds are updated daily with every commit to the master branch.
</details>When switching between release channels on Windows, the MSI installer automatically preserves your important data and configuration.
Preserved during channel switches:
netdata.conf, collector configs) in C:\Program Files\Netdata\etc\netdataNot preserved (by design):
:::tip
Unlike switching between install types on Linux, Windows channel switching does not require manual backup and restore procedures. The MSI installer handles data preservation automatically.
:::
Download the Stable MSI:
https://github.com/netdata/netdata/releases/latest/download/netdata-x64.msiRun the installer:
.msi fileVerify the installation:
Download the Nightly MSI:
https://github.com/netdata/netdata-nightlies/releases/latest/download/netdata-x64.msiRun the installer:
.msi fileVerify the installation:
:::warning Silent installation isn't supported on Windows Server versions earlier than 2019 due to TLS compatibility issues. Use the GUI installer instead. :::
<details> <summary>Switch to Stable Channel via PowerShell</summary># Run PowerShell as Administrator
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest https://github.com/netdata/netdata/releases/latest/download/netdata-x64.msi -OutFile "$env:TEMP\netdata-x64.msi"
msiexec /qn /i "$env:TEMP\netdata-x64.msi" REINSTALL=ALL
# Run PowerShell as Administrator
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest https://github.com/netdata/netdata-nightlies/releases/latest/download/netdata-x64.msi -OutFile "$env:TEMP\netdata-x64.msi"
msiexec /qn /i "$env:TEMP\netdata-x64.msi" REINSTALL=ALL
If you want to ensure your Netdata Cloud connection is maintained during the switch, you can provide your claim token and room IDs explicitly.
Get your current cloud settings:
# Check current cloud configuration
Get-Content "C:\Program Files\Netdata\etc\netdata\cloud.d\cloud.conf"
Look for your token and rooms values.
Switch to Stable with Cloud settings:
# Run PowerShell as Administrator
$TOKEN = "<YOUR_CLOUD_TOKEN>" # <-- Replace with your Netdata Cloud claim token
$ROOMS = "<YOUR_ROOM_IDS>" # <-- Replace with your comma-separated Room IDs
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest https://github.com/netdata/netdata/releases/latest/download/netdata-x64.msi -OutFile "$env:TEMP\netdata-x64.msi"
msiexec /qn /i "$env:TEMP\netdata-x64.msi" TOKEN="$TOKEN" ROOMS="$ROOMS"
The REINSTALL=ALL parameter is a Windows Installer (MSI) standard option that forces reinstallation of all Netdata components, ensuring a clean upgrade path.
When to use REINSTALL=ALL:
When not to use REINSTALL = ALL:
:::warning
The REINSTALL = ALL parameter ensures complete replacement of binaries but is not required for normal channel switches. The MSI installer handles upgrades automatically.
:::
After switching channels, verify which version you're running:
<details> <summary>Check via Netdata Dashboard</summary>http: //localhost:19999v2.1.0 (clean version number)v2.1.0-123-nightly (includes commit hash)# Get installed Netdata version
Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object {
$_.DisplayName -like "*Netdata*"
} |
Select-Object DisplayName, DisplayVersion, Publisher
Example output:
DisplayName : Netdata
DisplayVersion : 2.1.0
Publisher : Netdata Inc.
You can also verify the Netdata service is running through the Windows Services manager:
Or check via PowerShell:
# Check Netdata service status
Get-Service netdata | Select-Object Name, Status, DisplayName
# Check service executable path
Get-WmiObject win32_service | Where-Object { $_.Name -eq 'netdata' } | Select-Object PathName
Symptoms: MSI installer shows error about existing installation
Solution 1: Use the REINSTALL=ALL parameter explicitly:
msiexec /qn /i netdata-x64.msi REINSTALL=ALL
Solution 2: Uninstall first via Windows Add/Remove Programs, then reinstall:
Or uninstall via PowerShell:
# Uninstall existing installation
msiexec /qn /x netdata-x64.msi
# Wait for uninstall to complete
Start-Sleep -Seconds 10
# Reinstall with new channel
msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" ROOMS="<YOUR_ROOMS>"
Symptoms: After switching channels, node doesn't appear in Netdata Cloud
Solution: Reclaim the node:
# Stop Netdata service
Stop-Service netdata
# Remove old cloud configuration
Remove-Item "C:\Program Files\Netdata\var\lib\netdata\cloud.d\*" -Force
# Reinstall with claim token
msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" ROOMS="<YOUR_ROOMS>" REINSTALL=ALL
# Start service
Start-Service netdata
You can also verify the service status in Windows Services:
</details> <details> <summary>Issue: Service Won't Start After Switch</summary>Symptoms: Netdata service fails to start after channel switch
Solution: Check service status and perform clean reinstall:
# Check service status
Get-Service netdata
# Check Windows Event Log for errors
Get-EventLog -LogName Application -Source Netdata -Newest 20
# Perform clean reinstall
msiexec /qn /x netdata-x64.msi
Remove-Item "C:\Program Files\Netdata" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item "$env:PROGRAMDATA\Netdata" -Recurse -Force -ErrorAction SilentlyContinue
msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" ROOMS="<YOUR_ROOMS>"
If the service still won't start, check the Windows Services manager to ensure the Netdata service is present and configured correctly:
</details>For users who prefer the traditional Windows approach, you can also manage Netdata installations through the Windows Control Panel:
Access Add/Remove Programs:
Locate Netdata:
Uninstall if needed:
This method provides a familiar Windows experience but requires manual download and installation of the new channel.