This is somewhat related to my previous question, Why do installed fonts disappear after reboot?.
Having got the font install issue sorted out under XP just fine, recently we've got a Windows 7 workstation and I've created a special GPO for it. Initially it was UAC that was demanding administrative access to C:\windows\fonts despite the fact the policy dictates that directory is writable (as is the relevant registry entries, on XP anyway). The issue now though is that when I try to copy a font or hit install it claims that the font "does not appear to be a valid font". This happens with every type of font as well.
Is there some new and special consideration when allowing these changes on Windows 7?
Any input would be appreciated.
Many thanks, Doug
So I figured it out.
Having looked at the Resultant Set Of Policy and seeing nothing untoward there, I checked C:\windows\security\logs\winlogon.txt
The Windows 7 client GPO is a copy of the standard XP one that I created, and therefore had entries in it to allow domain users to edit the content of C:\windows\fonts.
However, Windows 7 shows this in winlogon.txt:
I checked the GPO and removed the settings for this directory and re-added it, which upon a GPO update and restart gave me this:
I tried adding a font and voila! Worked as intended.
Hope this helps anyone else who may come across the same issue. No idea why re-adding the same security setting made it work but it did.
Well I can only suggest you have the UAC turned off because I have taken ownership and set the Windows 7 font directory and registry key permissions to allow users change access but the UAC keeps prompting for administrator credentials.
This error occurs because the file attribute
System
is checked. Checked directorys atSystem
cannot have their permissions changed. In my case I try these following command:To correct these error below:
You could try to use the Silent Install Builder from Apreltech at https://www.silentinstall.org/. This program builds MSI or EXE packages containing a font registry scripts. You could deploy Silent Install Builder's MSI through GPO.
Login with Admin account first