Xbox interface unresponsive, error on report 0x80070c00

I love standby, even in the preview program I reset infrequently

YW. It works pretty well... does the same thing as holding the power button until it shuts down, except for it restarts on its own, which is nice.

I agree with Goatsnatcher on quitting apps. I almost always quit them as soon as I'm done with them, which seems to help keep things running more smoothly between restarts. I really wish they'd add a 'quit all' option. A lot more people would probably use
that if it were a feature and it'd be a lot more convenient than quitting them separately. At least now we can restart the way it should be done, which I do pretty regularly anyway.

The problem with the energy saver setting though is that it doesn't download updates overnight, so theoretically you could log on one evening to play Destiny, only to find a 3gig update needs to be downloaded.

Which is another reason I prefer Energy Saver; do not want things updating without my approval. Take Killer Instinct for example...It's been wanting a 6Gb update since season two released, I may want to play a few games here and there (Offline), but I don't
like it well enough to update. Most months I'm close to my cap and others I go over; 6Gb of data serves me better for another high def movie rather than a game I rarely play.

Peace, J.R.

So far I haven't had an update stop me for more than 15 minutes. There are ups and downs either way. What we need is a "Restart" option. So we can use instant on and just reboot it if there's a need. Or, reboot it once a day or something as a preventative
measure.

Yes, you can hold the power button to do this, but I prefer the "Graceful" shutdown method.

These weird glitches may happen from time to time. It's usually a result of using the "instant on" mode, where the console goes to sleep instead of turning off completely. If you're having unexplained issues with the console, you can hold your finger on
the power button (on the console itself) for about 8 seconds and that will force a full shutdown, so when you turn it back in it'll do a full boot up instead of waking up from sleep.

If you're in the preview program it's also a good idea to use the feedback reporting tool if something like this happens, so that the devs can look at the logs and see what caused it.

So yeah, I'd just put it down to a system software bug, considering pulling the power and doing a full reboot cleared it.