![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 12%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 61%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHP%3C/text%3E%3C/svg%3E)
Hi Midi,
That error means the gateway web service itself isn’t responding, even though the main RD Gateway program looks like it’s running. After the security patch, the part of Windows that delivers the gateway through IIS likely stopped working. Usually this happens if the SSL certificate on port 443 isn’t loading correctly or if the “RDGateway” application pool in IIS crashed. The fix is to open IIS Manager, check that the RDGateway pool is started, and confirm the certificate binding is still valid. If the pool keeps stopping, it’s tied to the latest update and may need either a rollback of that patch or waiting for Microsoft’s hotfix. In short, the gateway service is up, but the web layer it depends on is broken.
Hope it helps.
Harry.