File-based Detection method where folder path contains an apostrophe

I have to deploy a number of legacy applications that use a VB6 setup (not MSI) and the installations do not populate the registry in any useful way. For all of them I am using a file-based Detection method (e.g. app.exe in %ProgramFiles%\AppName, etc). This works fine for all but one of them and it seems to be because the folder path contains an apostrophe ( %ProgramFiles%\Contoso’s dept).

In each case I configure the file detection by browsing to the executable on a machine where it the app has been deployed to eliminate typos and this works for all the other applications but not the one where the path contains an apostrophe.  I am aware having apostrophes in folder paths should be avoided but we have no choice as the application is developed by a third party.

I realise I can use a script detection (e.g. Powershell’s Test-path) but would prefer to keep it as simple and clear as possible as well as keep it consistent with how I have configured detection logic for other applications from this third-party. I tried escaping using “\” and dropping the apostrophe altogether but had no success. The UI doesn't allow you to put the folder path in double-quotes. 

The only post here that seemed vaguely relevant after a quick search was

Has anyone come across an issue with the file detection method like this before?