Windows UPDATE "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet."

I'm in the UK with BT as my ISP  

I turned on my laptop today, didn't faff around with any settings whatsoever,  and I no longer get that error message! It just works. I'm not quite sure what fixed it  but I just turned on my laptop after 3 days (I encountered the problem on Saturday) and the WU began to download and install

Hi. I'm on BT as well, but it took the DNS change to 8.8.8.8 and 8.8.4.4 to get me working again ( that was after 'live chatting' with someone at BT; who after contacting MS informed me that MS were working on it and it could be a week before it's fixed!! ). Seems fixes are very machine specific, judging by comments from the 'Community. It will be interesting to see how / when the situation will be resolved.

I'm in UK on BT internet had this problem for 5 days. Today I turned off the BT Hub, left it off for 30 seconds then turned it back on again.  Windows Update now working again.

What were the steps? I just updated THREE computers and NONE of them are able to connect to Windows Update. I did an "in-place upgrade" on one of them and it did not resolve the problem. 

MESSAGE: "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet."

UPDATE is KB4476976 (OS Build 17763.292)

And, yes, I am connected to the internet. This is very annoying. If it is an issue/bug (and it must be) how does MS plan on rolling out a fix if users cannot connect to Windows Update? I have tried all the known fixes out there (stop/start services related to WU, run various commands in an elevated command prompt, perform an in-place upgrade, you name it. Nothing works).

Thanks.

William Hill

i have the same issue until now

Hello Community,

Me again - I contacted MS via the 'Get Help' facility of Windows 10 and an MS chap (via Support-LogMeInRescue) took control of my computer and sorted it. He was so quick I could not quite follow what he did but he changed some IP stuff to something like 4.2.1.1 or 4.2.1.2 (so quickly I could not quite make it out I'm afraid!). He did this after an ipconfig/flushdns (as administrator) and then did a restart.

I know this is almost certainly a bit vague for you techies out there but it might give you a 'starter for ten' as they say on University Challenge/College Bowl. However, the long and the short of it is that MS online folk have an answer, it would appear, for non-techie bozos like me. It is still working ok after a shut down (before going the pub) and start (after returning from the pub, to calm what had been frayed nerves!!). Hoorah!