You must generate a new .INI file using the instructions I gave you and follow them exactly as written in my post timed at 17:39 on Page 1 of this thread.
From what you wrote previously, I think you are going wrong by starting up RailMaster after deleting the .INI file.
Once you have deleted the .INI file [do not have RailMaster running when you delete the .INI file] ... you do not restart RailMaster.
Instead, you run the downloaded installer [from the link at the top of the RailMaster forum] to generate the new .INI file and then and only then re-start RailMaster. To run the installer, you must 'right click' the downloaded and saved installer file and chose 'Run as administrator'.
When restarting RailMaster you then ignore any error messages and cancel them to go straight into the .INI file editor to make the .INI changes I recommended. Once the .INI amendments [if any] are saved, then close down RailMaster and restart it again.
The above is the abridged version of the full details in my linked posts.
If after the final re-start you still get Elite communication error messages, this can sometimes be quite normal. You just have to open 'Windows Device Manager' to check which COMM port has been assigned by Windows to the Elite. Armed with that information, you open the RailMaster 'System Settings' screen, then make sure that 'Controller A' has the same COMM port number selected. Then close and re-open RailMaster once more.
Once you have got a stable controller connection then ensure that you keep on using the same USB port for the Elite to connect to. Changing the USB port will likely loose communication between RailMaster and the Elite and you will have to manually sync the allocated COMM port again. RailMaster was written for Windows XP and the COMM port allocations are not automatically maintained in sync. You have to do it yourself, hence the guidance to keep using the same USB port. A PC/Laptop USB 2.0 port is also more reliable than a USB 3.0 port as well.