You are using hopefully Windows 10 or Windows 11 as UltraEdit 2025.1 does not start anymore on Windows 7/8/8.1.

It would be better to upgrade to UltraEdit 2025.2 because of copy/cut/paste and hex copy selected view in hex edit mode is not working in UltraEdit 2025.1.0.*, but in UltraEdit 2025.2.0.* and UltraEdit 2025.0.0.* and all former versions.

I recommend doing following:

1. Open in Windows File Explorer the directory %APPDATA%\IDMComp by coping this directory path with Ctrl+C and pasting it into the address bar of Windows File Explorer with Ctrl+V and hitting key RETURN or key ENTER for opening the hidden directory and make a backup of the directory UltraEdit with Ctrl+C and Ctrl+V. Windows File Explorer names the directory copy UltraEdit - Copy. That copy of the entire application data directory makes it possible for you to go back to v2022.0.0.102 in case of being unhappy with v2025.2.0.8 for whatever reason.
2. Uninstall UltraEdit v2022.0.0.102 with unchecking the option Deactivate license and with not checking the option Remove application settings in first uninstall window. That results in an uninstall of all program files of UltraEdit v2022.0.0.102 but keeping the license information and your entire UltraEdit configuration.
   I strongly recommend to make the uninstall of the program files because of there are a lot of changes in the program files folder of UltraEdit and the registration of the DLLs used by UltraEdit.
   It is also necessary to restart Windows after the uninstall for the completion of the uninstall although no extra mentioned by the uninstaller. The Explorer context menu DLLs of UltraEdit cannot be uninstalled (=deleted) directly by the uninstaller because of being used by the Windows File Explorer running as your desktop. The uninstaller registers therefore pending rename operations to delete those files and last the program files directories of UltraEdit during next start of Windows. You want to install next a new version of UltraEdit. Therefore it is necessary to restart Windows now and do not wait until Windows is restarted the next time to finish the installation of a security update (with pending file rename operations).
3. Install UltraEdit v2025.2.0.8 after the restart of Windows and start UltraEdit.
   Your existing UltraEdit configuration in %APPDATA%\IDMComp\UltraEdit is automatically upgraded by UltraEdit on first start respectively first exit. UltraEdit itself makes a backup of the configuration first before update the configuration, but having a copy of the entire UltraEdit application data directory is always best.

Keep the directory %APPDATA%\IDMComp\UltraEdit - Copy for some weeks until you are sure that you will use v2025.2.0.8 in future. Then you can delete the directory copy.

I suggest further reading Recommendations on updating from UE/UES ≤ v2024.0.0.28 to ≥ v2024.0.0.35.

There are some files installed new in the program files folder of UltraEdit or subfolders like the tag list file, some syntax highlighting wordfiles and the language template files which are copied by UltraEdit on first start to %APPDATA%\IDMComp\UltraEdit or subfolders but only if those files are not yet existing in the application data folder or its subfolders. The tag list file, the syntax highlighting wordfiles and the language template files in the application data directory can be customized by a user at any time. UltraEdit does not update an already existing tag list file, or the existing syntax highlighting wordfiles, or the existing language template files. It updates only an existing *.ini file, an existing *.vod file, the *.rb0 file (just the ribbon tabs which the user cannot customize), and some other application data files, but an existing tag list file, existing *.uew files or existing *-tpl.xml files are never automatically updated by UltraEdit.

A user must update such files manually if the user wants to make use of the updated default tag list file, the updated default syntax highlighting wordfiles, the updated default language template files etc. That reads perhaps difficult but it is not as those files are all text files. A text file comparison can be made for that reason to find out which default files can be simply copied from the program files folder of UltraEdit to the application data folder because of not being customized by the user and which default files must be merged into the customized user data files.

I recommend to look on following files in your case with upgrade from 2022.0.0.102 to 2025.2.0.8:

1. %ProgramFiles%\IDM Computer Solutions\UltraEdit\taglist.uet (ANSI encoded) versus %APPDATA%\IDMComp\UltraEdit\TAGLISTU.uet (UTF-16 LE encoded)
2. %ProgramFiles%\IDM Computer Solutions\UltraEdit\template\language\*-tpl.xml versus %APPDATA%\IDMComp\UltraEdit\templates\language\*-tpl.xml
3. %ProgramFiles%\IDM Computer Solutions\UltraEdit\wordfiles\*.uew versus %APPDATA%\IDMComp\UltraEdit\wordfiles\*.uew

Note: The *.uew files never needed should be deleted from %APPDATA%\IDMComp\UltraEdit\wordfiles\ as that speeds up the startup of UltraEdit a little bit. Syntax highlighting wordfiles can be added later easily again at any time to %APPDATA%\IDMComp\UltraEdit\wordfiles\ from either the wordfiles directory in the UltraEdit program files folder or the online wordfiles database of UltraEdit, Inc. There is really no need to keep wordfiles in %APPDATA%\IDMComp\UltraEdit\wordfiles\ just for nothing else than having them in this directory although not used at all. I have since 25 years my own list of syntax highlighting wordfiles and add wordfiles or customize my wordfiles whenever I have a need to do that.

Backup/restore user customizations is designed for making a backup of a user customization to be restored later on same computer or a different computer using the same version of UltraEdit as used on creating the backup. The user can also configure which files to include in the backup in case of wanting to customize just a specific file or a specific set of files  like layouts or wordfiles of the UltraEdit application data and want to be able to restore the initial or an intermediate version of the file or the set of files. But this feature is not designed for making a backup of a user customization of UltraEdit version a.b.c.d and restore it on same or a different computer with UltraEdit version m.n.o.p. The container format is even different between various versions of UltraEdit simply because of big differences in  set of the application data files.

The first two version numbers (major and minor version) must be identical to be able using functional safely backup/restore user customizations. The *.uec files might work also if just the UltraEdit major version is identical between backup and restore, but that is not guaranteed by this feature. It could even work to backup and restore a user customization between different major versions of UltraEdit but that is for most combinations of different major versions not the case as I know from my own backups of entire UltraEdit installations (program files + my application data files).

An example is the storage format of smart templates. The storage format of smart templates changed several times in the last three years due to several issues with templates created by users containing data which have broken the XML syntax used for the template files. The latest version of UltraEdit knows all former used storage formats for the templates and can interpret them therefore correct after an upgrade or update of UltraEdit. But a once by UltraEdit v2025.2.0.8 upgraded template file cannot be read anymore by an older version of UltraEdit which has no knowledge about the templates storage format as used  by UltraEdit v2025.2.0.8.

I have archived nearly all public released versions of UltraEdit and UEStudio as installed with my application data files to be able to help users of older versions or find out since which version a bug exists on finding a bug in currently latest version.

A real parallel installation and usage is difficult to achieve and nowadays with UltraEdit 2025.2.0.8 difficult because of the registration of the files in %ProgramFiles%\IDM Computer Solutions\Common and the shell extension DLLs ue32ctmn.dll and ue64ctmn.dll. The shell extension DLLs are no problem as existing in older versions of UltraEdit with same file name. But the common file names and their registration changed as described at SFTP won't connect to server in UEStudio version 2025.1.0.20 64-bit which makes it difficult to use an older version of UltraEdit now parallel to version 2025.2.0.8. The older version of UltraEdit can be still used parallel to v2025.2.0.8 as long as not using FTP/FTPS/SFTP and SSH/telnet as in this case the common DLLs being different between v2025.2.0.8 and older versions are not used by UltraEdit.

There can be done following which I do since 25 years:

1. Make a copy of %ProgramFiles%\IDM Computer Solutions\Common in same directory with new directory name Common_2022_0 as administrator.
2. Make a copy of %ProgramFiles%\IDM Computer Solutions\UltraEdit in same directory with new directory name UltraEdit_2022_0 as administrator.
3. Make a copy of %APPDATA%\IDMComp\UltraEdit in same directory with new directory name UltraEdit_2022_0 with standard account.
4. Uninstall UltraEdit 2022.0 as described in my first post on this topic with restart of Windows.
5. Install UltraEdit 2025.2 in same directory as former used version of UltraEdit which means into %ProgramFiles%\IDM Computer Solutions\UltraEdit resulting in also creating new %ProgramFiles%\IDM Computer Solutions\Common or updating it on an older version of UEStudio, UltraCompare and UltraFTP are installed too. UltraEdit, Inc. released new versions of UltraEdit, UEStudio, UltraCompare and UltraFTP on same day because of their common usage of the common DLLs. There are now two variants of the wodCertificate*.dll and wodFtpDLX*.dll for still supporting older FTP/FTPS/SFTP and SSH/telnet servers with deprecated and partly insecure ciphers and encryption algorithms.

I have not tried it but it should work to start and use UltraEdit v2022.0.0 102 without using FTP/FTPS/SFTP and SSH/telnet by creating a shortcut which runs %ProgramFiles%\IDM Computer Solutions\UltraEdit_2022_0\uedit64.exe with /i="%APPDATA%\IDMComp\UltraEdit_2022_0\ue.ini" for shortcut property Target. ue.ini contains absolute folder and file names with the path %APPDATA%\IDMComp\UltraEdit which need to be updated with appending _2022_0 on using this possible solution. There can be used v2025.2.0.8 to modify paths in files in folder %APPDATA%\IDMComp\UltraEdit_2022_0\ and its subfolders before starting older version of UltraEdit. A real parallel start of both versions of UltraEdit at the same time requires also using at least for the older version the parameter /fni as first parameter before /i="…" or there is in both versions checked Allow multiple instances at Advanced - Settings or Configuration - Application layout - Miscellaneous.

What worked in the past very good for me as the file names of the common DLLs were the same for all versions of UltraEdit, UEStudio, UltraCompare, UltraFTP and therefore their registration in Windows registry was renaming the three folders of currently latest version of UltraEdit like 2025.2.0.8 by appending the version number to the end of the directory names like _2025_2 and renaming the folders of the older version like _2025_0 back to original names without the version number appended while no instance of UE (and UES, UC, UFTP) is currently running. Then the older version could be used as before.

The new names of the common DLLs and their registration is nowadays a problem on using this method but works as long as not using FTP/FTPS/SFTP and SSH/telnet. Well, in my test it was not necessary to rename the Common folder to use an older version of UltraEdit with different common DLLs without using FTP/FTPS/SFTP and SSH/telnet. It was enough to rename just the program files folder and the application data folder of UltraEdit.

Note: The folder rename of the program files folder of UltraEdit cannot be done if Windows Explorer has currently loaded the shell extension DLLs which prevents the folder rename. It is necessary to uncheck in configuration of UltraEdit the Explorer integration and restart Windows to prevent loading the shell extension DLLs by Windows Explorer. Then it is possible to rename the program files folder of UltraEdit while no instance of UltraEdit is running.