Known Limitations

 Unsupported 16-bit Files: Resource Tuner Console does not work with NE and other 16-bit files. It exclusively supports 32-bit and 64-bit files, and there are no plans to add support for 16-bit program files.

 No .NET Resource Handling: Currently, Resource Tuner Console does not handle .NET resources in managed assemblies. It is compatible only with unmanaged 32-bit and 64-bit PE files.

 Limitations with Protected or Compressed Executables: RTC does not work with protected or heavily compressed executable files, except for UPX-compressed files. If your target files were packed by third-party protectors that encrypt data and resources to prevent reverse engineering, manual unpacking is required before modification. Resource Tuner Console respects the security attempts of other software authors.

Resource Tuner Console ships with the UPX Unpacker plug-in, which is used for unpacking files compressed with UPX (see https://upx.github.io).

 Limited Support for Self-Test Protection: Resource Tuner Console does not work with applications that have built-in self-tests to verify if they have been tampered with. RTC does not attempt to bypass or circumvent such protection systems.

Functionality Currently NOT Supported

 Copying Icon, Cursor, Icon Group, and Cursor Group Resources with Another Language: The CopyResource procedure does not support creating copies of these resources with different languages.

 Manipulation of Menu, Dialog, and RC Data Resources: Due to the visual nature of GUI elements such as Menu, Dialog, and RC Data resources, Resource Tuner Console currently does not support any manipulation of these resources.