Page 1 of 1
Double Click on filename results in error instead of opening the file
Posted: 05 Jul 2022 11:23
by huey_v
When I double click a file in the file list I get en error message: "Wrong Parameter" (German: Falscher Parameter). Normally the file should open. This behavior is conistent throughout all file types.
Double clicking on folders in the list view still works fine and opens the subfolder corectly.
In earlier versions of xyplorer the double click on files for opening them worked properly. I do not know whether I accidently changed a configuration or if this is an error of xyplorer.
Please help!
Re: Double Click on filename results in error instead of opening the file
Posted: 05 Jul 2022 11:57
by highend
Menu - Tools - Customize File Associations...
Show a screenshot of it
Re: Double Click on filename results in error instead of opening the file
Posted: 06 Jul 2022 11:52
by huey_v
Thanks, please find below the screenshot as attachement.
Formerly opening by double click worked without specific entries for the files, as the windows standard file assiciations have been used. Then after a upgrade the double click did nor open files any longer. I added for test purposes the entries for pdf and winword. This did not make a difference. Double click still does not open the files.
When I right click and selct "Open" from the context menu, the files open properly.
Best regards,
Hubert
Re: Double Click on filename results in error instead of opening the file
Posted: 06 Jul 2022 12:23
by highend
Does it work in a fresh XY instance?
+ ENTER in the address bar
Re: Double Click on filename results in error instead of opening the file
Posted: 07 Jul 2022 07:23
by huey_v
Double Click is working now - after a win11 update has been installed yeserday. Sorry for bothering you, this is a very strange effect.
Re: Double Click on filename results in error instead of opening the file
Posted: 07 Jul 2022 08:49
by Horst
huey_v wrote: ↑07 Jul 2022 07:23
Double Click is working now - after a win11 update has been installed yeserday. Sorry for bothering you, this is a very strange effect.
I guess you are using an Insider Windows 11 version
because there was never such an errror with any updates of the release versions.