Fix Something Went Wrong (7q6ca) When Signing Into Microsoft Word

If Microsoft Word shows Something Went Wrong (7q6ca) when signing in and reports that it cannot download or upload data because cached credentials are expired, refresh local identity cache folders after closing Microsoft 365 apps. This guide follows the cache-rename steps that clear stuck sign-in data before you escalate the account issue.

What the Word Sign-In Error 7q6ca Means

Word shows Something Went Wrong (7q6ca) during sign-in. The app may indicate it cannot download or upload data because cached credentials are expired. Sign-in problems usually involve account identity, saved credentials, security information, or organization policy rather than Word alone.

Quick Answer for Word Something Went Wrong 7q6ca

Close all Microsoft 365 apps. Press Windows + R, open %LocalAppData%\Microsoft, then rename the IdentityCache and OneAuth folders to IdentityCache.old and OneAuth.old. Restart the computer and try signing into Word again. Confirm you use the correct account context if sign-in still fails.

Possible Causes of Word Sign-In Error 7q6ca With Expired Cached Credentials

• Cached credentials in local identity folders may be expired or stuck.

• IdentityCache or OneAuth data under LocalAppData may be out of sync with the current Microsoft account.

• Multiple Microsoft 365 apps may still hold an old sign-in session.

• Organization policy or account security settings may still block access after a local cache refresh.

Recommended Solution: Rename IdentityCache and OneAuth Folders for Word Error 7q6ca

When to use this: Use this when Word shows Something Went Wrong (7q6ca) and cached credentials appear expired, especially if Credential Manager alone did not clear the problem.

If the issue is not resolved in Credential Manager, cached credentials may still be stored under the Microsoft LocalAppData folders. Try the following steps:

1. Close all Microsoft 365 apps.

2. Press Windows + R, then enter %LocalAppData%\Microsoft and press Enter.

3. Look for the IdentityCache and OneAuth folders.

4. Rename them to IdentityCache.old and OneAuth.old.

5. Restart the computer and sign into Word again to see whether error 7q6ca is cleared.

Why this works: Renaming IdentityCache and OneAuth forces Microsoft 365 apps to rebuild local auth data instead of reusing expired cached credentials.

If this fails: Confirm the correct personal or work account, refresh authentication again after restart, and escalate to an administrator or Microsoft support if the account remains inaccessible.

Additional Check: Confirm Account Context After Clearing Word Sign-In Cache

1. After restart, open Word and sign in only with the account that should own the files or license.

2. If both work and personal accounts are present, sign out of the unused account before retrying.

3. If the account is work or school managed, ask an administrator whether a policy is blocking sign-in.

Keep Editing Documents With WPS Office While Word Sign-In Error 7q6ca Persists

WPS Office cannot repair Microsoft account sign-in, cached Microsoft credentials, or the 7q6ca authentication path inside Word. Those fixes stay with Microsoft account and Office sign-in tools.

While Word sign-in is blocked, WPS Writer can help you keep document work moving:

1. Install WPS Office on your computer.

2. Open a local copy of the document in WPS Writer.

3. Edit and save locally, and export to PDF if you need a shareable copy.

4. Return to Word after IdentityCache and OneAuth are rebuilt and sign-in succeeds.

This reduces downtime when Word cannot complete sign-in. If you need a practical writing alternative during account recovery, try WPS Office.

Use Word, Excel, and PPT for FREE

Free Download

Prevention Tips for Word Sign-In Cache Problems

• Close Microsoft 365 apps fully before switching between work and personal accounts.

• Avoid signing into many accounts inside the same Office profile when you only need one.

• Keep a local document copy before clearing identity cache folders.

• Restart once after renaming IdentityCache and OneAuth so apps rebuild clean auth data.

FAQs About Word Something Went Wrong 7q6ca

Do I need to delete IdentityCache and OneAuth?
Rename them to .old first so you can recover the folders if needed; a restart then rebuilds fresh cache data.

What if Credential Manager did not help?
Cached credentials may still live under %LocalAppData%\Microsoft in IdentityCache and OneAuth.

Can WPS Office clear the 7q6ca Word sign-in error?
No. WPS Office cannot fix Microsoft sign-in; it can help you edit documents while you clear the cache.