I'll bring this up again because I wonder if your setup packaging is including an older file, even though you've said before that it's already been dealt with? Not that this is any irritation for me -- I simply go into that unit and comment out the unused variable reference. It's the same as what I reported before (see below).
I updated to the latest TMS VCL UI pack and rec'd no installation errors. But when compiling my projects, the same warning that I've seen in past updates again appears:
C:\....\TMS VCL UI Pack\AdvGrid.pas(11942): Hint warning H2077: Value assigned to 'de' never used [C:\....\myProject.dproj]
You must have an old version of AdvGrid.pas hanging around on your system / library path as in the latest release, there is NO such hint in the code. Please search your FULL hard disk and remove ALL old versions of AdvGrid.pas and clean up your library path to point ONLY to the latest version of TMS VCL UI Pack.

I was hoping I'd find a duplicate version of AdvGrid.pas, but to no avail.
All path references point to the same folder on my system:
C:\DelphiComponents\tmssoftware\TMS VCL UI Pack\
Observe the attached picture:
-
Results of a file search for AdvGrid.pas throughout all of Drive C. It yielded one result at the above folder.
-
The contents of AdvGrid.pas in that folder, revealing that it's the older version where I had to remove those two unused var references.
-
Pictures of Delphi 12.3's 32-bit and 64-bit Library Path list, showing the three "TMS VCL UI Pack" references in each one. There are no other "TMS VCL UI Pack" references anywhere higher up on those lists.
As I have said before, this is a trivial issue for me. If the TMS installer failed to overwrite AdvGrid.pas, I would think that it would have reported an installation error after the setup completed (as I've seen in my system for unrelated issues years ago, which I've solved by pausing my virus software during installation). Regardless, if there was an overwrite error, there was nothing that reported it.
I won't bring this up again. I just figured I was helping your team to find a possible glitch in your setup configuration. If I am the only one reporting this, I conclude it's something oddly happening on my end.
I suggest to do an uninstall.
After uninstall, double check that all files are gone. Then do an install on a clean machine.