also @ TechSpot: Asus' new lineup of Z87 Haswell motherboards revealed

Issue with Hamachi installation

Discussion in 'Software Apps' started by Kagamex, Sep 30, 2012.

Post New Reply
  1. Mavrickx888 TechSpot Member Posts: 38

    Interesting... I'm speculating here, but based on what it's saying (Where it says "failed" next to GetRegValue, GetServicePat, etc.), it looks like you have indeed gotten rid of everything you possibly can when it comes to Hamachi. Why it's still saying you have a previous version installed is beyond me.

    Here's another complete shot in the dark:
    Try installing with this installer: http://www.oldapps.com/Hamachi.php?old_hamachi=15 (Version 2.0.1.66, released Nov. 9 2009)

    It best matches the date of when you think you installed it. I know it says 2009, but it was the most current version as of summer 2011.

    The basis of my thinking is that maybe the newer versions of the Hamachi installer can't completely detect where the older versions of Hamachi reside and/or cannot completely uninstall previous installations. After doing a little bit of research, just about everyone around the net with a similar problem to yours has one thing in common: they are trying to reinstall Hamachi where the previously installed version is old (Usually around 1+ years). I know this seems unlikely (Seeing as the actual installer probably changes very little from release to release), hence the "complete shot in the dark" statement, but I'm hoping to prevent the seemingly inevitable solution here... reformat.

    If all of that doesn't work, my only guess is that we're focusing on the wrong culprit here. Maybe it's not the installer that's the problem, but something else entirely. However, I'm fresh out of ideas at the moment...
    Kagamex likes this.
  2. LookinAround TechSpot Chancellor Posts: 7,677   +39

    Here's another idea you can try. Install Regscanner 32 or 64 bit version as appropriate for your Windows installation. (IMO best - and fastest - registry scanning tool I've found :) )

    We'll search the full registry for either words Logmein Hamachi and also any references to that product's Windows Installer ID.

    Scanning for the ID
    > Open Regscanner.
    > Copy/paste the Windows ID below as the Find String
    Code:
    2F1C8FD962ED3D9409B931C2C3A5EC6B
    > Set Matching to "Exact Match"
    > Check all Look At boxes to look at: Values, Data, Keys and Search Unicode values
    > Check Scan the following base keys then click on each base key so they're all highlighted
    > Now click OK
    > If anything found, click Ctl-A to select all the registry items found. Then Ctl-S to save. And be sure to change Save As to "Tab Delimited Text". Don't delete anything. Just upload the file to your next post.

    Scanning for text
    > You can start a new scan by typing Ctl-N
    > Type Logmein Hamachi as the Find String
    > Set Matching to "Registry Item contains one or more words"
    > All the other values should be same as we did for above. Click OK. And report any items found (but don't delete anything)
  3. Kagamex Newcomer, in training

    Really sorry about the late reply, been busy the latest weeks. Anyway, here's the file you requested. And a side note, I had to run what most likely is the 32-bit version because the 64-bit version gave me the error code "0xc000007b".

    Attached Files:

  4. LookinAround TechSpot Chancellor Posts: 7,677   +39

    Not sure where this may lead us but here's a few more thoughts based on your scan.

    First
    Here's one of the notable registry keys that appeared in your scan
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{47E16407-05D3-4D2A-B2B9-C30700B7C2AD} Publisher REG_SZ LogMeIn, Inc. 2012-09-29 22:28:08

    This is the section of the registry containing Uninstaller info
    1. Do you still have LogMeIn installed? I'm guessing not...
    2. Note that Windows translates things like Program Names into internal IDs. It uses the internal ID to store data in the registry about the program. In this case the ID is 47E16407-05D3-4D2A-B2B9-C30700B7C2AD. LogMeIn is just a value of the key (Windows would use it to later display it to us humans rather then dispaly the internal ID).

    So do another scan this time searching for 47E16407-05D3-4D2A-B2B9-C30700B7C2AD and post the result. Don't remove the uninstaller key yet.

    Second
    References to that internal ID and LogMeIn text are also found under keys for VirtualStore. I googled VirtualStore Windows 7 and found this M$ KB. It mentions installation issues. See if any of it applies. Common file and registry virtualization issues in Windows Vista or in Windows 7. Though I'd also say don't delete any registry keys just yet but see if any other situation they describe may apply
  5. Kagamex Newcomer, in training

    I searched for the "47E16407-05D3-4D2A-B2B9-C30700B7C2AD" ID and found nothing. Neither did I find anything concerning Logmein Hamachi in the VirtalStore folder.
  6. jobeard TS Ambassador Posts: 12,210   +118

     
  7. LookinAround TechSpot Chancellor Posts: 7,677   +39

    If there's an alternative solution that meets your needs, I agree, would likely be the easiest approach. jobeard can provide more info about Apache and if you google Free VPN, there's other possibilities as well.

    I'll be traveling so if you wanted to explore LogMeIn Ham further would have to wait till sometime next week... and of course can't predict the result.
  8. jobeard TS Ambassador Posts: 12,210   +118

    If you elect to install Apache:
    1. create \Apache
    2. Install into it, not Program Files
    3. allow it to create the Service
    4. install the Apache Monitor
    then use Services.msc to set the Apache Server to Manual start.
    The Monitor can then be used to bring it online at will.

    More on figuration upon request