Installed fonts require reboot - Win10

[GlenT]

This is what our font looks like after installation, and before Win10 reboot:

FontWin10.png (134.55 KiB) Viewed 9365 times

[Daniel]

Hello Glen,

Please schedule your "SetProperty" custom action after "Install Execution Stage -> Searches" action group.

Regarding the shortcut icon it appears on your installed font (installed in WindowsFolder\fonts directory) this happens because the source file of your installed fond is in another directory than "WindowsFolder\Fonts" one. If you want your font source file to be installed directly in Windows Fonts folder, then please go to "Files and Folders" page and drag your font file under "Windows Volume\Windows\Fonts" folder. Let us know if this helped.

All the best,
Daniel

[GlenT]

If you want your font source file to be installed directly in Windows Fonts folder, then please go to "Files and Folders" page and drag your font file under "Windows Volume\Windows\Fonts" folder. Let us know if this helped.

That is the location that we have been using all along:

WindowsFontsFolder.png (26.21 KiB) Viewed 9358 times

[GlenT]

Please schedule your "SetProperty" custom action after "Install Execution Stage -> Searches" action group.

Moving our Custom Action to this location did not work. Still no reboot. I suspect that the action "Force" may not exist in AI Pro.

[Daniel]

Hello Glen,

Please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them.

If you cannot share with us your project file, then you can try to isolate the behavior in a buildable sample (.aip + its referenced files) which we can build and test on our side.

All the best,
Daniel

[GlenT]

OK, AI project and log file have been sent.

Note that I experimented with creating a new AI project that only installed the font file and nothing else. This succeed, both in installing the font while successfully without requiring a reboot, and in requesting a reboot after the install was completed.

We use a third-party merge module in our installations which installs some drivers. I suspect that calling this merge module at the end of installation interrupts our the reboot request and possibly the font installation. Maybe the log file will show something.

[Daniel]

Hello Glen,

I apologize for my delay.

I've finished investigating your setup project and it seems the font installation issue might be cause by the permissions you set on your font file from the "File Permissions" tab. Please note that when the "Keep existing permissions" flag is not checked the permissions are set by using the standard Windows Installer actions. I'm not sure why but it seems when using the standard Windows Installer mechanism to set permissions the font file is registered only after the system is rebooted.

When the "Keep existing permissions" flag is set a specific Advanced Installer custom action will be used to set the permissions at install time and from my test when this flag is set the font file installs as expected without needing a system reboot. So, can you please check the "Keep existing permissions" option for your font file, rebuild the project and see if this helped?

Regarding the reboot prompt issue, this indeed is caused by a limitation of our Enhanced User Interface feature. When the EUI is enabled you can trigger a reboot prompt message after installation only by using our "Dialog Editor" feature (available only in the Enterprise edition) as it is explained in "Conditional Restart" forum thread.

Let us know if this was of any help to you.

All the best,
Daniel

[GlenT]

Daniel, setting the Keep Existing Permissions flag on the font file does seem to work. In my single test with Win10, the font file did install and was available for use without requiring a reboot. I will continue testing to see if this has any negative effect on other versions of Windows (other than Win10).

Regarding the reboot prompt issue, this indeed is caused by a limitation of our Enhanced User Interface feature. When the EUI is enabled you can trigger a reboot prompt message after installation only by using our "Dialog Editor" feature (available only in the Enterprise edition) as it is explained in "Conditional Restart" forum thread.

From your other comments on reboot, I was able to use the Custom Action to invoke a reboot request with a bare AI project installing only the font file using the Professional AI project type, so I am not really clear on this. Hopefully, I will not need it if the Keep Existing Permissions flag works.

[Daniel]

Hello Glen,

From your other comments on reboot, I was able to use the Custom Action to invoke a reboot request with a bare AI project installing only the font file using the Professional AI project type, so I am not really clear on this. Hopefully, I will not need it if the Keep Existing Permissions flag works.

Yes, you are right. I gave you incomplete information. I have to rephrase, you can conditionally trigger a reboot using a custom action in a "Professional" project type only if you have the "Enhanced User Interface" feature disabled. When our EUI is enabled the only way to conditionally trigger a reboot is to use our "Dialog Editor" feature as it is described in our "Conditional Restart" forum thread.

Please accept my apologies for my previous incomplete answer regarding the conditional reboot solution.

All the best,
Daniel