Related page:
https://social.msdn.microsoft.com/Forums/azure/en-US/6f9f1695-9d64-43f3-8527-6b895599233a/use-unicode-utf8-for-worldwide-language-support?forum=windowsgeneraldevelopmentissues

Overview
Recently (starting March 2020 or so), a handful of Azhagi+ users started reporting the display of an "informational" error message by Azhagi+, as soon as the latest Azhagi+ 10.45 is started. Typically, the "informational" error message would say "Subscript out of range".

Only in the 1st week of June 2020, I could get time to focus on the above issue. I had to spend a whole night (and more time later on) to get to the bottom of this issue and find the root cause. For a sincere developer like me, it was a real sapping/ablation of my energy/time. One reason for not being able to attend to this issue promptly is because of the fact that I just could not reproduce the aforesaid error message in Azhagi+ in my Windows 10 system at all. Ultimately, Thanks a TON to the Lord Almighty, for without His Gracious Compassion, I could not have got to the very bottom of this tricky issue (with a beta setting that is buried very deep in the 'Windows 10' Settings Scheme) and found out the solution.

The final finding
Perfect it is, Azhagi+ 10.45, as ever. The issue reported by a handful of users is actually due to a "Windows10 and Windows11" BUG (bug, in my personal humble opinion) in a particular Windows 10/11 setting. How this buggy (in my personal humble opinion) setting is causing havoc to so many robust apps is stated/discussed in more than one web page in the net. One such web page is - https://social.msdn.microsoft.com/Forums/azure/en-US/6f9f1695-9d64-43f3-8527-6b895599233a/use-unicode-utf8-for-worldwide-language-support?forum=windowsgeneraldevelopmentissues

The bottom line
There is NO problem with Azhagi+ 10.45. The issue reported by a handful of users is to do with a buggy setting in Windows 10 and Windows 11. Once that buggy setting is set right, users can happily work with Azhagi+ 10.45 as usual.

How to set right the abovementioned buggy BETA setting in Windows 10?
IMPORTANT NOTE: Please effect the following only if you are comfortable doing the same and not otherwise. If you are not computer-savvy and hence not feeling comfortable effecting the following, then you can always take my help OR the help of any other computer-savvy person's. For Windows 11, see the screenshot at the end of this page.

1. Better to have a look at the screenshot below first and then read the following steps.
   
2. You first need to reach 'Language Settings' screen in your Windows 10 system. One way to reach it is by typing 'language' in the 'Search Bar' at the bottom left of your taskbar and then clicking 'Language Settings' shown at the top of the list of best matches.
   
3. In the 'Language Settings' screen, click on 'Administrative Language Settings' link (under 'Related Settings' on the right side top.
   
4. Thereafter, click on 'Change system locale...' button.
   
5. In the small window which opens, you can see a setting with caption "Beta: Use Unicode UTF-8 for worldwide language support". This setting needs to be kept UNTICKED. Then, latest 10.45 Azhagi+ will work perfectly as ever.
   

• Note-1: If in case the aforesaid option is grayed out (in ticked state) and you are unable to untick it, then you need to ensure first that your display language is English and not 'Tamil', Hindi', etc. Ideally, I would suggest you to have your display language as "English (United States) US"
  


• Note-2: If you try to change the display language, your system may require you to restart the system. Restarting your system may take a while. So, if you are in the midst of an urgent work, then you can schedule the task of changing the display language to a suitable later time.
  


• Note-3: Once you UNTICK the aforesaid "Beta:... .. ." option, your system may require you to restart the system. So, better to save and close all your running applications and then UNTICK the aforesaid option.
  


• Note-4: Restarting your system may take a while. So, if you are in the midst of an urgent work, then you can schedule your aforesaid UNTICKING task to a suitable later time.
  


• Note-5: VERY IMPORTANT - In some systems, restarting once may not work. You may need to restart twice or even thrice, for the UNTICKING of the "Beta..." setting to take effect fully. Or, perhaps you can completely shut down your system and then start it again, if you find Azhagi+ 10.45 still displaying an 'informational' error message, after the first restart. In this regard, please see the following supporting feedback from one user hereunder: