Using Classic Outlook on Windows for personal email, calendar, and contact management
how can i fix itttttttttttttttttttttttttttttttttttttttt
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Unable to open Teams and Outlook on multiple company devices. This is disrupting bussiness.
Error tag: 7Q6ch
Error code: 2147500037
Troubleshopoting tried...
Clearing Outlook cache.
Running online repair.
Restarting device.
SIgning in/out of work/school account.
Cleaned up outlook temp folders.
Outlook safe mode won't start.
Can you please advise if a solution?
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
how can i fix itttttttttttttttttttttttttttttttttttttttt
Ran into this issue when I installed a licensed version of M365 over the temp version that comes with Dell Laptops- couldn't get it to activate with the online M365 license. Took a day to troubleshoot using all of the "fixes" I found on the Internet with no joy. Opened a case with MS...tried a bunch of stuff with no joy. Finally, they had me run "sfc /scannow" as a last resort- it found and replaced some corrupted system files. Rebooted and now all is hunky dory
that 1001 error is related to fslogix. KB5045594 fixes that error
Hi Jacob,
We are experiencing this same issue in our organization as we attempt to implement Virtual Desktop Infrastructure. Our VDI desktop utilized Shared Computer Activation for Microsoft 365 and when a user launches Outlook or Teams it will prompt them for their credentials and then it brings up the Office activation page and when you attempt to sign in you can enter your email address and then it shows the "Something went wrong [7q6ch]" error. The funny thing about this is that if the user waits a few days and attempts to access Outlook (or any other Office app) within the VDI desktop, the error might not happen anymore.
Occasionally the user's writable volume has to be reset to clear data and when this happens it will frequently cause Office apps to stop working again. So far, it appears that there is some sort of time limit for Shared Computer Activations but no one has been able to confirm this for sure. As an admin for the environment it is critical that we understand how this works and can respond to users. So far, Microsoft hasn't been able to give us a straight answer as to why this is happening.
I also find it very interesting that you started seeing this in early August as that is also when we started seeing the issue. I currently have version 2407 Build 16.0.17830.20166 installed. Is it possible that the problem has to do with this build of Office? I am considering trying an earlier build to see if it has the same issue.
Hello folks,
I wanted to post a quick update to let you know of my progress. Your posts helped me significantly as I went ahead and swapped to version 2302 of Office. I still had this version in the App Volumes library so I was able to switch the "CURRENT" version from 2407 to 2302 and this eliminated the 7q6ch error entirely. I ran into a minor issue where if the user signs out of the Office activation they are not able to sign back in during the active logon session but if they log out of Windows and log back in, they are able to sign back into and activate the Office apps. So, this issue seems to be related to the MONTHLY channel version of Office that came out in July of '24. The next step is for me to build an app volume with a more recent build (thinking 2402 Semi-Annual would be prudent) and see if Office continues to work correctly. As for you guys, I would consider removing Office from the workstation and obtaining the Semi-Annual build to see if that corrects your issue.
Just because it is the latest and greatest, doesn't mean it works the best - tried and true versions can often be the better solution!