Skip to main content
Participant
March 11, 2022
Answered

Shared libraries showing something went wrong error since installing latest XD update

  • March 11, 2022
  • 2 replies
  • 612 views

Since me and my team have installed the latest Adobe XD update, we're all getting "Something went wrong initializing creative cloud libraries" errors in our libraries panels. I've tried all of the trouble shooting recommendations by Adobe in https://helpx.adobe.com/creative-cloud/kb/creative-cloud-libraries-panel-doesn-t-load-in-desktop-products.html. Plus, restarted my PC, uninstalled all of creative cloud and re-installed it again. I've reverted back to the previous version of XD and this issue no longer occurs. Has anyone else experienced the same thing?

This topic has been closed for replies.
Correct answer rachaelo54086792

I've managed to speak with Adobe and get a resolution for this issue. They have confirmed they are working to fix this in the next version of Adobe XD. However, the solution (which has fixed my teams PC/laptops) in the iterim is to run the following in Command Prompt:

CheckNetIsolation LoopbackExempt -a -n=adobe.xd_pc75e8sa7ep4e

2 replies

rachaelo54086792AuthorCorrect answer
Participant
March 22, 2022

I've managed to speak with Adobe and get a resolution for this issue. They have confirmed they are working to fix this in the next version of Adobe XD. However, the solution (which has fixed my teams PC/laptops) in the iterim is to run the following in Command Prompt:

CheckNetIsolation LoopbackExempt -a -n=adobe.xd_pc75e8sa7ep4e

Participant
March 22, 2022

*When on the latest version of Adobe XD

HARSHIKA_VERMA
Community Manager
Community Manager
March 22, 2022

Hi rachaelo54086792,

 

Thank you for sharing the solution that worked for you. We'll follow up with the team about this issue and will get back to you if we need further information for the investigation.

 

Thanks,

Harshika

Participant
March 11, 2022

Yes, I've done everything you mentioned apart from reverting to the previous version. Interested to know if anyone has a fix which doesn't involve rolling back - it seems as though some on my team have had the update with no problems but I'm not sure why there's a difference in set-up for us.