1. Issue

Customer cannot add a custom library by using Types Library Manager in Unity Pro V13. However, customer can add a custom library if the Libset version is set to V12, not V13.1. Customer also has full admin rights on the PC and VM. Reinstalling the Unity Pro doesn’t work as well.

2. Product Line

Unity Pro V13.1

3. Environment

Unity Pro V13.1, Win10

4. Resolution

Manually replacing the custom.db file of V13.1 can fix the issue.
The root cause is the custom.db file is corrupted due to the installation package of Unity Pro which has potential error.

Udgivet til: Schneider Electric Danmark