Closed Skylark13 closed 7 months ago
Windows 10 22H2, same problems. Thanks for your sharing!
Thanks for reporting the issue, but I cannot reproduce this bug on my end (Windows 10 23H2) at the moment.
Additionally, installing/updating fonts without the -g
flag should work because we reverted the changes in PR #200 with PR #227. (Details for the implementation can be found at https://github.com/matthewjberger/scoop-nerd-fonts/issues/198#issuecomment-1488996737)
I will try to set up a Windows 10 21H2 VM this weekend to see if there are any issues.
Edit:
Feel free to share more information if you encounter this bug, as additional details will assist in addressing and resolving the issue more effectively.
Thanks!
I am not on 23H2 yet (I just updated to 22H2 yesterday), maybe something is different there. But as far as I know, I have PR #227 and it was giving me the errors above yesterday.
Perhaps to repro it, you need to reboot between installing the font and trying to update it? I don't know.
Hmmm, actually, I uninstalled the font through scoop and rebooted yesterday, and today I tried to install it (without -g, as an additional test) and it still failed with the same issue. I wonder if it's a local problem, perhaps because (a long time ago) I had installed those fonts manually before I ever installed them through scoop? I'll attempt to delete them manually, and then retry and report back.
Sorry for the noise!
OK, I think this was indeed a local problem. What I did:
I could not delete the font files manually from C:\Users\username\AppData\Local\Microsoft\Windows\Fonts
, they were in use by "System". I had to delete references to them in the registry (which were under HKEY_USERS\S-1-5-21-2876648415-106451411-856188508-1001\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts
), then reboot, then I could delete them.
Then I could install the font using scoop without running into those error messages.
Note that updating the font from a console which uses the font still failed with the same error. I think this is expected. I just had to start a cmd.exe or another shell not using that font, and then the update went through without error. Similar to when updating pwsh or WindowsTerminal, I'll have to keep an eye out using scoop status
when there is an update to the font, and update it in another shell instead of the one I use normally which uses the font.
Thanks for the quick support and hope this helps someone else even though it wasn't an issue with scoop in the end.
Hello,
I saw this closed issue #198 Also this merged PR #200
However, I am on Windows 10 21H2 and I am getting the following when I try to update CascadiaCode-NF:
So it seems even on my version of Windows, we cannot update fonts installed at user level. I am thinking the same fix that was done for Windows 11 22H2 should be done for all versions of Windows, as it seems the same problem applies (according to this Stack Overflow answer stating "This behaviour was introduced with a security update released in August 2014")
https://stackoverflow.com/a/27681134
I cannot explain why no one else has reported this before. Perhaps everyone knew to install fonts with the -g flag, except me 😕
For now I will uninstall the font, reboot, and reinstall it with the -g flag to install it for all users. That should fix my problem. But I wanted to report the problem.
Thanks!