No sale el intro de mi Xbox one x[The intro of my Xbox one does not appear x]

If you have the console set to Instant On you will not see the intro. Try holding the power button on the console for 10 seconds till it shuts down then restart. You'll see the intro then.

Modern Warfare está causando que mi Xbox One X se bloquee y apague por completo mi consola.
Soy consciente de que Infinity Ward está trabajando en el problema, pero hoy no han recibido una actualización de ellos, ya que mencionaron en su página de soporte de reddit que trabajarían estrechamente con Microsoft en ese tema.
¿Alguien sabe cuándo solucionarán este problema para los usuarios de Xbox One X?
Además, mi consola se ha apagado por completo como si fuera a apagarla manteniendo presionado el botón xbox durante 10 segundos, como 10 veces.
Dañó la configuración de mi red y me obligó a restablecer la tabla NAT en la configuración de mis enrutadores.
Además de eso, ¿qué otro daño a largo plazo ha sido hasta el momento de corromper el disco duro de todos los reinicios duros aleatorios?

Yo lo tengo y mi xbox one x no tiene ningún problema.

muchas gracias por contestar, los siento quise decir que mi xbox es serie x, y el hdmi que uso es el que viene en la caja de la caja de la xbox, de igual forma mi tv es hasta UHD 4K, 3840 x 2160 a 60 Hz

Al parecer no es el juego, ya que funciono funciono bien en mi vieja xbox one, encontre un hilo donde mencionaban muchos detalles entre este juego y xbx x desde el mes de noviembre...

[Translation - Apparently it is not the game, since it worked well in my old xbox one, I found a thread where they mentioned many details between this game and xbx x since the month of November …]

Checked earlier but wouldn't let me reply. Turns out that my controller firmware is up to date. This is indeed a very strange issue! I can't remotely think of anything off the top of my head that you haven't already tried but I'll have a think. No doubt
it will be a software-related bug.

Hi, thanks for writing!

Actually, your findings are not surprising to me. When I was trying to make some sense of this situation, I tested the older an older Xbox One controller (manufactured in 2014) with the Xbox One X – which worked flawlessly (noteworthy
here is the fact that the latest firmware version that is available for the older controller is 2.x, which is different from the Xbox One X model 1708 controller – bearing a firmware version of 3.x). Likewise, in my tests, the Xbox One X controller worked
flawlessly with the good old Xbox One. There is something in the combination of the Xbox One X and controller model 1708 (the one that ships with the Xbox One X, which is essentially the same as the Bluetooth-enabled controller that can be purchased separately)
that is causing this problem.

Moreover, if you turn on the console using the power switch that's on its enclosure – rather than using the controller –
and activate the Xbox One X controller just after the Xbox One X-exclusive 4K intro animation has been played, it syncs without a hitch. However, if you do the same and yet activate the controller almost simultaneously with turning the console itself
on – this issue recurs.

This suggests that turning the console on with using the console's power button – as opposed to the controller – is of no significance here; what's significant is the timing thereof. Get past the 4K intro animation and everything syncs fine (this is also consistent
with the inability to reproduce this issue when "Instant-On" mode is activated, because then the 4K intro animation does not get played back to begin with). Moreover, another interesting factor is that the original Xbox One itself does not have any 4K intro
animation, and is able to sync with this controller perfectly every time.

I've been working in the software industry for over a decade (for most of that time, I was responsible creating interfaces between various software and hardware components). Although this is plain guesswork and speculation, this situation bears high resemblance to
a typical timing issue.

By the way – I, too, can confirm that version 1711 of the operating system had no effect on this issue and as such it still persists. The Xbox Support representatives, on their part, are not aware of this issue and suggest that I send my console in for service.

How could something as fundamental as this be missed during a proper QA/QC procedure is beyond my perception.