Forum Discussion
Outlook Insider not starting
16.0.15330.20004 is now out, but it takes a while for "Experiments" to return so I don't know if it's fixed or not. Someone who never deleted Experiments would know.
Update: Looks like the problem is still there. Upon further testing, at least here it relates specifically to 1.28 here:
HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\Ecs\outlook\ConfigContextData
I would suggest just deleting 1.28, if you have it.
David Overton xyzxyzxyz With a workaround as a stopgap (see above), I'm starting to wonder why I see this problem with some and not others when everyone is using an Exchange account.
Do you have any ideas? Could the version of Windows be involved? What are you running? It does happen that the one having the issue is on Win11 Dev (25xxx) while the one who doesn't is on Win11 22H2 (22621), but I find it hard to believe that's it.
It might also be something about the Exchange account, as there are countless variables there, but we've tried multiple ones (in different profiles) and that so far hasn't been the answer. It remains consistent one way or the other: always a problem or never one.
- David OvertonJun 03, 2022Copper Contributor
rpodric It is definitely more complex.
I created another user on my system and could not repro the issues once I joined all the accounts. This suggests it is a profile specific issue as the other user had access to the same accounts, but e-mail worked fine.
What I can say is that I've done a clean install of the latest Windows 11 Dev build and the issue has gone away. I can say I was able to stop the problem for a while by removing accounts from "Settings / Accounts / E-mail & Accounts", so it sounds linked, but in the end, a clean install solved my problem. Same OS, same Exchange, same accounts, same Office - different result.
- rpodricJun 03, 2022Bronze Contributor
Yes, by coincidence I was going to try another Windows profile today (and still will). Sounds like that will work, which does make some sense given the evidence, but it's hard to connect that with the Registry hack that I mentioned, which is extremely Office specific. I can't even imagine what it could be about Windows suddenly that Office is objecting to, but it must be something.
(Previously, I had tried doing the other thing you mentioned: removing the registered account in Windows Settings, as a logical step before creating a new Outlook profile, but that wasn't the answer.)
It sounds like the problem started for you with a Dev build upgrade. That's something that I was never sure about here, since I did a Dev build upgrade and 15321 in very close proximity to each other. I've yet to find any mention of the issue in Feedback Hub, and you would think that someone would have mentioned it there even if it's not really a Windows problem but more a Windows ricochet.
I won't be doing a Windows clean install, that's for sure (you're more ambitious than I).