About this article
This article explains an issue identified when using a specific version of WebView2 that causes Templafy add-ins and Templafy Desktop to fail and as a result not be accessible. Microsoft has released WebView2 versions greater than the affected version 95.0.1020.30 in which the issue has been fixed.
Affected Templafy users will see the following messages in Templafy Desktop, Composer and add-ins.
A Settings Warning message appears with an "Unhandled Exception has occured in a component in your application. If you click Continue, the application will Ignore and attempt to continue".
Templafy Composer and add-ins
A message headed Microsoft Office Application Add-in. An unhandled exception occurred in your application. Contact your administrator or the author of this document for further assistance.
Templafy work around
Templafy has added a Microsoft approved work around to Templafy Desktop and Templafy add-ins. The fix is available on the Insider release plan. More about the Insider release plan can be found here https://support.templafy.com/hc/en-us/articles/360017017298-Insider-release-plan. Below, you will find version numbers in which the work around can be found in Templafy One and Templafy Hive.
|Templafy One||Templafy Hive|
|Templafy Library add-ins||7.0.222||7.0.222|
|Templafy Email Signature add-ins||7.1.7||7.1.7|
Non Templafy work around
Change the BrowserSignin policy value
While Microsoft continue working on a fix, they have provided the following work around.
IT teams, group policy management teams or deployment teams should follow the advised steps to change the policy value of BrowserSignin from 2 to either 1 or 0 if you see this REG_DWORD in the following registry location.
More information about this policy can be found in this Microsoft Knowledge Base article https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#browsersignin.
Upgrade WebView2 version
Webview2 can be upgraded to a newer version than 95.0.1020.30 from here Webview2 - Microsoft Edge Developer.
Additional discussions of the problem can be found in the below GitHub posts. The first link is that of Microsoft's summary of the identified problem, work around and timeline for fix.