Hi @darko.kuzmanovic,
Thanks so much for the reply and the information, I appreciate it.
I just checked and, indeed, I run the version 24H2.
A bug like this would make a lot of sense coming from a Windows update 
I tried to see if it’s possible to downgrade, but I haven’t made it yet.
Please let me know if you come across a fix.
Hopefully the Fontself team will find the time as well to look into it.
Best regards
Blank Screen on Windows 11
Hi,
Brand new to the forum, having the exact same issue.
Did anybody find a solution to this?
It’s very frustrating!
Thanks in advance.
Hi,
I also have the same problem.
I just bought the extension for Illustrator, but it came with this problem.
I also have the 24H2 version, and I have done all the steps of the help page, even I have downloaded the version of Illustrator 2025 to 2024 and other versions, and I still have the same problem.
Besides I have modified details in Regedit (as the help page pointed me), but there is no result.
I hope a solution as soon as possible.
Greetings.
1 Like
Sadly there’s no further information on my side.
Still can’t use Fontself for over 2 months now and there seems to be no response from the Fontself team or any of the support agents in the forum, like @franz despite this issue apparently being a bug that many users face.
I really hope they are working on it.
I will personally wait for a few more weeks and, if there’s no response, I’ll have to ask for a refund.
Hi again. I bring news.
I have managed to revert my Windows 11 edition to 23H2, and as @darko.kuzmanovic mentions, the extension works correctly (even in the latest version of Illustrator 2025).
It seems that the latest update (24H2) has several errors since it was released to the public, so much so that it looks like an Insider Preview edition (a test edition).
However, I have seen other configurations with this version (23H2) and everything is correct. Everything points to the fact that the problem is not the extension, but it is the operating system.
Now, the thing is, if you already have the 24H2 edition, and you can’t go back to 23H2, you will have to completely format your PC. But be careful, as Microsoft currently only provides the 24H2 ISO, and getting the 23H2 ISO is quite an ordeal (even more so when looking for a reliable source).
I hope I have been able to contribute something.
Greetings.
Thanks @DBecerra.Ofi for the insights. We’ve been investigating the issue on our side as well but we haven’t been able to reproduce this problem on the latest Windows 11 edition 24H2, so it looks more like a Windows-bound bug.
Apparently there is a 10-days period during which you can revert to 23H2 version but Microsoft doesn’t provide a way to do it afterwards, which is very unfortunate but totally out of our control.
We are still investigating and will keep you all updated once we’ve found out anything more actionable.
Thanks for your patience and understanding.
1 Like
Hello to all. I have the same problem but I use windows 10. My log file returns this error:
2024-11-09T09:32:59.502Z - info: getClipboardText()
2024-11-09T09:32:59.541Z - warn: Oops, unable to read clipboard
2024-11-09T09:32:59.541Z - error: Error: spawnSync C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\fallbacks\windows\clipboard_x86_64.exe EACCES
at __node_internal_captureLargerStackTrace (node:internal/errors:415:5)
at __node_internal_errnoException (node:internal/errors:545:12)
at Object.spawnSync (node:internal/child_process:1086:20)
at Object.spawnSync (node:child_process:666:24)
at Function.module.exports.sync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\node_modules\execa\index.js:334:30)
at Object.pasteSync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\lib\windows.js:15:30)
at Object.exports.readSync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\index.js:48:38)
at a1J (http://127.0.0.1:4770/js/app.min.js:208:555563)
at Object.getClipboardText (http://127.0.0.1:4770/js/app.min.js:208:561153)
at f2i. (http://127.0.0.1:4770/js/app.min.js:208:238535)
at f2i.eUi.$emit (http://127.0.0.1:4770/js/app.min.js:539:32944)
at Function.sendEventWithData (http://127.0.0.1:4770/js/app.min.js:208:282992)
at http://127.0.0.1:4770/js/app.min.js:208:237239
2024-11-09T09:32:59.569Z - warn: Oops, unable to empty the clipboard
2024-11-09T09:32:59.569Z - error: Error: spawnSync C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\fallbacks\windows\clipboard_x86_64.exe EACCES
at __node_internal_captureLargerStackTrace (node:internal/errors:415:5)
at __node_internal_errnoException (node:internal/errors:545:12)
at Object.spawnSync (node:internal/child_process:1086:20)
at Object.spawnSync (node:child_process:666:24)
at Function.module.exports.sync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\node_modules\execa\index.js:334:30)
at Object.copySync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\lib\windows.js:14:29)
at Object.exports.writeSync (C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.fontself.maker.v2\node_modules\clipboardy\index.js:45:14)
at a1J (http://127.0.0.1:4770/js/app.min.js:208:555675)
at Object.getClipboardText (http://127.0.0.1:4770/js/app.min.js:208:561153)
at f2i. (http://127.0.0.1:4770/js/app.min.js:208:238535)
at f2i.eUi.$emit (http://127.0.0.1:4770/js/app.min.js:539:32944)
at Function.sendEventWithData (http://127.0.0.1:4770/js/app.min.js:208:282992)
at http://127.0.0.1:4770/js/app.min.js:208:237239
@Nikos This is an issue related to the clipboard access, you can fix it by following the steps described here: https://help.fontself.com/en/articles/923399-extension-panel-is-empty
Hi,
I got the exact same issue as well. Is there any news on how to solve it?
Same problem here. Brand new Windows 11 machine.
Hi everyone.
Same issue here on one machine (Surface 9 Pro). As we can have 2 installs, I have it on my desktop and my surface. Both are running Windows 11 Pro 24H2. It works fine on my PC, but just a blank panel on my Surface 9 Pro, which is more than capable of running Photoshop and Illustrator. I have no issue with any other software, so something is stopping the panel from loading. It shows a quick message saying loading panel, then nothing. Sat with it for 32 mins and it didn’t load, opened and closed Illustrator a couple of times and rebooted. At home I have a 1.5gbps internet connedtion, on the train I use a satalite connection (internet is the same, just that it satalite connection instead of ADSL. I switched to my cell mobile hotspot via 5G, and nothing. It’s still blank.
I work on the train travelling to different locations, so working on the go is a must for me. Currently, I can not complete my current project with Fontself. If It is a known issue, as it has been mentioned a lot here, there should be a warning before purchase. I’ve had to buy High Logic FontCreator because I need to complete my current project on the move.
Surface Pro is an Intel i7, 32gb Ram, and a 2tb SSD (upgraded).
Home PC is a i9 i9-14900K 6.3ghz, with 256gb Ram and a RTX 4080.
Also, when verifying my email here, Bitdefender flagged the link with mismatched certificates. Possible false positive, but whoever runs the site may need to update their SSL certs or issue a new one on the subdomain.
Is the developer on here? do you know what’s going on, and will there be a fix? As a new purchase today, I may have to request a refund, which is a shame as I have seen and read good things about Fontself.
Mike.
Edit: It’s the same in Photoshop, a blank panel. I have other panel addons installed in Photoshop, 6 different ones and they work fine. I also saw the link about the clipboard. Mine is already off and everything is allowd in the firewall.
Sorry to hear. If none of the solutions described here work, then it’s difficult to know what’s specific to your setup (as it could be an issue with a firewall, an antivirus, the Internet provider, the operating system, etc.).
But if you cannot make it work we will do the refund, just let us know. @M1cr0ft
Yes, they’re all done with the firmware and updates via Windows Update. All software and drivers are current. And it’s the public version of Windows 11 Pro 24H2, and not a insider release.
I’ll keep trying for a solution, but I may have no option if we can’t find a fix. Which is a shame. I’ll be in touch if I can’t resolve the problem.
@M1cr0ft as you can see, this thread was opened nearly 4 months ago and to this day there has been no fix or at least interest or effort for the issue to be fixed.
All we keep receiving is a copied/pasted standard troubleshooting reply although it is obvious that it has to do with the plugin not functioning on the new Windows 11 Update.
I am not a skilled pc guy - I am just a graphic designer - but this absence of interest in fixing a simple bug all this time indicates a lack of professionalism and respect to the users.
It had been an amazing tool for me and all those who used it I believe, however it was left abandonded to simply rot. Because it does not pay the developpers anymore.
And that’s why we have all these super-expensive subscription-based applications nowadays. At least they function.
So, I guess we will have to move to FontCreator or maybe here’s the idea for a new app for someone to develop!?
Such a pity
Regards,
Michalis G
@michalis We have had several exchanges about this and—as previously explained—this issue can originate from several misconfigurations (hence the detailed articles about potential fixes, which solve most frequent cases) and some OS hiccups (but we and others have been able to use the extension in the newest Windows versions, which makes it hard to detect every single case). You are welcomed to find alternative solutions that will suit you best.
At present, I’ve not had a lot of time to investigate the issue. I’ve spent half of my life creating visual effects and design for major movies and tv shows, the other half is with Microsoft. If we have other addons that connect to the internet, with no issue, via some form of wrapper, there’s no reason that fontself would do the same. Granted, developers all use different methods. My Surface Pro has the same security and setup as my main PC, so in theory, there should be no issues, but there is. As previously stated, both are running Windows 11 Pro 24H2.
What is a concern to me are the warnings I keep getting clicking on the links to this forum, and I also wonder if the issue could also be related to a SSL issue via the addons. But it is odd that It works on one machine but not the other, with the exact same settings. But the question to be raised is it’s not just one user that is being affected, but multiple, and some with Windows 10 and 11. The developer is quite correct that these things do happen, but I hope that this issue will be investigated, and not left to rot. It’s also something that Adobe frown upon. I don’t want do be that person who asks for a refund at every hiccup. I believe in giving chances to resolve a problem. But there’s only a certan period of time for this and if there’s no active development on Fontself, or an active effort to find a cause for this, then as I stated in my other post, I might not have much of a chilce.
Thanks @M1cr0ft for the details, as you state yourself it’s difficult to understand why 2 identical configurations behave differently, one running the extension normally while the other blocks.
The exhaustive list of solutions form our docs adresses a wide range of issues that are beyond the scope of the extension itself, which is the nature of complex inter-dependent software, and should hopefully demonstrate our care for our users.
We totally understand this might not be a sufficient, and repeat that anyone who cannot get any value from our software can (and has always been able to) get a refund.
New here but having all the same problems on a new PC with OEM Windows install. What I’m finding that I haven’t seen mentioned is I do get the Fontself extension window to show the dialog box when “Report a Bug” is selected. Same behavior for Publisher.
Also, nodejs is not listed in the firewall before and after I installed that App.
Node.js — Run JavaScript Everywhere