Possible bug? Autoruns64 fails to find a program file when it includes program arguments.

Question

I am running autoruns64 v14.10 on a Windows 11 Home 23H2 system. I was looking closely at the various entries that appear in yellow, indicating that the designated file could not be found. One of the entries, copied from autoruns64, looks like this:

Send to OneNote.lnk File not found: "C:\Program Files\Microsoft Office\root\Office16\ONENOTEM.EXE /tsr"

Note that the program argument of /tsr has been included in the path, within the double quotes. The program does, in fact, exist at "C:\Program Files\Microsoft Office\root\Office16\ONENOTEM.EXE". It looks as though autoruns64 is mistakenly taking the entire text of the shortcut's target as the full path instead of honoring the quotes found in the target definition. Here is an image of the relevant property tab:

Note the difference in the placement of the closing double quote in the shortcut as opposed to the version in autoruns64's File not found message, as shown above. Possible bug? In any event, thanks for creating and continuing to update this very helpful tool.