Error 8007007A on Xbox 360; MS does NOTHING, keeps closing threads!

Hello

Thank you for coming to the forums today,

Please be aware that you need to follow the forum guideline when posting

I had a similar issue with signing in, I found the best solution was once I was logged in to my account, I set up a pass key sign in on the console which doesn't require you to enter you password at all,

This can be done in all setting, this means your account is safe and locked, but it gets round the error you are facing,

Please let me know if this helps

I hope this help,

Please feel free to use the forum for any questions you might have, but please done not post the that topic as this would be against the forum guildlines

Thank you again

Hello ,

First, please refrain from using caps within your post. It is advised that before posting you review the
Xbox Forum Guidelines to ensure that all users are keeping this community safe and friendly.

You continue to mention that the sign in error (8007007A) has relation to ports involving Xbox Live and a network. While ports are a suggested tool to gain a better connection to Xbox Live, they may not have a relation to why you cannot sign into your profile.

If you are not experiencing any connection quality issues, and have attempted/exhausted multiple troubleshooting steps, it would be best to report this occurrence with our
customer support team.

Best wishes.

Javier, the problem is this is a two-month old problem that is ON-GOING. As it stands now, I have not even touched my 360 since last month because of this stupid problem. All Customer Support has told us is to "send the console out for repairs." What for? None
of us had this problem until the May 2019 update. I was able to log into my console no problem whenever I wanted to enter my password manually until May 2019. This is a problem on Microsoft's end that needs to be fixed. The consumers should not be held responsible
for Microsoft's screw-up with their software updates.

This is one regular tweet I came across on this subject. I'm not the only one affected, and Edgeworth is as well.

https://twitter.com/Lxmhara/status/1132036697204711424
I saw you another post @Lunatic, and that thread was closed after I replied (again, stating it was an old thread, and to start a new one). So I did. And Javier, you are not my 9th grade English teacher. Unless the post is entirely in caps, don't chastise
me on my choice of formatting. MAYBE if you guys didn't give up on Windows Phone, I would've had more formatting options! I've been a user of MS products for 30 years! My first OS was MS-DOS 5.0, so issues like this are not my first rodeo! My point is,
I am NOT the only person having this problem, the textbook, level 1 support tech responses are not working. Suggesting we send in our consoles, when it doesn't matter who has the problem, and what vintage console it is, is not an acceptable solution. Closing
thread after thread, is not an acceptable solution. Commenting on my formatting, instead of why this is only be affecting people that do not want to store a password, is not an acceptable solution.

So, Javier, did you bother to read my follow up? Did you notice that, I've broken this problem down to ONE common denominator? If you do not save your password, this code comes up, and you can not sign it. If you RESAVE your password, however, even with
the service alert that pops up on network test, you can sign in just fine.

As of right now, the ONLY way to secure an account on a 360 is to save the password, then setup a pass code.

To recap, this problem occurs with an account, whether you use 2FA or not. This has been replicated with a White, OG 360 with the Falcon motherboard, hardwired network, AND a newer 360 E on a wireless connection.

This is a service level issue, not one dependent on console. Signing in on Xbox One, and backwards compatible games on a One, do not experience this issue.

This is going to be an advanced level problem, that will have to be elevated, probably to at least a level 3 tech.

Thank you!

Hello Edgeworthian,

First, please refrain from using caps within your post. It is advised that before posting you review the
Xbox Forum Guidelines to ensure that all users are keeping this community safe and friendly.

You continue to mention that the sign in error (8007007A) has relation to ports involving Xbox Live and a network. While ports are a suggested tool to gain a better connection to Xbox Live, they may not have a relation to why you cannot sign into your profile.

If you are not experiencing any connection quality issues, and have attempted/exhausted multiple troubleshooting steps, it would be best to report this occurrence with our
customer support team.

Best wishes.

Hello Edgeworthian,

First, please refrain from using caps within your post. It is advised that before posting you review the
Xbox Forum Guidelines to ensure that all users are keeping this community safe and friendly.

You continue to mention that the sign in error (8007007A) has relation to ports involving Xbox Live and a network. While ports are a suggested tool to gain a better connection to Xbox Live, they may not have a relation to why you cannot sign into your profile.

If you are not experiencing any connection quality issues, and have attempted/exhausted multiple troubleshooting steps, it would be best to report this occurrence with our
customer support team.

Best wishes.

Javier, the problem is this is a two-month old problem that is ON-GOING. As it stands now, I have not even touched my 360 since last month because of this stupid problem. All Customer Support has told us is to "send the console out for repairs." What for? None
of us had this problem until the May 2019 update. I was able to log into my console no problem whenever I wanted to enter my password manually until May 2019. This is a problem on Microsoft's end that needs to be fixed. The consumers should not be held responsible
for Microsoft's screw-up with their software updates.

This is one regular tweet I came across on this subject. I'm not the only one affected, and Edgeworth is as well.

https://twitter.com/Lxmhara/status/1132036697204711424
I saw you another post @Lunatic, and that thread was closed after I replied (again, stating it was an old thread, and to start a new one). So I did. And Javier, you are not my 9th grade English teacher. Unless the post is entirely in caps, don't chastise
me on my choice of formatting. MAYBE if you guys didn't give up on Windows Phone, I would've had more formatting options! I've been a user of MS products for 30 years! My first OS was MS-DOS 5.0, so issues like this are not my first rodeo! My point is,
I am NOT the only person having this problem, the textbook, level 1 support tech responses are not working. Suggesting we send in our consoles, when it doesn't matter who has the problem, and what vintage console it is, is not an acceptable solution. Closing
thread after thread, is not an acceptable solution. Commenting on my formatting, instead of why this is only be affecting people that do not want to store a password, is not an acceptable solution.

So, Javier, did you bother to read my follow up? Did you notice that, I've broken this problem down to ONE common denominator? If you do not save your password, this code comes up, and you can not sign it. If you RESAVE your password, however, even with
the service alert that pops up on network test, you can sign in just fine.

As of right now, the ONLY way to secure an account on a 360 is to save the password, then setup a pass code.

To recap, this problem occurs with an account, whether you use 2FA or not. This has been replicated with a White, OG 360 with the Falcon motherboard, hardwired network, AND a newer 360 E on a wireless connection.

This is a service level issue, not one dependent on console. Signing in on Xbox One, and backwards compatible games on a One, do not experience this issue.

This is going to be an advanced level problem, that will have to be elevated, probably to at least a level 3 tech.

Thank you!

The fact that this has to be brought up by even an Ambassador has shown how much of a problem this is. Makes me wonder why contacting support is a pain in the ****. There's literally no good help outside of canned responses if it comes to major topics like
this one. There is literally no channel reaching the right people.

Hello Edgeworthian,

First, please refrain from using caps within your post. It is advised that before posting you review the
Xbox Forum Guidelines to ensure that all users are keeping this community safe and friendly.

You continue to mention that the sign in error (8007007A) has relation to ports involving Xbox Live and a network. While ports are a suggested tool to gain a better connection to Xbox Live, they may not have a relation to why you cannot sign into your profile.

If you are not experiencing any connection quality issues, and have attempted/exhausted multiple troubleshooting steps, it would be best to report this occurrence with our
customer support team.

Best wishes.

Javier, the problem is this is a two-month old problem that is ON-GOING. As it stands now, I have not even touched my 360 since last month because of this stupid problem. All Customer Support has told us is to "send the console out for repairs." What for? None
of us had this problem until the May 2019 update. I was able to log into my console no problem whenever I wanted to enter my password manually until May 2019. This is a problem on Microsoft's end that needs to be fixed. The consumers should not be held responsible
for Microsoft's screw-up with their software updates.

This is one regular tweet I came across on this subject. I'm not the only one affected, and Edgeworth is as well.

https://twitter.com/Lxmhara/status/1132036697204711424