how to fix it - The credential is invalid. Unexpected sub status (6008)

Question

how to fix it - The credential is invalid. Unexpected sub status (6008)

NUR MAISYARAH SUHAIMI 5

Correlation Id: [Moderator note: personal info removed]

Timestamp: 2025-12-22T01:00:23.000Z

DPTI: [Moderator note: personal info removed]

Message: The credential is invalid. Unexpected sub status (6008).

Tag: 657rx

Code: 2148073494

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Answer 1

AlexDN 11,440 Microsoft External Staff Moderator

Dear @NUR MAISYARAH SUHAIMI,
Thank you for posting your question in the Microsoft Q&A forum. I understand you’re currently unable to sign in due to the error message: “The credential is invalid. Unexpected sub status (6008)” along with code 2148073494. This typically means your device is trying to authenticate using outdated or corrupted sign‑in information.

To better assistance, could you please confirm following information

Does this issue happen in all Microsoft apps (Teams, Outlook, Office) or only in specific ones?
Is this a work/school account (e.g., ******@company.com) and do you know if your license is active?

Are you signed into Windows with the same work account, or a different/personal account?

Does it happen when you use other device to sign-in the same account?

In the meantime, I recommend some steps below

1/ Sign out of all Office/PowerPoint/Teams apps.

2/ Clear cached authentication data:

Delete contents of this folder: %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
Open Control Panel > Credential Manager > Windows Credentials and remove any Microsoft/Office‑related credentials.

3/ Go to Settings > Accounts > Access work or school, disconnect your work/school account, restart the device, and reconnect it.

4/ Try signing in again via https://office.com to confirm credentials are valid.

Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution. Your detailed response will help us diagnose and investigate the issue more efficiently.

I truly appreciate your patience and understanding. If I misunderstood what you’re looking for, feel free to let me know or share a screenshot. I’d be happy to help further!

I'm looking forward for your reply. Thank you for your cooperation.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

AlexDN 11,440 Reputation points Microsoft External Staff Moderator

2025-12-23T08:18:38.34+00:00

Dear @NUR MAISYARAH SUHAIMI,
Good day and I hope you're doing well. I just wanted to check in and see if there is any update from you

If you're still facing any problems, please feel free to share more details about the current error or steps you're stuck on. I’ll be happy to assist further.

Looking forward to your update.
Alex Venegas 0 Reputation points

2025-12-29T14:03:28.5566667+00:00

Hello @AlexDN , I experienced the same problem yesterday 29 of December 2025, and after I found your answer, I applied it and it worked very well!

Thank you!

Happy New Year!
AlexDN 11,440 Reputation points Microsoft External Staff Moderator

2025-12-29T23:35:49.0633333+00:00

Hi @Alex Venegas,
Thank you for sharing your feedback! Every insight you give makes this community stronger and more welcoming. Your voice helps others feel supported and find solutions faster. I truly appreciate you being part of this journey.
stewart graham 0 Reputation points

2026-01-16T13:53:59.5566667+00:00

This worked for me also ... I tried a number of posts from microsoft help, one of which included the credential manager steps. Deleting the contents of %localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy has seemed to push me over the edge ... after I did that, the popup/error didn't appear anymore and I was able to login to my accounts.
Wilker Knupp Soares 0 Reputation points

2026-01-29T20:30:52.5666667+00:00

Gostaria de te agradecer @AlexDN esse procedimento realmente resolveu!
Muito Obrigado!
ENOC ARIAS 0 Reputation points

2026-02-18T04:15:49.46+00:00

Deberia comprobar primero si la hora y fecha del dispositivo sean correctas, y si todo esta bien, entonces verificar reglas de Firewall o algun tipo de proxy activo en el dispositivo.
FK 0 Reputation points

2026-05-29T08:31:41.75+00:00

This worked for me - the AppData folder was empty already but deleting the Microsoft Credentials in the Control Panel and then restarting seems to have fixed it

Answer 2

The error message you are encountering, "The credential is invalid. Unexpected sub status (6008)," suggests that there is an issue with the credentials being used for authentication. Here are some steps you can take to troubleshoot and resolve this issue:

Verify Credentials: Ensure that the username and password you are using are correct. You can test this by logging into the machine directly with the same credentials.
Check Username Format: Depending on your machine's join state, you may need to use a specific format for your username:
- For Microsoft Entra joined or hybrid machines, use ******@domain.com.
- For domain-only joined machines, use DOMAIN\user. You can check your machine's join state by running the dsregcmd /status command.
Account Restrictions: Confirm that there are no security or account restriction policies that might be preventing the user from logging in, such as time-of-day restrictions.
Smart Card Logon: If your machine requires smart card logon, note that connections to machines with this requirement are not supported. You would need to use a machine without this requirement.
Password Expiration: If you were able to connect previously but are now receiving this error, it could be due to a password expiration. Ensure that the password is still valid and has not expired.
Use Password Instead of PIN: If you are using a Windows Hello PIN, switch to using a password, as PINs are not supported for this type of connection.

If you follow these steps and still encounter issues, consider checking the specific error codes associated with your situation for more targeted troubleshooting.

References:

Invalid credentials error when running desktop flows in Power Automate for desktop