Problem with installing mumble.

  • Anonymous - 2012-10-22

    I'm trying to install the newest mumble 1.2.3a. At the point it's about start
    installing, i get an error saying

    "Installations" is not a valid short file name" Any ideas how to fix it?

  • Kissaki

    Kissaki - 2012-10-22

    Eh, what?
    No idea what that’s supposed to mean/be.

    Try redownloading the installer.
    Try installing a snapshot.

    Did you have problems with different installers up to now?
    Can you try to install a different program that uses msi install?

  • Anonymous - 2012-10-22

    I have tried redownloading multiple times, without any luck. I haven't had
    mumble until now. I'm pretty sure i can install other files.

  • Anonymous - 2012-10-23

    I also tried installing the snapshot version.. The "installations" folder used
    to be on my HDD, but i deleted it, and no longer exists. I tried looking it
    from the registry, but it wasn't there either.

  • Anonymous - 2012-10-23

    Now when i'm looking at the registry, it had some files in
    E:\Asennukset\Mumble, when my HDD is actually in J:\

    How is this possible?

  • Kissaki

    Kissaki - 2012-10-23

    What was the Installations folder?
    The target folder you tried to install to?
    Or the folder the msi installer was placed in before running it?
    Or a temporary folder even?

    Well, depends on what E was/is … :)
    And what registry values you’re actually looking at.

  • Anonymous - 2012-10-25

    The MSI has default installation to C:\Program Files(x86)\Mumble

  • Stefan H.

    Stefan H. - 2012-10-25

    Google has some suggestions on what might cause the issue (though none matches
    the error completely):

    • This issue may occur if you have reinstalled Mumble on a new drive after you moved or removed the drive in which Mumble was originally installed.
    • This might be caused by permission issues in one of the target locations

    For the first issue Microsoft has a tool that might fix that:

    In the second case you should check permissions in the relevant locations.

    Good look with fixing this.




Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks