Still Showing as 2016.3.3 after Update

After I updated to 2017.1, my program still shows everywhere as 2016.3.3. I'm not sure if this is intended, a function of the updater not being able to update Windows registries associated with the program name, or whatnot. Just wondering if this can be fixed.

0
2 comments

Hi there,

Where does it show that? Inside actual IDE (e.g. on Welcome screen or "Help | About") or in actual Windows (desktop/menu shortcut; pinned icons; Uninstall section etc)?

Some screenshots will be useful.

But in general:

  • Inside IDE -- you must be still using old version then. Uninstall it (keep the settings) and then install latest version from full installer -- if no settings for current version is detected then you will be prompted to import them from previous version
  • Pinned Taskbar icons -- I'm always using uninstall and then install from full package .. and pinned taskbar icon still shows the text of the version that was pinned
  • Cannot comment on other shortcuts/installed apps screen -- I'm always using full installer and simply do not see such issue.

 

Small note/possible reason: what x-bit version do you use. I mean -- 32-bit IDE/JDK or 64-bit one? You can find it in "Help | About" or by checking Task Manager -- PhpStorm.exe vs PhpStorm64.exe .

  • 2016.3 and all versions before that were coming with bundled 32-bit JDK. If you wanted to use 64-bit you had todownload 64-bit JDK manually and tell IDE to use it.
  • 2017.1 now comes with 64-bit bundled JDK by default .. and you have to explicitly choose to download 32-bit JDK as separate download (during installation) if you wish to using 32-bit one.
  • Plus, 2017.1 (at very least 2017.1.1) now gets installed into "C:\Program Files\JetBrains" while before it was "C:\Program Files (x86)\JetBrains"

Maybe it has something to do with the above changes?

0
Avatar
Permanently deleted user

It was showing outside the IDE. I simply uninstalled and installed the newest version which also came with the x64 and it has fixed the issue.

0

Please sign in to leave a comment.