## Description <!-- A clear and concise description of the problem with screenshots of the issue, if applicable. What is the behavior you see and what behavior do you expect? (Note: Feature requests should be made by creating a new topic here: https://discourse.paraview.org/c/feature-requests/14). --> Some Ensight case files that opened fine in Paraview 6.0.1 do not seem to open in Paraview 6.1.0. When trying to open these case files with Paraview 6.1.0, the list of readers will appear instead. As an additional issue, the list of readers does not seem to include the Ensight case reader. The only reader in the list that mentions Ensight is the `Ensight Master Server Reader`, which I believe is used to read in Ensight SOS files. So it would be good to have the Ensight case reader listed here, too. See the screenshot below. {width=559 height=593} ## Steps to reproduce <!-- Steps to reproduce the behavior. Include example datafiles and/or state files that demonstrate the behavior. Screenshots may be helpful. --> Here is an example dataset: [not_recognized.tar.gz](/uploads/ce8818a65c070b7dc21d707727a3714f/not_recognized.tar.gz) If you load this dataset in Paraview 6.0.1, it will load fine. If you load this dataset in Paraview 6.1.0, it will not load and the list of readers will appear instead. In the file `not_recognized.case`, there are two lines for `model`, where one of them is commented out. If you use the following line, you will get the reader list to appear. ``` model: 0000/not_recognized.*****.geo ``` If instead you use the line below, then it loads fine. ``` model: not_recognized.*****.geo ``` So adding the directory `0000` to the path seems to cause the error. ## Configuration <!-- Operating system, standalone client, client/server, pvpython, pvbatch --> * **Operating system and version:** Mac Sequoia 15.7.5 * **ParaView executable and version:** <!-- GUI client, pvpython, pvbatch, etc. --> Paraview 6.1.0 * **ParaView configuration:** <!-- standalone client, remote server, Catalyst, etc. --> standalone client @dbanesh @cory.quammen