Profile not loading database from second partition

Just upgraded from 1.0.245 to 1.1.4 on Windows 7.

I have (previously) moved my Joplin database to a second partition and up to now having the Target of the shortcut as
"C:\Program Files\Joplin\Joplin.exe" --profile D:\Data\Joplin
was loading the database from that location.

With the latest version it is not loading the data from that location (and I've double checked by running it from the command line). There is no mention of changes to the --profile parameter. Has a bug been introduced or did the profile parameter get changed/removed, in which case how can I load a database from a different location to standard?

I've tried to roll-back to 1.0.245, but get the same error reported at How do I roll back a "profile version"? (although it does then load my database fine if I change the Target to "C:\Program Files\Joplin\Joplin.exe" --profile D:\Data\Joplin, so it is just complaining about the database that it finds in the default location)