It should never have been connecting in the first place. The previous entries about using “netsh winhttp import proxy source=ie” is just a workaround to let it connect to the internet. If you’ve configured a local WSUS server, and it’s still trying to connect to internet locations, this should worry you. After it fails to connect to the internet, it will then try to talk to local WSUS and work fine. You might have to scroll up a fair way (use the time on the left of the log as a guide because you noted the time earlier). See if it’s got entries about connecting to “”. To confirm if this is the issue, note the time according to system clock, then do a check for updates using the regular process and let it finish (even though it takes ages), then check out closely your Window update log “C:\Windows\WindowsUpdate.log”. The best and quickest way to work around it is to use this command: When it tries (and fails) to connect to the internet, it will retry some 10 or so times, locking up the Windows Update interface until each attempt times out. It does this for something to do with the Windows Store. Even if you try to get it configured Windows Update to go to WSUS server in your local environment. The basic issue is Windows is trying to connect to the internet and checks connectivity when you check for updates.
0 kommentar(er)
