Help! I can't open files in Photoshop CS6

[bnies813]

I am having a strange/frustrating problem with Photoshop CS6 and I don't know how to fix it. I can't open an existing file and I can't create a new file. It was working fine about a week ago and now this!

Photoshop launches and I can stare at a blank application as long as I want or go to preferences and mess around with settings, but when I try to open an existing, or create a new file, it looks like it's about to open, I'll get the "update fonts" box and everything, but then PS completely shuts down. No warning, no error or anything. I take that back, at first I was getting an error about the file being created using a different text engine. I got that error to go away, but PS still shuts down when I try open or create files.

I work on a Windows 10 PC.

I tried the following:

• Uninstalling/reinstalling
• Changing the Compatibility Mode
• Running as Admin
• Resetting preferences

Please help! I need Photoshop for some client work I'm starting. Worse comes to worse, I have a mac I can use for my PS work, but I really don't want to be working off two computers at once.

[JJMack]

All files or particular files. It sounds like you tring to open Files that have compatibility probelm's and fonts need to be Updated but Photoshop crashes instead of updating some fonts,

[bnies813]

The issue happens with all files. Even when I go to File-->New

[bnies813]

Hallelujah!!! It's working again!!!!

The issue was either a Windows Defender issue or a conflict with Duet Display.

I thought it was a Windows 10 Build 1803 related issue, but I found a file I was working on AFTER that build installed, so that wasn't it. Then I remembered I installed a program about a week ago, (Duet Display) to be able connect my iPad as a second monitor. I uninstalled Duet, restarted, opened PS, got a message from Windows Defender about features being blocked, tried opening a file and viola!

I am so relieved it's working again! I am now about to do a full system scan, just to be sure there's nothing else wrong.

Thanks JJMack, but all seems to be good now.