I may have found the bug in 11.2.100 if you are using Kinetic.exe
Basically AutoUpdate does 50-100 random tests of files checking if the file can be deleted.
Their code has a line to exclude Epicor.exe from this test and since your new Assembly name is Kinetic.exe it will “possibly” try to check if Kinetic.exe (but not always true - it sorts it alphabetical so it depends if your exe gets caught in the 50 picked) can be deleted (which is in use). If any of the 50 files comes back as “not-deletable” it assumes that Admin privs are required.
The test it performs is
File.Copy(file, tempFile);
IOHelper.DeleteFile(file);
File.Move(tempFile, file);
You could add to your Epicor.exe.config or Kinetic.exe.config the following which will cause AutoUpdate to write a log with more information on which file is causing trouble.
it should write to your Temp directory an EpiUpdate file
Also there should be a Kinetic.exe and Epicor.exe perhaps have your shortcut point to Epicor.exe instead, they look identical.
Im curious which executable you are using. I could be wrong but that’s in a nutshell what I could think of.
Workaround:
Change your shortcut to target Epicor.exe
EDIT
I tested it and using Epicor.exe during new install doesnt have the prompt but using Kinetic.exe does.
The reason this happens in a new install is because your folder contains about 50 files and Kinetic.exe will be tested (Epicor.exe would have been excluded), during a regular AutoUpdate (after ReleaseClient is downloaded) you have 1000+ files and Kinetic.exe doesnt get tested and you wont notice any issues.
You can replicate the same thing by naming your assembly abc.exe post-install while having Local Admin, then forcing an update.
Not sure who maintains the Rich Client still but ill just tag @Rich as FYI