Font problem

[mv92]

Hi all!

I've been experiencing a weird issue everytime I install a new font: the font works perfectly fine, but every program or folder goes blank (see photos).

I think it all started when fonts I have used for years started appearing as missing, so I reinstalled them to get them to work. Then they would work, but the whole computer would just go blank.

Everything goes back to normal once I erase the new fonts.

Any idea what the problem might be and how to solve it?

Thanks!

[Steve Werner]

To help you, we need to gather some info:

What version of InDesign and exact operating system version?

Does this happen in other Adobe Creative Cloud applications? Does it happen in other applications on your computer?  What kind of fonts (examples, font type) are you installing?

[mv92]

Hi Steve,

So the InDesign version I'm using is the CS6, the operating system is Windows 10 Home (64 bit).

This happens also in Photoshop and Illustrator, and overall on my computer.. wherever there's text (folder names, menus, search bars in browsers) it goes blank. The fonts I install are mainly OTFs and TTFs.

I forgot to mention, for some weird reason if I plug in a projector or my graphic tablet everything goes back to normal. I'm not sure whether the issue is connected to fonts or not, but it usually happens when I install a new one.

Thanks!

[Steve Werner]

I'll let the Windows experts reply. I'm a Mac user. But CS6 may be too old for the Windows 10 version you're using. Let's see what they say.

[MW Design]

Not a Windows "expert," but CS6 runs fine on my Windows 10 installation. The recent spat of updates from MickeySoft has created some havoc, though. Mostly to do with file associations.

Mike

[BobLevine]

Not a Windows "expert," but CS6 runs fine on my Windows 10 installation.

However, I’ve seen too many CS6, CS4 and even CS3 happy users on Win10 machines to consider this as a first candidate to troubleshooting.

Those are not very helpful things to tell someone under these circumstances. It doesn't matter if it works for some people, the fact is, it isn't supported and it's untested. I'll bet if you look around you can find someone running Pagemaker under Windows 10.

There are umpteen releases of Windows 10 between Pro and Home and Microsoft issues updates quite frequently. Any single one could kill a running CS6 install.

The only suggestion that I, as a fulltime Windows user can suggest, is running CS6 under Windows 7 compatibility mode. After that, I'll let others spend their time on this. It's simply not worth the bother.

I take no joy in saying that but it's hard enough to troubleshoot supported installations.

[MW Design]

Your diatribe isn't "very helpful," either.

I was answering Steve in particular, not the OP. And while I have been a lifelong Windows user, and owned a tech support company, I would't still classify myself as an expert, even if it was written as a self-depreciating statement.

I don't know who marked winterm's answer as correct, but it was done. Cannot remember if it was so when I responded or not.

It is clearly a Windows issue and as Exploder has issues, it likely has nothing to do with CS6's ability or lack thereof to run "just fine" on Win10 of whatever favor. I myself am using Win10 Pro. My wife's computer is Win 10 Home and it works fine on it.

Even so, you and winterm are correct. It is not supported on Win10. And should the OP resolve the Windows issues, and if the OP is still having issues, we (likely not you) may be able to aid the OP.

And a fwiw, it is evidently "worth the bother" for the OP.

[BobLevine]

I’m not calling myself an expert, either, but I do know that saying you’re running Windows 10 is meaningless at this point…it’s like someone saying they’re using a Mac. It tells you nothing. There have been seven or so major releases of Windows 10 and then there are monthly build updates and Pro and Home.

Finally, I was speaking for myself when I said it wasn’t worth it to spend time on, but I at least offered a suggestion…something nobody else bothered to do.

[MW Design]

Finally, I was speaking for myself when I said it wasn’t worth it to spend time on, but I at least offered a suggestion…something nobody else bothered to do.

Er. Somebody did offer a suggestion before I wrote my reply to Steve.

As I have reinstalled my and my wife's system a couple few times since Win10 arrived (I do clean installs every once in a while due to alpha & beta testing frequently), and CS6 just installs fine and runs fine, all I have is my experience for which to respond to Steve.

I have no idea whether fixing the OS will resolve the issue or not. But it is the proper first step. This is my last post to this thread unless the OP comes back. Pat yourself on the back, Bob.

[winterm]

Sure, the main point here is that this is a system issue. You can uninstall InDesign at all, and I bet, that glitch still will persist. It's just not InDesign related. That's why Dov Isaacs marked my answer as 'correct', I guess.

[winterm]

Steve, you’re right, CS6 is not officially supported under Win10. However, I’ve seen too many CS6, CS4 and even CS3 happy users on Win10 machines to consider this as a first candidate to troubleshooting.

[Dov Isaacs]

That's right and I believe that this discussion has gone to completion and is being locked now.

          - Dov

[winterm · Accepted solution]

Obviously it's a system-wide problem (just see the 3rd screen shot with Explorer window). That said, InDesign forum is not the best place to look for the answer on this. AFAIK some folks experienced similar issues after Creators Update, or those having Atom Z series processors, or obsolete version of Comodo firewall, … or whatever else.

Being in your shoes I'd perform a system file check first (I'd begin with Option 3), and then look for further possible solutions in Windows forums.