RogerBin

In the end I took advise that suggested there could be conflicts between maintaining both installs so I deleted the MSIX Sandbox version 1st and then installed the MSI/EXE for each of the 3 programs. It worked out good. My previous settings were in tact and add-on included or easily added back. I had found that by going to your account (>Help > Account) - via Affinity in my case - that all of my add-on where easily restored or added from there. I actually found there were some I forgot to install so this worked out well for me.

Could someone define what the context of 'user content' in this thread addresses? I searched Affinity for User Content but the best I could figure is that this may be the external links to content in a project file versus embedded... images linked versus embedded which I understand. Yet, this sounds like something different?

I'm a little confused with 'user content' being an issue. Does this mean that content files I created with the MSIX version (afphoto, afdesign, and afpub) wouldn't open with the MSI/EXE installed version - or does that mean add-ons? My advise from an Affinity FB message said to delete the MSIX 1st because there can be compatibility issues between them. I'm not concerned about setting or add-ons, so that wouldn't be an issue for me.

Should the Universal versions of Photo, Designer, and Publisher be uninstalled before installing the EXE versions? Or, will they be deleted from the Windows Sandbox during install? I use these with Reallusions CTA and iClone and looking for fuller integration.

Glad you mentioned the rogue file. I imported an indd In Design file file to Publisher but got the same export error. In my case I'm guessing it was a linked file that got move, and fortunately images in just the 1st two pages, So, I just replaced the two images. The conversion process sure worked slick, and I'm glad to be free from idml and indd.