This is only a wild guess. I am not a regular user of Windows, but I have experienced situations (some years ago and with older versions of Windows) where using reserved characters in a Windows filename caused odd behaviour. In my case, the characters were hyphens/dashes, apostrophes/quotes, full stops (periods), and spaces at the end or start of a file name. Reserved characters are used by the file system for particular purposes. The most familiar example these days is the use of forward slashes in a URL (web address) to indicate a change of directory (folder).
This Microsoft web page Naming Files, Paths, and Namespaces - Win32 apps | Microsoft Docs gives a lot of information on reserved characters and naming conventions.
In your screenshot, the error message contains two apostrophes and some periods at the end. You could try removing them or replacing them with some other “normal” character and see if that makes a difference.
Another thing to try is to move the file to another location and see if it opens from there. One with a shorter filepath, such as directly inside the Documents directory, would be my first choice. Even though Windows has a filepath character limit of well over 200 characters, sometimes the operating system and applications differ in how they handle really long filepaths. Similarly with reserved characters. Sometimes an application will allow a file name to contain characters which the operating system will interpret, and handle, differently.