Hi, I'm using a plugin/dissector that requires me to be on version 3.0.x and doesn't support later versions. I have changed gui.update.enabled to FALSE.
I am installing by the win64 3.0.14.exe package, but still keep finding my Wireshark has updated itself to 3.2.14, and this breaks my plugin.
Any ideas for sneaky ways Wireshark could be getting updated against my wishes?
Preferences are applicable per-profile, so if you had changed profiles then it's certainly possible that the gui.update.enabled preference was enabled in the new profile. That said, that feature doesn't automatically update Wireshark - at least not to my knowledge. What it will do is inform the user that a new update is available, but it's entirely up to the user to decide whether to update Wireshark or not, so most likely either you or someone else who uses your machine chose to update Wireshark, whether that was done through the update notification from Wireshark or completely separately.
In addition, if Wireshark had informed you that a new version was available, I believe it would have informed you about Wireshark 3.4.6, not 3.2.14, since 3.4.6 is the latest available stable release. If you are currently running Wireshark 3.0.14, what do you see if you manually check for updates via "Help -> Check for Updates..."? Does it tell you 3.2.14 or 3.4.6 is the newest version?
Hi cmaynard,
Currently it seems to be staying on 3.0.14 as I want it to, after running it for a day or so and rebooting my PC a few times. I think the only thing I did differently this (third) time I reinstalled was to check all the boxes for deleting plugins directories and other assorted Wireshark files when I uninstalled 3.2.14.
To answer your question, no matter whether I was running 3.0.14 or 3.2.14, the auto-update checker informed me that the newest version available was 3.4.6.
So I think case closed for now unless the problem comes back. Thanks, Arthur
Asked: 2021-07-08 19:13:14 +0000
Seen: 549 times
Last updated: Jul 09 '21
