As I have written over and over again, a startup time of several seconds is always caused by a bad UltraEdit configuration or a bad computer configuration. Even on first start after Windows start with the UltraEdit program files not already in cache my much slower computer starts UltraEdit v19.10 in less than 3 seconds.
It can be easily verified if an UltraEdit configuration is responsible for a longer startup time. While UltraEdit is not running, rename in directory
%APPDATA%\IDMComp the directory
UltraEdit for example to
UltraEditBak and start now UltraEdit. UltraEdit recreates now the directory
UltraEdit, creates the standard environments, copies the standard wordfiles and templates from the program files directory to the application data directory, and recreates the other configuration files like uedit32.ini with all settings set to default. You may see all the windows usually displayed only after a new installation. Now close UltraEdit and start it again.
If the restart is fast within one second, the reason for the long startup time must be searched in your previous configuration in the renamed folder, perhaps hundreds or even thousands of history entries because clear history button never used.
If the startup time is still more than 10 seconds, the reason must be searched on your computer. How to do this using Process Monitor from Sysinternals (Microsoft) and what are all possible reasons are explained comprehensive in all existing forum topics about startup time of UltraEdit and therefore I will not explain them here again. Read carefully and completely post by post the topics found by the advanced forum search engine using
startup time long* as search term.