in reply to Nooo!... Have I trashed my Strawberry?

You need to uninstall the old version before installing the new version. Otherwise you end up with mixed directory contents from the two versions.

You could probably delete the entire directory and then reinstall the more recent version, but that might leave things behind in the registry.

One possible approach (untested) is to (1) uninstall 5.40, (2) reinstall 5.32 to hopefully get back to where you were, (3) uninstall 5.32 to clean it out, and then (4) reinstall 5.40.

Neither approach will bring back your old modules but it's safer to reinstall them anyway. Or just stick with the portable version which is what I do.

If you want to work with several perl versions and switch between them as needed then berrybrew, maintained by stevieb, is well worth looking at.

  • Comment on Re: Nooo!... Have I trashed my Strawberry?

Replies are listed 'Best First'.
Re^2: Nooo!... Have I trashed my Strawberry?
by Intrepid (Curate) on Jun 10, 2025 at 19:04 UTC

    swl contributed:

    One possible approach (untested) is to (1) uninstall 5.40, (2) reinstall 5.32 to hopefully get back to where you were, (3) uninstall 5.32 to clean it out, and then (4) reinstall 5.40.

    Yes, thanks, that's helpful. Just now I uninstalled 5.40 and reinstalled 5.32, which I briefly tested and which seems to be functional. I had managed to forget that MSI packaging includes the capability to uninstall the software (I'm still relearning stuff I once knew long ago).

    Furthermore:

    If you want to work with several perl versions and switch between them as needed then berrybrew, maintained by stevieb, is well worth looking at.

    I am going to take a look at berrybrew, which I have heard of, and see if that's the preferred way for me to get a perl5.40 or other versions on my system (in addition to the one I already have on the USB drive).

    … ok, I set up berrybrew, it's a little rough around the edges at least if you use git to fetch it: when I followed the directions to configure it I got bin/berrybrew.exe:Permission denied. No big deal, I just needed to chmod 0755 in cygwin. Then it said I had to be an Administrator to run it, so I started a PS/CMD shell as Admin and then it worked. I've got "berrybrew --help" open in my shell now ;-)

    Jun 10, 2025 at 19:03 UTC

      It's best to use the Windows installer to install berrybrew. It allows for seamless upgrades, and provides the facility to install its own UI.