justin
24b9e0aa80
A fresh Windows Server install has neither ASP.NET Core 8 nor .NET
Desktop 8, so the Service refuses to start and the GUI fails to
launch — the symptoms link to aka.ms/dotnet-core-applaunch but it's
not obvious from the GUI itself what's wrong.
Setup now:
- Detects each runtime by looking for an 8.x folder under
%ProgramFiles%\dotnet\shared\Microsoft.{AspNetCore,WindowsDesktop}.App
- Uses Inno Setup's built-in TDownloadWizardPage to fetch any missing
runtime from the aka.ms redirect and runs `/install /quiet /norestart`
- Treats Microsoft's 1638 / 3010 / 1641 exit codes as success
If the box has no internet, the prereq install fails with a clear
message and a "continue anyway?" prompt. README + installation docs
list the manual download URLs and `dotnet --list-runtimes` check;
troubleshooting has a section pointing at the same fix when the
service won't start after install.
Webhook Server documentation
Webhook Server is a Windows service that runs a script (PowerShell, cmd, or any executable) when an HTTP request hits a URL you choose. It's designed for sysadmins who want to wire a tool like Zerto pre/post scripts, GitHub Actions, a monitoring system, or a backup tool into a Windows-side automation step — without writing a custom listener every time.
New here? Start with these
- Concepts — five-minute read on what a webhook is and how this server uses one
- Installation — download, install, first endpoint
- Recipe: Zerto failover post-script → DNS + service checks — the canonical reason this exists
Topical
- Upgrading
- Uninstalling
- Run As modes — when to use which
- Service account & Active Directory
- Network & security
- Troubleshooting
Recipes (cookbook style)
- Zerto failover post-script → DNS + service checks ← canonical use case
- GitHub-style HMAC-signed webhook
- Pop UI on the user's desktop
The flagship Zerto recipe also ships with a ready-to-use Zerto-side post-script at scripts/examples/zerto-post-failover.ps1.