Outlook crash on Azure AD Joined Windows 10

%3CLINGO-SUB%20id%3D%22lingo-sub-265351%22%20slang%3D%22en-US%22%3EOutlook%20crash%20on%20Azure%20AD%20Joined%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265351%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20maybe%20someone%20encounter%20similar%20problems%20when%20live%20natively%20in%20Microsoft%20365%20on%20Azure%20AD%20Joined%20Windows%2010%20and%20Outlook%20from%20Office%20365%20ProPlus.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOutlook%20crash%20on%20start%20with%20%22%3CEM%3EThe%20unexpected%20error%20occurred.%3C%2FEM%3E%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20reason%20for%20this%20can%20be%2C%20that%20you%20have%20Azure%20AD%20Display%20Name%20attribute%20filled%20with%20special%20characters%20or%20some%20local%20alphabets%20(like%20here%20in%20Czech%20Republic).%20Windows%2010%20support%20Unicode%20for%20local%20user%20profile%20path%2C%20but%20some%20apps%20no.%20And%20one%20of%20them%20is%20Outlook%20currently%20unfortunately.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENice%20workaround%20is%20rename%20account%20before%20joining%20machine%20or%20rename%20path%20in%20registry%20manually%20after%20enrollment.%20I%20made%20just%20a%20quick%20%3CA%20href%3D%22https%3A%2F%2Fkazzan.wordpress.com%2F2018%2F09%2F14%2Foutlook-crash-on-azure-ad-joined-windows-10%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eblog%20post%20about%20this%20issue%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-265351%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Windows%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824001%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20crash%20on%20Azure%20AD%20Joined%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824001%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F746%22%20target%3D%22_blank%22%3E%40Petr%20Vlk%3C%2FA%3E%2C%3C%2FP%3E%3CP%3EUnfortunately%20we%20encountered%20the%20same%20issue%20with%20the%20Windows%20build%26nbsp%3B%3CSPAN%3E10.0.18362.239.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ESo%20this%20is%20not%20fixed%20as%20you%20write%20in%20your%20blog%20post.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENever%20mind%20thank%20you%20for%20the%20workaround!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20shame%20on%20you%20Microsoft%2C%20that%20kind%20of%20error%20in%20the%2021st%20century%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824057%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%20crash%20on%20Azure%20AD%20Joined%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824057%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F183145%22%20target%3D%22_blank%22%3E%40Martin%20Trn%C4%9Bn%C3%BD%3C%2FA%3E%26nbsp%3BHi%2C%20should%20be%20fixed%20by%20Outlook%20team.%20Windows%20still%20behave%20the%20same%20to%20today%20builds.%20Unfortunately.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20of%20the%20possible%20solution%20is%20make%20a%20dummy%20AD%20and%20sync%20the%20SAMAccountName%20attribute%20to%20AAD%20which%20Windows%20will%20then%20use%20for%20local%20user%20profile%20path.%20But%20I%20know%2C%20for%20the%20cloud%20only%20scenario%20it%20is%20not%20so%20cool.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20just%20talking%20to%20AAD%20and%20Windows%20teams%20to%20get%20this%20addressed.%20If%20you%20can%20also%20create%20ticket%20or%20at%20least%20escalate%20if%20you%20have%20some%20your%20contacts%20in%20Microsoft%2C%20will%20be%20appreciated.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
MVP

Hi, maybe someone encounter similar problems when live natively in Microsoft 365 on Azure AD Joined Windows 10 and Outlook from Office 365 ProPlus.

 

Outlook crash on start with "The unexpected error occurred."

 

The reason for this can be, that you have Azure AD Display Name attribute filled with special characters or some local alphabets (like here in Czech Republic). Windows 10 support Unicode for local user profile path, but some apps no. And one of them is Outlook currently unfortunately.

 

Nice workaround is rename account before joining machine or rename path in registry manually after enrollment. I made just a quick blog post about this issue.

2 Replies
Highlighted

Hi @Petr Vlk,

Unfortunately we encountered the same issue with the Windows build 10.0.18362.239.

So this is not fixed as you write in your blog post. 

 

Never mind thank you for the workaround! 

 

And shame on you Microsoft, that kind of error in the 21st century?!

Highlighted

@Martin Trněný Hi, should be fixed by Outlook team. Windows still behave the same to today builds. Unfortunately.

 

One of the possible solution is make a dummy AD and sync the SAMAccountName attribute to AAD which Windows will then use for local user profile path. But I know, for the cloud only scenario it is not so cool.

 

I am just talking to AAD and Windows teams to get this addressed. If you can also create ticket or at least escalate if you have some your contacts in Microsoft, will be appreciated. Thanks.