I've been told that this is an ongoing issue which has been addressed and that is known with Adobe XD on MS Windows 10.
Even though most of the troubleshooting tips are inclined to instruct the users to perform an update of XD to its latest version and/or a simple restart of their system to fix it, I am more inclined to suuport the other users who have exhausted all other tips available in the forums.
If we look the Adobe XD Release Notes, system requirements https://helpx.adobe.com/xd/system-requirements.html we can clearly see that Adobe XD is an app supported in 64bit operating systems with 64 bit supported processors.
Using this logic as an troubleshooting approach, let's remember that in MS Windows 64-bit programs are installed in the “C:\Program Files” folder and 32-bit programs are installed in “C:\Program Files (x86)” folder.
However, the systemwide module (.dll) libraries that belong to 32-bit programs and 64-bit program are handled quite differently between the application and the operating system, and they are separated into two different folders.
In any case, from examining the different crash dumps that users are sharing, one out of three events is always identified consistently by the error event handling in MS Windows : the faulting applicattion name " XD.exe" or "XD CC.exe".
If we take as an example any of the Adobe XD's crash logs that Adobe XD users are submitting, thereare two areas of interest in the crash dumps are:
- The exception code: it varies from user to user (0xc0000008, 0xc000027b, 0xc0000409 for example)
- Faulting Module name(s): it varies from user to user (ntdll.dll, twinapi.appcore.dll)
Now, even though the exception code and the faulting module events vary from user to user, there is another area that seems to also remain constant. That is the application's faulting path C:\Windows\System32
So going back to what I said earlier about where 32 and 64 bit programs are installed, you should be asking yourself "What heppened to C:\Windows\SysWOW64 ? Did we forget about it?"
System32 is the system wide library folder in MS Windows. However, keeping in mind that Adobe XD is a 64bit app, why is it trying to load or register a module (.dll) in a known area that is reserved for 32bit apps when it is loaded up ?
That said, and in spite of the growing clutter of troubleshooting threads that I've seen in the community forums, I would like to highlight a few suggestions to work around this fault exception.
If a 64 bit (.dll) module is failing to load you can re-register that server module using this command : regsvr32 followed by the .dll module name.
EXAMPLE: You will need to open the command prompt, prefereably as Administrator go to C:\Windows\System32. Then type regsvr32 twinapi.appcore.dll and hit Enter.
like this C:\Windows\System32 > regsvr32 twinapi.appcore.dll
OR,
If using Windows Explorer you can also copy twinapi.appcore.dll and paste it in
C:\Windows\SysWOW64 then repeat the step above in the SysWOW64 directory:
C:\Windows\SysWOW64 > regsvr32 twinapi.appcore.dll
NOTE: Conversely, you can use /u parameter to unregister a module
As I read in a post outside if the Adobe forums, the tricky part is to always remember that that the 32-bit .dll should be registered into C:\Windows\SysWOW64, and the 64-bit .dll should be registered into C:\Windows\System32. This is a little different than following the logic of "64-bit programs are installed in the “C:\Program Files” folder and 32-bit programs are installed in “C:\Program Files (x86)” folder".
To explain how virtulal memory addressing is handled between the OS and the application is beyond the scope of this tip. And to explain how System32 and SysWOW64 works is also beyond this scope but I hope that the suggestions above could help someone.
2 Correct answers
495
Replies
AdChoices