After doing extensive testing on my end, and finally having some people cooperate and test it too(To determine that it is indeed not a person to person case), it is safe to say that the Halo Reach File Share system is broken in the sense that nothing new can be uploaded to it. I have tried to do so and did everything I could to troubleshot and nothing worked. I had several other people try with the same results. Additionally as a side/secondary glitch, whenever Halo: Reach is started up, the “Welcome to Halo Reach” screen for new players, or one of the Forward Onto Dawn messages comes up everytime of starting the game.
Every time I try (and the same with other LIVE users) to upload any file to the file share, I get a Transfer Failed message stating the file cannot be submitted. I am hoping that a fix is found to these given issues by 343i soon (Not demanding an immediate fix, I don’t feel entitled, lol), as it somewhat counterbalances Reach being backwards compatible with the one not having the File Share work along the lines of adding new files.
Yeah i have been trying for days and i haven’t been able to fix it, glad its not just me.
> 2533274975125454;2:
> Yeah i have been trying for days and i haven’t been able to fix it, glad its not just me.
Well, I’ve done a large assortment of things to try to troubleshoot the given issue and nothing has worked. It seems Reach is glitched in that sense server wise, as well as the “Welcome to Reach” message popping up everytime Reach is started up now. There has also been reports since this has been happening of people being temporarily being cR banned while playing in Custom Games, so I think the servers for Reach need maintenance, it’s just a matter of when 343 will get around to it.
I had the same issue guys
So, an odd little update. The File Share is still broken, but they might be trying to fix it today. Reason why I say that is logging onto Reach today, my 360 oddly synced my cloud storage when going onto the main menu screen. Either that or, its breaking even more.
> 2533274898831741;5:
> So, an odd little update. The File Share is still broken, but they might be trying to fix it today. Reason why I say that is logging onto Reach today, my 360 oddly synced my cloud storage when going onto the main menu screen. Either that or, its breaking even more.
I think they just fixed it because the reach server were completely hard-rebooted.
> 2533274873630868;6:
> > 2533274898831741;5:
> > So, an odd little update. The File Share is still broken, but they might be trying to fix it today. Reason why I say that is logging onto Reach today, my 360 oddly synced my cloud storage when going onto the main menu screen. Either that or, its breaking even more.
>
>
> I think they just fixed it because the reach server were completely hard-rebooted.
Thanks for the news. It’s fixed 
.
Update: It’s broken again, back to Transfer Failed.
Update: File Share was up for about ten minutes and is down again.
ANother Update, The File Share was on and off since my last post, but appears to be down now again.
Last Update, from me anyways. I do have what I wanted from my File Share screenshot wise and reconfigured it, though the File Share is still going in and out. I dunno if my updates helped out on 343’s end at all. Community Engineer Cizlin thanked me for making this thread, so I’m guessing it did. What seems to fix the issue for a minute before it derps out, at least from my testing is clearing the system cache and redownloading the 2 MB update. I dunno if that information can help out on 343’s end, but I hope it does.
So, if somebody else wants to keep testing and updating, they can, but I am done with testing as I am reaching the same results and have completed what I wanted to do.
Well, it’s 2018, now, and it’s still not fixed. Lol. Why am I not surprised? Why is the file share like this, now?
Please don’t revive 2 year old topics, thanks