Interesting, looks like it's geofenced now, getting 403 directly but c2r.microsoft.com works on vpn. Wonder if I need VPN to run it too now. Edit: confirmed, does not start on my direct connection (Ziggo) but works when I'm on a VPN to Australia, did not even need to reinstall. Go figure.
Looks like Akamai geofencing to me $ curl -v c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe * processing: c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe * Trying [2a02:26f07::58dd:fe60]:80... * Connected to c2r.microsoft.com (2a02:26f07::58dd:fe60) port 80 > GET /ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe HTTP/1.1 > Host: c2r.microsoft.com > User-Agent: curl/8.2.1 > Accept: */* > < HTTP/1.1 403 Forbidden < Server: AkamaiGHost < Mime-Version: 1.0 < Content-Type: text/html < Content-Length: 309 < Expires: Fri, 25 Aug 2023 17:49:51 GMT < Date: Fri, 25 Aug 2023 17:49:51 GMT < Connection: close < <HTML><HEAD> <TITLE>Access Denied</TITLE> </HEAD><BODY> <H1>Access Denied</H1>
Scratch that's, it's IPv6 that fails, IPv4 works, that explains why it suddenly stopped working after I changed wifi connection and forgot disable IPv6 $ curl -v c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe * processing: c2r.microsoft.com/ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe * Trying 104.110.191.136:80... * Connected to c2r.microsoft.com (104.110.191.136) port 80 > GET /ConsumerC2R/en-us/14.0.4763.1000/SetupConsumerC2ROLW.exe HTTP/1.1 > Host: c2r.microsoft.com > User-Agent: curl/8.2.1 > Accept: */* > < HTTP/1.1 200 OK < Content-Length: 1632984 < Content-Type: application/octet-stream < Last-Modified: Wed, 14 Dec 2016 06:45:10 GMT < Accept-Ranges: bytes < ETag: "0xA8E45E6CEDBBA1A9C70B73C3B4620936D1E4BF18F6B1FEED264154B8C9A8868F" < ApiVersion: Distribute 1.1 < Content-Disposition: attachment; filename=SetupConsumerC2ROLW.exe; filename*=UTF-8''SetupConsumerC2ROLW.exe < X-MSEdge-Ref: Ref A: 460A9966381F460FBF71BA6AEE005314 Ref B: CH1AA2020615035 Ref C: 2023-08-25T17:54:03Z < Cache-Control: public, max-age=259200 < Date: Fri, 25 Aug 2023 17:54:03 GMT < Connection: keep-alive
Why not temporarily uncheck IPv6 from the Internet Protocol option in the network adapter options? Now you have actually succeeded.