Vscode.exe

Thanks for the infoThe version comment makes that a possibility as to part of the issueHowever I see that the suggestion is that latex workshop is acting as middleman thus its the need to go back via synctex calling workshop rather than vscode.exe direct that seems to be the root cause

vscode.exe

041b061a72