This message was deleted.

Well, i did just find this... perhaps this is the kicker... I know you said to delete these keys, but didn't realized it was REQUIRED for it to work.. If experimentation was previously enabled, you also need to delete any data under the following registry keys to clear the experimentation cache HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Experiment HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentEcs HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentTa

Have to delete the Experiment Keys to temporarily resolve the issue. The DisableFeatureRollout key stopped working for us with a recent update of Office as well. Did I post this link already? https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/authentication/connection-issue-when-sign-in-office-2016 I have an open ticket, but MS doesn't really seem interested in working on the issue and would rather just close the ticket by installing an older version of Office (Semi-annual vs Current channel) that doesn't have what ever Experimental code is being installed. I don't recall if I posted more on this as well, where we created an Outlook launch script that deletes the Keys before opening Outlook: @echo off reg delete hkcu\software\Microsoft\Office\16.0\Common\Experiment /f reg delete hkcu\software\Microsoft\Office\16.0\Common\ExperimentConfigs /f reg delete hkcu\software\Microsoft\Office\16.0\Common\ExperimentEcs /f <path to Outlook.EXE> I also just noticed that I have a slightly different set of keys that what you mention above. I believe I have seen the ExperimentTa before as well, but not on all of the accounts with the 1001 errors.

Do you find the outlook launch script "fixes" the issue?

The script works 100% of the time so far to prevent the issue for the users that have it happening. Outlook Version: 2308 (Build 16731.20234 Click-to-Run) Current Channel

Thank you very much

Support requested we roll back to Semi-Annual channel and I refused. I haven't heard back on the next steps.

Semi-Annual fixed the 1001 issue for us, but for some users we had to force Modern Auth with the following Registry keys. It was trying to auth with WAM and was very unhappy.

Yeah, WAM doesn't work for us here either. I have AutoDiscover configured similarly, maybe not exactly the same, and the 3 Identity keys configured already for quite some time to get authentication to work consistently.

that came from MS directly. when they finally responded to our case after a week, after we blew them up.

Microsoft support has told us this is confirmed to be a bug and they are "working on it". They linked us this article, which doesn't help too much. https://support.microsoft.com/en-us/office/error-something-went-wrong-1001-signing-in-t[…]-desktop-applications-6f63238d-d83c-437c-a929-de72fe819793 The temporary relief steps in the article don't do anything for us. We have implemented a login script that removes user permissions to the Experiments Keys (below). It uses SetACL.exe to set the permissions. This does cause SDXHelper.exe to crash, but on 2016 and 2019 servers it crashes silently, so we haven't really been worrying about it. We put in an AppLocker block for it on the couple remaining 2012R2 clients (which are rapidly being migrated out) to prevent pop-up messages when it crashes. We are published apps only, so you may have a different experience if you attempt to go the same route.

@ECHO OFF
reg delete HKCU\Software\Microsoft\Office\16.0\Common\Experiment /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs /f

reg add HKCU\Software\Microsoft\Office\16.0\Common\Experiment /ve /f
reg add HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs /ve /f
reg add HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs /ve /f

"%~dp0\SetACL.exe" -on hkcu\Software\Microsoft\Office\16.0\Common\Experiment -ot reg -actn restore -bckp "%~dp0\ExperimentACL.txt" -silent

reg delete HKCU\Software\Microsoft\Office\16.0\Common\Experiment\excel /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\Experiment\outlook /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\Experiment\sdxhelper /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\Experiment\word /f

reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\ApplicationUpgradeCandidate /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\Ecs /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\ExternalFeatureOverrides /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\FirstSession /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\FirstSessionUpgradeCandidate /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\SDXInfo /f

reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\all /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\excel /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\outlook /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\sdxhelper /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\unknown_app /f
reg delete HKCU\Software\Microsoft\Office\16.0\Common\ExperimentEcs\word /f

This is the ExperimentACL.txt file:

"current_user\Software\Microsoft\Office\16.0\Common\Experiment",4,"D:AI(D;CI;DCLCWDWO;;;OW)"
"current_user\Software\Microsoft\Office\16.0\Common\ExperimentConfigs",4,"D:AI(D;CI;DCLCWDWO;;;OW)"
"current_user\Software\Microsoft\Office\16.0\Common\ExperimentEcs",4,"D:AI(D;CI;DCLCWDWO;;;OW)"

Good lord, that's ughhh

But users aren't complaining now. 🙂

That's all that matters. 🙂

https://support.microsoft.com/en-us/office/error-something-went-wrong-1001-signing-in-t[…]-desktop-applications-6f63238d-d83c-437c-a929-de72fe819793 Microsoft updated the article. Fixes are coming. I see where I also may be roaming some some registry data I shouldn't be...