We've run usual t-shooting (sfc, dism, desintall-reinstall, etc). I have opened a ticket with support but they are completely useless – hardly managed to schedule a call-back within a week. Report Id: d1e78a5d-2dcd-4313-b547-c41eefe64980įaulting package full name: _1000.17763.1.0_neutral_neutral_cw5n1h2txyewyįaulting package-relative application ID: AppĬ:\Windows\SystemApps\_cw5n1h2txyewy\ Looking into the event log we can correlate this with a crash of įaulting application name:, version: 3.529, time stamp: 0x5cde4ed1įaulting module name: edgehtml.dll, version: 3.1817, time stamp: 0x409d5916įaulting application start time: 0x01d719d23699f2e6įaulting application path: C:\Windows\SystemApps\_cw5n1h2txyewy\įaulting module path: C:\Windows\SYSTEM32\edgehtml.dll Looking into %localappdata%\Microsoft\Office\16.0\Licensing we see that there was no token generated. They enter the username then a blank window pops up for a few second and disappears. We have deployed following using the deployment tool as per this procedure and everything went ok, except that whenever an user wants to launch an app they are prompted to activate with their account. ![]() We are having issue activating O365 on a 2019 RDS Server.
0 Comments
Leave a Reply. |