install problem - file association paraview 5.11 in windows 11

ParaView Support
1

Hello I am working on my personal computer and having trouble updating to the last version of paraview.

After downloading and installing, as usual in previous version, the msi package, when I update the executable associated with the vtk files - it seems that the file association fails.

All the vtk files icon turns to blank:

image

and when I click on these the following prompt is shown:

image
image447×565 29.8 KB

However if I click on paraview.exe, nothing happens.

It is not a huge problem, I can still use the older version just fine or I can open the 5.11 binary and manually open the file from inside the paraview, however It is a bit of a pain day to day.

I was wondering if I am the only one with this issue with win11

1 Like
2

bump :sweat_smile:

3

It seems that this is something else that we lost in the exe → msi migration :confused: .

Cc: @wascott @cory.quammen

4

We don’t use the msi version. We download the zip ball, and I then repackage it into a zip and also a exe package. Thanks for the heads up.

5

the same file association issue arise both with the installer and with the zip package

6

Yeah, the .zip is never going to do file associations; it is just a directory containing ParaView.

7

Hello all,

I’m reviving this thread because I have the same problem, pretty much every time I want to upgrade ParaView to a new version, on both windows 10 and 11, using msi.

After installing the new version, I update the file association in the settings as mentioned in the initial post, but it seems the new path is not saved and the file association still point to the old ParaView install. (or just fails if I uninstalled the older version)

Is there a workaround to solve this issue?

Thanks,
Yann

8

Alright, I found the culprit, and the solution.

  1. Press Win + R, type regedit, and press Enter to open the Registry Editor.
  2. Navigate to the following key: HKEY_CLASSES_ROOT\Applications\paraview.exe\shell\open\command
  3. Update paraview path to the desired version.

This will make things way easier and more comfortable to upgrade to newer versions!

1 Like
9

I’d expect this to be automatic. Worth opening an issue imo.

FYI @cory.quammen