Windows admin and developer tools: WAC, RSAT, Sysinternals, PowerShell 7
Official downloads for Windows Admin Center, RSAT, Sysinternals, PowerShell 7, Windows Terminal, WinGet, .NET and the VC++ runtime — and which ones belong on a server.
Tools that go on the server, and tools that do not
Section titled “Tools that go on the server, and tools that do not”A common mistake is installing everything on the server. The split that ages well:
- On the server: the runtime the app needs (VC++ redistributable, .NET hosting bundle), the agent your monitoring requires, Windows Admin Center if you deliberately manage that way.
- On a management PC: RSAT, Windows Terminal, PowerShell 7, Sysinternals, WinGet, the ADK.
Every tool on a server is another thing to patch and another thing that can be used against you after a compromise.
Windows Admin Center
Browser-based management for servers, clusters and PCs without opening RDP. The short link resolves to the current MSI.
Open vendor pageRSAT — Remote Server Administration Tools
AD DS, DNS, DHCP, Hyper-V and IIS consoles on a management PC. On Windows 11 it is an optional feature (Settings), not an MSI.
Open vendor pageSysinternals Suite
Process Explorer, Autoruns, Procmon, sigcheck, PsExec. Verify a downloaded ISO/tool with sigcheck; inspect services with Autoruns.
Open vendor pagePowerShell 7
Side-by-side with Windows PowerShell 5.1. Use it for cross-platform scripts; do not remove 5.1, some Windows components need it.
Open vendor pageWindows Terminal
Tabs, panes and a real font for server work. On Server Core there is no Store — use the GitHub release or install it from a desktop.
Open vendor pageWinGet (Windows Package Manager)
Repeatable installs for lab VMs: winget install --id ... --silent. Pin versions in scripts instead of clicking through wizards.
Open vendor page.NET SDK and runtimes
Install the ASP.NET Core Hosting Bundle on servers; the SDK belongs on build machines. Keep runtime versions pinned per app.
Open vendor pageVisual C++ Redistributable
The usual fix for PHP/Node/native tools failing with 0xC0000135 (missing DLL). Install both x64 and x86 when in doubt.
Open vendor page
Windows Admin Center
Section titled “Windows Admin Center”WAC is a browser-based management gateway: server overview, services, event logs, files, PowerShell, updates, and Storage/Cluster views, without opening RDP to the internet.
Two things the marketing does not say loudly:
- The installer is a gateway you host yourself; it is not a cloud service. The
aka.ms/WACDownloadshort link resolves to the current MSI. - It runs on a management host and connects out to servers. Do not expose the WAC gateway directly to the internet; put it behind a VPN or a reverse proxy with authentication, and use the HTTPS port you chose at install.
The Windows Admin Center lab guide covers the install, the certificate choice and the tunnel problem we hit.
RSAT is not one program. It is the set of MMC snap-ins and PowerShell modules for AD DS, DNS, DHCP, Group Policy, Hyper-V, IIS, failover clustering and storage.
On Windows 11 it is an optional feature (Settings → System → Optional features → Add a feature → RSAT: ...), not a downloadable MSI. On Windows Server the equivalent tools are installed as features. If you follow an old blog that points at a WindowsTH-RSAT_...msi, that file is from Windows 10 1809 and will not install.
Sysinternals
Section titled “Sysinternals”The suite is the fastest way to answer “what is this process doing?”:
Process Explorer— handle and DLL view, signature check per process.Autoruns— every autostart location, including scheduled tasks and services.Procmon— file/registry/network trace; use a filter or drown.sigcheck— hashes and signature chain for a downloaded file.PsExec— remote execution; also the tool attackers reach for, so treat its presence on a server as a finding.
Download the ZIP, run from a folder, do not install. Sysinternals tools are signed; verify the signature before running them with elevated rights.
PowerShell 7 and Windows Terminal
Section titled “PowerShell 7 and Windows Terminal”PowerShell 7 installs side by side with Windows PowerShell 5.1. Do not remove 5.1: some Windows components and older modules depend on it.
On Server Core there is no Microsoft Store, so winget install Microsoft.WindowsTerminal will fail. Either use the GitHub release MSIX, or do what most people do — run the terminal on your desktop and connect over SSH/WinRM.
.NET and the VC++ runtime
Section titled “.NET and the VC++ runtime”- Servers hosting ASP.NET Core apps need the Hosting Bundle, not the SDK.
- Build machines need the SDK.
vcruntime140.dllmissing (error0xC0000135) is what the VC++ redistributable fixes. It is the single most common reason a freshly extracted PHP or Node binary refuses to start.