Skip to main content
HelloImJAG
Inspiring
November 15, 2017
Answered

Updated XD, can't modify/add text = crash

  • November 15, 2017
  • 12 replies
  • 8675 views

Device: Surface Pro 3
Edition: Windows 10 Pro

Version: 1709 (I updated from 1703 because problem also affected that)
OS Build: 16299.64

From what I saw I can do everything except add or modify text. I created a new blank .xd file and I couldn't add text there either.

Timeline
Updated XD 2.0BUG
Uninstall/Reinstall x2
Update Windows
Uninstall/Reinstall
Windows 10 Fall Creator Update

Uninstall/Reinstall

No Luck

Question: Is there a way to revert update or pick a XD install version?

This topic has been closed for replies.
Correct answer elainecc

We just released XD 2.1, which fixes this issue. If you don't see the update immediately, launch the Creative Cloud desktop application, click on the ... button in the upper right hand corner, and select "Check for App Updates." Thanks again for your patience as we worked to resolve this issue!

-Elaine

12 replies

elainecc
Community Manager
Community Manager
November 15, 2017

We're also tracking this issue here: Adobe XD Version 2.0 crashes when double clicking text

db14555488
Participating Frequently
November 15, 2017

I am having the identical issue - was working fine until latest update. me and an adobe customer support staff are working through it at the moment. will post here when we find a solution. Unfortunately it isn't possible to roll-back to prev version for XD.

HelloImJAG
Inspiring
November 15, 2017

Thanks for sharing, hopefully we find a solution soon as nothing I've tried has helped.

db14555488
Participating Frequently
November 15, 2017

no prob. ok so we spent about 3 hours debugging - we traced the error to a dll file: if you hit windows key and type "event viewer" and expand errors and double click you'll see the following amongst the error messsage: Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll. We tried replacing it with other copies, as well as forcing permissions via power shell. that rules out any permissions issue with the dll. The issue has been raised to the next level and they are investigating. I'm a developer myself, and from seeing the similar issue that another user had caused by adobe typekit, my spidey-sense tells me it could be issue to do with a failed API request that occurs when the text tool is used. That is complete speculation ofcourse. will be interesting to see what the error is caused by and how they fix it. will post here when I know more.