Skip to main content
Participating Frequently
October 14, 2021
Question

Font won't deactivate tho indicates it has

  • October 14, 2021
  • 1 reply
  • 703 views

I'm on a Windows 10 OS, having a problem in all Adobe apps (InDesign, Photoshop, Illustrator).

Rather than rely on Adobe's sketchy connectivity issues, we bought 2 fonts (it's been a problem for years, resulting in lost productivity).

We bought the same ones we were "renting" from Adobe, Tisa and Proxima Nova.

I deactivated ALL of the active fonts from Adobe, then installed the new fonts.

I used the Find/Replace Font dialog box in InDesign to replace the Tisa fonts with no incident.

Strangely, I didn't have to do that for Proxima Nova. I figured it was because the font names were the same (slightly different with Tisa).

After many hours of running in circles, I've made zero progress.

I know the programs are pulling the font from Adobe because I can see the path in the Find/Replace Font dialog box (see graphic). Also, the cloud icon is next to the font names in the drop-down list (see graphic).

I unchecked the Auto-Activate box in Preferences > File Handling.

I disabled Adobe Fonts in the CC Desktop Preferences > Services. And it shows no active fonts, as well.

I repeatedly checked on the Web site that all fonts were deactivated (see graphic), tho occasionally it had reactivated a few, which I deactivated yet again..

I've rebooted the computer several times.

And, to add insult to injury, when I open a document with the Proxima Nova font, it automatically reactivates it.

I have a ton of documentation that needs updating with the local version of the PN font.

I'm grateful for any help anyone can provide.

Thank you.

    This topic has been closed for replies.

    1 reply

    Legend
    October 21, 2021

    Disconnect from the Internet and try it. What happens?

    Participating Frequently
    October 21, 2021

    Good idea.

    The font works, but still lists the same path (from Adobe), which is interesting. I have to assume that somewhere in the software there's a glitch that keeps it from showing the correct path.

    Legend
    October 22, 2021