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

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.
  • Its possible.  I saw the same site, and unchecked malware scanning as well for anything coming from microsoft sites.  I even enabled the Microsoft Windows Update exception, and added a few sites to the list, and nothing worked with a file size of over 2 GB.

    All of the xbox game downloads, as well as any windows updates were immediately stopped as soon as they hit 2GB.

  • Any update on a fix for this?  I am see it in other area's like streaming music.  I had to exclude my xbox from all filtering policies to get past the limit issues, I don't want to have to do that to all my devices on the network.

  • In my case this only started after the upgrade to v17 mr-1. Maybe my pc did not find the magic update earlier.

    Ian

  • Sophos knows this ussue. I have opened a case about this.

    Message from sophos:

    "This is regarding the service request number 7725689.

    => We have got the below update from our GES team for reported issue.

    This issue is happening because range headers requesting byte ranges beyond 2Gb are failing. Also, 25582 means this bug is encountered even though the traffic is excluded from AV scanning.

    These lines in the awarrenhttp.log are the indicators of this:

    1511533406.470651931 [ 3388/    0x6b6f2200]       scanner.c:930   check_range_reqs parse_byterange failed to parse range header bytes=2147483647-2147483647 (2147483647,2147483646)
    1511533406.470659486 [ 3388/    0x6b6f2200]       scanner.c:990   process_request Blocking range request due to invalid range header
    1511533406.470663371 [ 3388/    0x6b6f2200]   awarrenhttp.c:519   set_errorstatus called
    1511533406.470670256 [ 3388/    0x6b6f2200]   awarrenhttp.c:501   prepare_response_header Not using error_headers for 416 (Range Not Satisfiable), instead use response_headers prepared
    1511533406.470679606 [ 3388/    0x6b6f2200]      response.c:670   send_response_headers called
    1511533406.470687171 [ 3388/    0x6b6f2200]      response.c:605   construct_response_headers_to_send statusline: [HTTP/1.1 416 Requested range not satisfiable]

    As of now no workaround is available for this to work with proxy.The reported issue is already forwarded to development team and they are working on priority for making permanent resolution."

  • Hi,

    interesting response considering that the MAC beta updates are all 2gb in size and download successfully, sometimes requiring two attempts.

    Ian

  • Nothing from Microsoft over 2GB in size would compete for me.  Windows updates, Xbox Live game downloads, even downloads from my subscription to Visual Studio (MSDN) over 2GB in size wouldn't complete.

    Its nice to know this is a bug in the SFOS software, and not me going nuts trying to figure out the issue, like I was initially.

    Hopefully the development team has a resolution soon, otherwise I'll be sticking to V16.

  • I had the same issue with XG after upgrading to 17 with my Xbox, many system resets later and I find its how the firewall policies now work in 17.  First you need to create your NAT forwards like usual. Those ports can be found on Xbox.com support, but here is the trick to make it work create a firewall rule like below.

     

     

    The details

    The group info

    The custom domains

  • Hi guys,

    thanks, the workaround from @BrianHawkins1 helped ... at least partially.

    My windows Machine seems to be able to download bigger chunks again (downloaded a windows store app with 8G sucessfully) but the xbox still seems to run into the 2G limit.

    I tried to add *.windows.com to the host group (i thought i identified one connection to an IP of that hostname on the xbox) but it didnt help. How can i identify the hosts I need to add to the rule in oder to make it work?

     

  • For Xbox Live? These are all the ones I had  to do to allow downloads to work. Do you have NAT setup to forward the standard ports?