We couldn't connect to the update service. We'll try again later, or y

Page 3 of 3 FirstFirst 123

  1. Posts : 215
    Windows 10 Home x64
       #21

    DragonskissXXX said:
    Tried this and sadly no Fix... Is this actually something on MS or Comcasts end that will be fixed eventually? or is it something that i will need to actually Fix.
    I'm no pro but I regret not just relaxing and waiting. MS support said my Win store or win update components were corrupted which seems strange since that was right after fresh install and it still wasn't updating.

    The DNS workaround I don't know how solid that is because like I mentioned in another thread they switched the DNS when I was connected through Ethernet and it did work but then on WiFi it continued to work and no adjustments were made to the network adapter DNS settings.
      My Computer


  2. Posts : 1
    Win10
       #22

    I built 4 x PC yesterday with the MediaCreationTool1809 and they all have the same issue

    We couldn't connect to the update service. We'll try again later, or y-err.png

    Version 1809 (OS Build 17796.253)

    I've tried going to Settings/Update & Security/Troubleshoot and click on Windows Update to run Troubleshooter to fix it. Troubleshooter didn't find any issue so I opened File Explorer and go to C:\Windows and rename SoftwareDistribution folder to SoftwareDistribution.bak and then ran Windows Update again, still broken!

    EDIT

    So I just connected my NORDVPN client and bang it's now working!!
    Last edited by HEADRAT; 31 Jan 2019 at 04:53.
      My Computer


  3. Posts : 7
    Windows 10 Pro
       #23

    I have four PCs here in UK. BT as my ISP.

    2 x Acer i7, 1 x HP Envy Laptop, 1 x Linx Notebook.

    MS Dialled in to one unit yesterday (30th) & claimed it needed a reinstall from iso. They revised that after I questioned why 4 units should fail at the same time. Currently waiting for a call back and answers from Level 2 support.

    A previous update some 2 or 3 weeks ago broke my Office 365 licensing on all machines. MS had to fix that via remote connection.

    Tried nslookup as in #10 above, received the incorrect response as shown in that post.
      My Computer


  4. Posts : 1
    Windows 10
       #24

    Nothing seemed to fix this issue until i changed the WPD MS Telemetry, WPD MS Third Party and WPD MS Update rules in Windows Defender outbound rules. All three were blocked. Go to Windows Defender Firewall with Advanced Security, click on outbound rules and they should be listed near the top.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:59.
Find Us




Windows 10 Forums