Disable cmd window update notice?

I am not sure which forum (if any) would be best to use for this question, but maybe someone will be able to advise or refer me elsewhere if I post in the most general one. It's not really a Windows 10 issue per se (I have the same problem in Windows 7 too).

I use a programme (XXCopy) which every so often, when I run a script, brings up a long screed (gradually appearing line by line in a cmd window) telling me I have been using XXCopy for so many days (several thousand now) and that I need to go to the website to get an update.

Thing is, as some of you will know, XXCopy disappeared over seven years ago and has not been updated or supported since. I know there are other options which might replace XXCopy, but I have been using it for so long and am so familiar with most of its intricacies when writing scripts that I can't envisage using something else.

At worst, I will just continue dismissing the update warnings (you can't until they have run their course), but does anyone know how I might be able to remove them once and for all. Decompiling/editing/recompiling the exe files? (The programme installs various exe files into C:\Windows subfolders). But you'd have to ask specific questions if needs be - not sure what to post at this stage.

Thank you!

Thank you.. that was quick. Thing is, the notification is not brought up by Windows but by the XXCopy programme itself. I am pretty sure that 'hacking' the files is probably the only way (a 'no no' usually, I am well aware of course; but given the developer's site closed many years ago without removing this update, maybe it's permissible?).

I am 99% sure that it is set from within a programme executable file - none of them is called anything helpful. There's a .bat file too, but that is only for uninstalling. The exe files are:

XXCOPY.EXE (one copy in System32 subfolder, one in .../SysWOW64
XXCOPYSU.EXE

I guess I could try disable the latter and see if that does anything (other than disable the whole programme!). It'd be several weeks before I could draw any conclusions, as the notices come up only every few weeks.

Thanks for the link. I should have said that I have tried what is suggested there a number of times over the years (it was posted 17 years ago), but as I think it mentions, it only works with one specific build of the programme. I never got it to work for me.

No, the forum was dead and had been for a long time last time I looked. Not sure if it even exists now (will double check).

Thank you for trying to help!