Xbox One X Media Player and Film & TV

I have a Seagate 4Tb USB 3.0 External HDD connected to my Xbox One X for media files (mp4 and MKV files).

This is seen as 3.6Tb total space by the Xbox One X and has 1.3Tb free space. This is a brand new drive < 2 weeks old. When the external drive is plugged into my laptop, it is possible to play any and all of the MP$ and MKV files through the Windows 10 Film
& TV app. It is also possible to connect this app, via Wi-Fi, to my Xbox One X and for the videos to then be played on the TV via the Xbox One X.

When, however, I connect the hard drive directly to the Xbox One X a large number of the videos are not playable and result in the following error being displayed:

Can't play.

Please try again. If the problem continues, visit www.xbox.com/support to check for guidance.

0xc00d11cd (0x80070001)

To say this is exceptionally annoying is an understatement. I have searched on both Xbox.com and through Bing.com - there is absolutely no information regarding this error available.

My Xbox One X is enrolled within the Xbox Insider Program and, as of the time of writing this, is running build 413.1807.26001.70 that was.
My console received the latest OS update on 24/08/2018 at 04:44 GMT. I am inclined to believe that this error is linked to the Xbox Insider Program builds as I have absolutely no recollection of ever seeing this error prior to enrolling my console
within the Xbox Insider Program, some 10 months ago.

I have logged this as an issue with multiple builds of the Xbox OS since I first saw it. I logged it with a Chat Agent when I had an issue with the Xbox One X even seeing this new drive a couple of weeks ago. Thus far, I have not even had the courtesy of
a response or even acknowledgement that this is an issue.

I fully understand that building and testing new software can be an exceptionally complex task and that priorities have to be set as logged issues are triaged to ensure that the most pressing issues are resolved in a timely fashion. I do find it staggering
and bordering on incompetent as well as a horrendous failure of customer support that nobody has bothered to respond (at the very least) to the Chat session in which I raised this (once again) as an issue and was advised that a response would be forthcoming.

I actually enjoy testing the Xbox OS for Microsoft and am more than happy to continue to do so. I do, however, request that some (any) information regarding this specific error be provided and (if possible/applicable) what, if anything, is scheduled (or
backlogged) to resolve this issue.

As I mentioned, I fully realise that this is in all probability a minor issue within the Xbox ecosystem - and that perhaps it is infact expected behaviour in certain circumstances - all I ask right now is some kind of acknowledgement and an explanation of
what the error codes actually mean.

:)

 

Media Player Device Discovery Issue

I had the same issue (including all the *sometimes* fixed it) but I SEEM to have resolved it (at least my Xbox One X has had a couple of restarts and still appears to find my server.

I had both my NAS (running a Twonky server) and my Xbox One X hard wired directly into the router - Xbox Films and TV app couldn't find the server (though the Films and TV app on my Windows 10 laptop had no such issue).

Now you're comment about the Xbox One X being hardwired (and the S being wireless) got me to thinking: as the Xbox is hard wired into the router I've never run the wireless set-up on my Xbox - may be worth a shot. This actually seems to have fixed it for
me (again at least for the time being).

I'll post again if it drops the server discovery but hopefully this has sorted it!

Cheers!

 

ERROR 0x8007139f help

I am getting the same error when trying to start Films & TV. I have uninstalled and installed numerous times with no success on both the internal and external drives.

Works ok on my XBOX One X but not my new XBOX One X

 

Just in case the 3.6Tb is also an issue for you, be aware that the 4TB on the packaging are "marketing" TB, which are calculated with 1000GB, whereas "real" TB are calculated with 1024GB.

So
4 marketing "Terabyte" are actually 3.6 Tebibyte, and therefore the size displayed is correct.

As for the videos not playing:

It would help immensely, if you could provide information about the video and audio codecs that were used for your MKV's and MP4s.

For example, while the Xbox One supports Dolby Athmos in the BluRay app, the codecs for Dolby Athmos are not available to the Film&TV app on the console, whereas on the PC you can install codec packs, that make different video and audio codecs available
to that app.

So when you file feedback through the Feedback app available to you as an Insider, please provide exact information with how the video is encoded, and what sound format is used.

Be aware, that MKV is not a format itself, but only a container that can bundle a variety of video and audio codecs, which are not all supported by the Film and TV app on your Xbox console, as you can't install external codecs yourself like you can on the
PC.

 

Thanks for your reply.

There are two issues not addressed in your answer.

1. What does the error code mean?
2. Why does this affect both MP3 and MKV files?

 

1. My assumption is, that either the console doesn't have the fitting codecs for the media file, or after searching for this particular error, that the Media Player app has issues with drives larger than 2TB.

In order to resolve the codec question, it would help if you knew the audio and video codec used on the MKV or MP4 file (or did you mean MP3 audio-only file in your first original post)?

2. It depends on wether your original post or this post has a typo.

If your first post is correct, and you have issues with MP4 (four) and MKV, then know that both filetypes are container files for a video and audio stream of varying codec formats.

For example, you could have a MKV consisting of a MPEG2 Video stream and Ogg Vorbis audio compression. Or the MP4 could be a H.264 Video stream and a AAC encoded audio track.

The Xbox One only has limited support for various audio and video codec combinations.

If your second post is correct, and you have issues with MP3 (three) audio files (that should work 100%), then I'd assume the issue is, that the console's Film & TV app can't work with drives larger than 2TB, as people with similar issues report that 2TB
hard drives with MBA work, whereas GPT partitioned discs seem to cause this error with disks beyond the 2TB limit.

 

Thanks for your reply.

From what I am seeing the issue is almost certainly that the Xbox One series have issues with external drives that are >2Tb.

I have reached this conclusion because I identified a few duplicate files on the drive, connected the drive to my Windows 10 laptop and removed the duplicates. When the drive was once again connected to the Xbox One X, a few of the files that were previously
inaccessible/unplayable, have now become accessible/playable.

It was my understanding that the Xbox One series were able to address up to 16Tb of combined external storage space. This does not appear to be the case when the drive is formatted as NTFS. With the NTFS format it appears that the maximum drive space is
2Tb; I have an identical make and model HDD (although 8Tb in size) that is formatted for Games Storage and the Xbox One X has no problems with this drive.

Ergo, the issue must (logically) be that the Xbox One series of consoles have an issue with addressing more than 2Tb of storage space that is not formatted to the propitiatory Xbox games storage format.

It is not an issue with the file formats themselves, this is a blind alley. The issue is with the amount of external HDD space that the Xbox One series of consoles may address. It would seem reasonable to assume that the error codes (0xc00d11cd (0x80070001))
refer to the NTFS partition being to big for the Xbox OS to effectively address, but as there is no data from Microsoft to support this, it remains a guess.

What I would like now is a definitive response regarding the actual meaning of the 0xc00d11cd (0x80070001) error codes, not a guess as to what it seems likely to mean.

Cheers.