I came onsite today to setup a new laptop (Windows 10, HP) to discover that Windows updates was very unhappy on the new setup. Discovered that the XG was blocking (warning really) about *.windows.com .CAB files which meant my XG web filter was blocking windows updates.... Not sure for how long on existing computers, but as soon as I manually added an exception for windows.com in the web filter policy, everything started working fine. Noticed that Sophos only listed microsoft.com and windowsupdates.com in the filter, but maybe Microsoft recently started using windows.com also for update CAB files....Not sure if I'm the only one, but this was my fix today.
Thank you for sharing your findings. I did find Microsoft.com in one of troubleshooting document from the Microsoft and this document :https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-troubleshooting so I am not sure if this is a recent change from the Microsoft. I will check if I can replicate this issue in my LAB and update this thread.
Community Support Engineer, Support & Services | Sophos Technical SupportSupport Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts If a post solves your question use the 'Verify Answer' button.
Sounds good, the conditions are when you have XG set to warn for risky downloads (not even block) just warn. And it's not microsoft.com that came up as an issue but instead windows.com as I mentioned, thanks. A bunch of my Win 10 computers got the newest feature update after I added exception, that had been failing last week.
Sorry that is my bad.
Yes, you mentioned Windows.com and it is also mentioned in the document from Microsoft.