Tip
New
#1
not Microsoft's fault?
I've read the article and I know it's true, but it still feels weird reading that o.O
Windows Update in Windows 10 is broken, but not Microsoft's fault
-
-
New #2
Another take on the DNS issue. Microsoft Aware of Windows Update Bug, Fix Possibly Rolled Out Quietly
-
New #3
-
New #4
"While additional details haven’t been shared, it looks like Microsoft has quietly rolled out a fix, as I’m seeing reports from users that the Windows Update service is up and running once again." (Softpedia)
Just because some users who were broke are now fixed does not imply or prove MS had anything to do with it. Toss grenade...run. Typical..........
-
New #5
Considering the problem was global and is still continuing for some today, one ISP cannot be the sole offender. I have Comcast and at one point yesterday, they were blaming Windows 10 Cumulative Update KB4476976 which came out
January 22nd. Not everyone has Windows 10 or that CU.
Microsoft Servers Down? Service Status, Map, Problems History - Outage.Report
-
New #6
Most are on 1803 or before, or Win 7, not 1809. Linux users had problems, too. Guess that CU bit them too ...........Considering the problem was global and is still continuing for some today, one ISP cannot be the sole offender. I have Comcast and at one point yesterday, they were blaming Windows 10 Cumulative Update KB4476976 which came out
January 22nd. Not everyone has Windows 10 or that CU.
Microsoft Servers Down? Service Status, Map, Problems History - Outage.Report
-
New #7
-
New #8
The whole thing has been a farce. I struggle to see how two major ISPs suddenly go into a DNS issue at the same time. Plus there were problems in other countries, I even saw someone in the Phillipines say the issue developed. Microsoft must of been at the root of the cause. I don’t think that CU was to blame though as it was installed the other week and windows update had been fine right up until the evening ((UK) time) on the 29th. They either changed something or something broke their end on or around the 29th.
-
-
New #9
Windows Update in Windows 10 is broken, but not Microsoft's fault
Last Updated: 05 Feb 2019 at 10:13
Multiple Windows users in the US and UK have been unable to download updates from Windows Update. But rather than the problem lying at Microsoft's end, the culprit appears to be various ISPs' domain name system (DNS) settings.
Users have also reported the same DNS issue preventing app updates from the Windows Store and breaking Microsoft's security feature, SmartScreen.
As spotted by Softpedia, Windows users pinpointed Comcast's DNS settings as the source of the problem, and, oddly, found that switching the computer's network settings to use Google's Public DNS allowed Windows Update to resume.
A user on Comcast's Xfinity community forum said they were able to get Windows 10 updates after changing the Windows 10 device's IPV4 and IPV6 DNS lookups from Comcast's default DNS to Google Public DNS...
Read more: Windows 10 updates are broken again, but this time it's not Microsoft's fault | ZDNet
UPDATE 2/4:
Windows 10 October 2018 Update version 1809 Now Re-Released - Windows 10 Forums
February 4, 2019 9:45 PM PST
“The Windows Update service was impacted by a data corruption issue in an external DNS service provider global outage on January 29, 2019. The issue was resolved on the same day and Windows Update is now operating normally, but a few customers have continued to report issues connecting to the Windows Update service. We expect these issues will go away as downstream DNS servers are updated with the corrected Windows Update DNS entries.”
Quote
Related Discussions
