08/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	First of all: thank you for this wonderful app, I use it for years now. Contrary to the previous version, the version 7 cannot be launched on my device in the office anymore due to company's security settings. Unfortunately, the windows message gives no more details than "access blocked" and I have no clue, how to figure out the true reason. Btw: As a workaround I looked for an option to download one of the previous releases. As your website offers the latest release only I was forced to search alternative download resources. It would be nice, if at least the preceeding version would still be available on your website. edited by kuehni on 08/01/2022
08/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	Thank you for the prompt reply, I will check the AV software used by my company next Monday.
10/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	Short update: AV software is nothing spectacular: Windows Defender. My limited user rights on this device do not allow me to access the Window's security log. The previous Symenu version runs without any issues.
20/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	Sorry for my delayed answer, it took me some time to perform this test. Surprisingly, the security block flag you mentioned is not available, neither on my private device nor on company's device. The Windows file property dialog shows only the checkboxes for the standard attributes (write protection, hidden ...), not the security section as shown in your example. Nevertheless, I tried to update SyMenu to 7.00v on my private device instead on company's device as before. Both, the manual update by me as well as the automatic update by SyMenu, gave me a functioning version 7, even on company's device. Your hint might be correct, that files downloaded on company's device got an execution lock flag, although I wasn't able to check this. During my tests I observed another issue with 7.00v. When quitting SyMenu, the application doesn't exit (on both devices). Instead the "green led" of the tasbar icon flashes for infinite time in an endless loop and the application doesn't response anymore. Reproducible I have to kill the SyMenu process using task manager when I exit Symenu 7.00v. This doesn't apply to the previous version. Luckily, this issue doesn't prevent the shutdown of windows, so I don't care about it as I don't exit SyMenu manually during normal usage.
25/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	You are right, SyMenu closes properly if the "Autoexec on close" flag is removed from the vbs script. Strange, as the script has not been changed and runs fine when manually launched. The script is nothing spectacular, it removes the context handler added by the "Autoexec on start" script (which still works with SyMenu 7): ******* Dim WSHShell Set WSHShell = CreateObject ("WScript.Shell") On Error Resume Next WshShell.RegDelete "HKEY_CURRENT_USER\Software\Classes\*\shell\Open with Notepad++\command\" WshShell.RegDelete "HKEY_CURRENT_USER\Software\Classes\*\shell\Open with Notepad++\" ***** Well, the style of the script is not nice, but it worked fine until SyMenu 7. Maybe I will rewrite both scripts implementing the context handler via ShellEx. SyMenu's Extension Manager does not allow to add the wildcard * as extension. edited by kuehni on 25/01/2022
25/01/2022 Topic: Security settings block access to SyMenu 7 kuehni	Solution: Any "autoexec on close" item refering to a vbs file instead to an executable file in the path element will block SyMenu's closure (regardless of the file content, it can be even blank). This can be solved by following approach: - change path from vbs file to the script interpreter (e.g. "%SystemRoot%\System32\wscript.exe") - move the vbs file to the program arguments (e.g. //nologo "#:\your path\your file.vbs")

---