Hum, yes, thats the problem. A broken windows (update) and/or missing services. ^^ My link above claims it got fixed by MS by now, while its not. Your link beeing from 2019 also has more reports than solutions (that I tried), but thanks.
I had a similar problem as you today, though not exactly the same. Yesterday I installed a new copy of NAV 360 so I wanted to BU the 2 PCs & 1 Laptop I installed it on. The Main rig went smooth so did the laptop. When I got to the Test rig it wanted to install W10 v2004 (have 19H2) so I tried to defer it using gpedit, that failed so I just let it install. Afterword's I uninstalled the Connector & DL & installed it again... FAIL to connect using Launchpad. Next I updated the 0.0.0.0.DNS settings using the Google Public DNS: 8.8.8.8 and 8.8.4.4, still no joy. So I uninstalled the Connector again. So I read my notes from previously w/ screenshot (attached) & deleted the (8) entries in Task Scheduler/Microsoft/Windows/Windows Server Essentials. Restarted the PC again, installed Connector again & was off to the races. HTH
My same WSE2016 Connector problem happened again updating from 19H2 to 20H2 builds for the PC backup Windows 10 OS. I went through the same steps again starting w/ 1. Uninstalling 'Connector'. 2. Update the DNS settings (as above) 3. Delete 8 items in the Task Scheduler (as above) 4. Restart PC 5. Install 'Connector' per my WSE2016 Installation guide for small businesses. & My WSE2016 backup began for that Test rig test. --- This was good news as I also have a x86 Win10 install on that PC w/ a favorite 16bit app & it still works on this newer feature update. --- This WSE2016 BU w10/partition had another problem (I fixed after mutable tries) after the update as it wouldn't shut down, but that's going to be another thread/post on another day.