Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
I tested using two methodologies.
I took a device inside my network behind Firewalls and Proxies and it failed.
I took the same device and plug edit into a home network without firewalls and Proxies and it worked.
We then used Fiddler and Wireshark to analyze the traffic and found that connections to Microsofts CDN when we invoked the Clicktorun were not using the WinInet Proxy.
Our Proxies were configured for Authentication for Microsofts CDNs. When we disabled Authentication, as is required for WinHTTP Proxy, the Click to run worked and our Office started to update. We've had 4000 Systems stuck on June's update for 2 months, As of today we've been able to patch 3000 systems with this firewall/proxy change.
This is not the kind of configuration the ordinary user would have here. I would assume most users here are on a home network and not an enterprise environment as you describe. Also, besides the fact that how does this explain some of the users having fixed the error, me included by other implementations mentioned here? Your knowledge is commended but I would be surprised that ordinary users will need to implement this type of change.