Adding the verbose resulted in this:
* Trying 142.250.187.206:80...
* Connected to google.com (142.250.187.206) port 80 (#0)
> GET / HTTP/1.1
> Host: google.com
> User-Agent: curl/7.81.0
> Accept: */*
* Recv failure: Connection reset by peer
* Closing connection 0
It hung on the "> Accept: */*" row for a minute or so then showed "linux ~ 127"
Yes, I have a standard home network setup. Single router with devices connected via wifi or Ethernet.
Sorry, I don't know how to add error 56.
* Trying 142.250.187.206:80...
* Connected to google.com (142.250.187.206) port 80 (#0)
> GET / HTTP/1.1
> Host: google.com
> User-Agent: curl/7.81.0
> Accept: */*
* Recv failure: Connection reset by peer
* Closing connection 0
It hung on the "> Accept: */*" row for a minute or so then showed "linux ~ 127"
Yes, I have a standard home network setup. Single router with devices connected via wifi or Ethernet.
Sorry, I don't know how to add error 56.
(12-26-2022, 04:13 PM)stevef link Wrote: The first commands check a few basic things about your connectivity which all appear ok.
The last command (curl) replicates what the update script checks before proceeding. It should get a near instant response but looks like it is timing out (or giving error 56) for you despite you having a working connection. Try the adding the verbose option to the command to see if it gives any more information on why this is happening.
Code:curl -vsk google.com
I'm assuming you are on a straight forward home network - let us know if that's not the case.
I wouldn't have thought this is related to previous Windows 11 not updating - but I don't really know.
5 minute boot time - seems long for that spec machine, could possibly be related, but I think we need to sort the updates first.
Edit - add error 56