Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 31 replies
  • Subscribers 38 subscribers
  • Views 110442 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SFOS V17 - Microsoft Update and Xbox Download Issues

ShawnGilronan

I recently upgraded my SFOS software to v17.0.0 GA from 16.05.8MR-8.  After upgrading, I was not able to run ANY updates from windows, let alone the anniversary updates people have had issues with lately.

Additionally, I thought my Xbox One X had died, after just getting it.  I had a bunch of patches to install for various games, and all of them were failing to install, until I connected the dots to the windows updates failing on all of my PCs as well.

Here's the curious part, after analyzing both the Xbox One downloads, as well as the windows updates, I noticed that all of the updates and downloads crashed out at the 2 GB mark.  It was easy to trace with the Xbox, as it gives you a running total of the current download.  However I ran the real-time logs through Sophos as well, and noticed every time the download hit the 2GB mark, it would be killed.

I set the exception for Microsoft Windows Update to ON for the Web Exception filtering, however it had no affect on the problem.

Why would Sophos kill any downloads from Microsoft that hit the 2GB mark?  What is special about that file size?  I did not have this problem with any other files of larger sizes.  I moved a bunch of my movies up to my google drive and onedrive, and was able to pull them back down no problem.

I would love to upgrade (again) to v17, however until this problem is resolved, I'll stick to v16.5.



This thread was automatically locked due to age.
  • 0

    I had this problem with SFOS 17.0.6 MR-6 and followed  post almost to success. I had to add *.microsoft.com.akadns.net to my list of FQDN hosts in the Xbox Live Group in order to get the update through.

    I found that hostname by turning on packet capture filtered to just the Xbox One S' IP and doing a reverse lookup (google search) on the relevant IP address. Took a few sites to find the actual domain behind it. Looks like it's simply a CDN.

    For clarity's sake, my problem wasn't specifically that I couldn't get an update larger than 2GB to download, it was that I couldn't get any update to download period. It would look like the xbox was stuck on downloading, not doing anything, but if I turned the Xbox on and off I'd get 0x801901a0 which thanks to Microsoft's presence on GitHub I know translates to HTTP 416 aka the range error.