Yes, the readme file is unfortunately also packed in uesetup.exe. The most important changes are shown during the installation procedure (saved in file changes.txt in the program directory after installation). Most users simply don't read it and just press OK. But the readme file can be read immediately after the installation by clicking on the appropriate shortcut in the start menu. Hm, is the readme file opened with UltraEdit or Notepad? I must confess that I always delete the shortcuts immediately after installation and use the Lister of Total Commander to read the readme before I start first time the new version. (And I always create a backup of ALL files of a program before I update I program because I'm very curious and want always know what has been changed after the update.)
And yes, UE will not ask an user to move its configuration files to a new location. I have never seen a program that does that. Every program I have ever used continues to use the existing configuration files even when a new version would create it on a completely new installation in a different directory because of requirements of new operating systems. Well, WinXP is not new ANYMORE, but it was in 2002 as Win2K was in 2000.
All the configuration files are created or updated by the application itself and not by the installer. Only the program really knows what it needs. Also the program must completely handle the configuration file itself or multi-user environments (more than 1 user on 1 computer) will never be supported when only the user who installs the program get updated configuration files. So not the installer updates the INI, the key mapping config file, the menus and toolbars, UltraEdit does it on first start after upgrade for every user if every user has it's own INI (and for every INI if a user like I have more than 1 INI with also multiple *.mfg, *.tfg, *.pfg, ...). Because UE handles the config files, they are also never uninstalled by the installer. The installer does not know where the config files are stored. The uninstaller Total Commander is a little bit better because it asks the user if he wants to uninstall only the program files or also the 2 configuration (INI) files of TC. But even the uninstaller of TC does not uninstall personal menu/toolbar configuration files and INIs of TC not stored in one of the default locations. That's the job of the advanced user, who created these extra files.
For installation of upgrades (version number increases by at least 0.10 = major version increases or minor version increases by 10) always an administrator account should be used because the new version could need access to HKLM to register new features like the SSH/Telnet OLE control.
To Manni and Bernie:
If with a restricted account UE v10.20 or higher really does not use the uedit32.ini in the correct user specific application data directory although the APPDATA environment variable of the restricted user account points to the correct directory and the directory is not write-protected and also really no other configuration files exist in the program directory of UE or the Windows directory and UE is surely also started without /i= command line parameter and no UEINIDIR is set then please report this to IDM so the developers look into it and fix it. You can use Filemon
with Include filter set to uedit32
to see what's going on at start of UE v10.20+ with a restricted user account.