Sorry! It is NOT that I refuse to help you. It is mostly I don’t know how… I asked for screenshots (a normal function of Windows, which I assumed you would know how to grab). I asked for the Debug Info (I told you what menu to go into to get it). You provided neither. Also, I thought telling you that NOTHING showed in " -> Configuration" was self evident and DIDN’T need a screen snapshot? The screenshot would have confirmed: 1) that there really was “nothing” there (maybe you and I have a different definition of “nothing”), 2) whether you had really selected “user scripts” or had selected “machine scripts”, and 3) that you were willing to follow instructions to try to get help. I’m happy to announce I’ve fixed it!!! Don’t ask me how but my WHOLE NP++ setup was weird!!! It seemed half in Program Files and half in AppData. That’s not weird. That’s how Notepad++ and PythonScript are intentionally set up. The FAQ footnote that I’ve begged you to read explains why there are the two different script locations. In fiddling around I copied the PythonScript directory from Program Files into AppData and TaDa! Everything fell into place… EVERYTHING WORKED like clockwork! You thus copied way too much. You could have copied just the scripts. Or you could have just clicked the “machine scripts” button in the dialog, like I told you to, and not had to copy any files. THANK YOU for your responses and help. Glad you’ve got it working.

@Samir-Sumantlal-Shah said in Hopefully Notepad++ can display correctly ...: GujaratiMT Searching suggests that “Gujarati MT” is a Apple system font that is not available elsewhere. Are you by any chance using the new MacOS port of Notepad++? That port is not maintained or endorsed by the creator of Notepad++. You would have to raise issues with it in its own repository. We’re not going have a clue here.

Thank you Peter. Makes perfect sense. Much appreciated!

I have checked out the https://github.com/donho/xmlSigner project and it is what I needed. I have used that project to correctly pass the XML signing test. I have opened some issues with that project. Here is a quick summary of how the update process works. The wingup code first queries a website to determine if an update is required and the returned XML provides information to be used later. None of the information in the XML is used if it doesn’t pass the XML security check. After passing the security check the code looks for the update status and download location, assuming an update is required. After prompting the user to download the update and finishing the download, it checks the code signing of the installer. Assuming that the code signing is valid and the correct certificate, it starts the install. I will try to document all the customizations to the code from Notepad++, wingup and xmlSigner to make it work in my project so that future users have a place to start, but that will be after I am sure its all working correctly with the new security updates. Thank you @xomx for pointing me in the right direction.

@dz15mlru Disable automatic encoding recognition. For Windows-1251 encoded Russian, auto-recognition will always open as Macintosh. If you start editing files, you will have two encodings, or rather garbage from two encodings, which will be difficult to fix manually, since you will have to re-read all the texts (this is a module for spoiling files). When you disable automatic encoding assignment, you will only have ANSI, UTF-8, UTF-16. WindowsXP-7-8-10-11 it will always open the ANSI file correctly, in 1251 encoding, as this is the default encoding. The remaining UTF-8 and others will also open automatically correctly. You will get rid of the problem forever. The automatic text encoding recognition module is needed if you open files in Arabic in ANSI, but in reality you will never do this, since a Russian-speaking person has only Russian-language files on their computer. People who want to make the file available to all people on earth save the file in UTF-8 encoding and it will always open correctly for you. You don’t need automatic file recognition, as it’s only for local files that you’ll never get from someone else’s computer abroad. Отключи автоматической распознавание кодировки. Для русского языка в кодировке Windows-1251 автораспознавание всегда будет открываться как Macintosh. Если начать редактировать файлы, то у вас будет две кодировки, точнее мусор из двух кодировок, который будет трудно исправить вручную, так как вам придётся перечитать все тексты (это модуль для порчи файлов). Когда вы отключите автораспозначание кодировки, то у вас будет только ANSI, UTF-8, UTF-16. WindowsXP-7-8-10-11 всегда откроет файл ANSI правильно, в кодировке 1251, так как это кодировка по умолчанию. Остальные UTF-8 и прочие откроются также автоматически правильно. Вы навсегда избавитесь от проблемы. Модуль автоматического распознавания кодировки текста нужен если вы открываете файлы на арабском языке в ANSI, но в реальности вы никогда этого не сделаете, так как у русскоязычного человека на компьютере есть только русскоязычные файлы. Люди, которые хотят сделать файл доступным для всех людей на земле сохраняют файл в кодировке UTF-8 и он всегда откроется правильно у вас. Вам не нужно автоматическое распознавание файлов, так как оно только для локальных файлов, которые у вас никогда не появятся с чужого заграничного компьютера.