Google earth

Google earth

I have GE 7.1.8.3036 (Earth Pro) working from Basecamp on two 64 bit Windows 10 machines.

I had to do the registry trick shown above on one of the machines.

I also have things working with the registry trick but on a Win7 64-bit system. However, I needed to make a slight change in this part of the instructions:

"From the Command Prompt type the following as applicable and press ENTER:
(Make sure you are in the C:\ root directory)

"C:\Program Files (x86)\Google\Google Earth Pro\client\googleearth.exe" /RegServer (works with Google Earth Pro in Win 7...10)" because googleearth.exe wasn't in the client sub-folder but in the sub-folder above so I used this command line: "C:\Program Files (x86)\Google\Google Earth Pro\googleearth.exe" /RegServer

Google earth

I also have things working with the registry trick but on a Win7 64-bit system. However, I needed to make a slight change in this part of the instructions:

My earlier change (mentioned above) was only because I was using an older version of Google Earth Pro (7.1.2.2041). When I updated to GEPro 7.1.8.3016 the sub-folder content changed and I had to run the original command line instructions to get things working again.

It's interesting to note that Garmin Support states the latest release of GE function no longer works with BaseCamp...
https://support.garmin.com/faqSearch/en-US/faq/content/go8phBi0Lt6nSjgcTpm4r8

However Garmin neglected to date or list the GE or BaseCamp versions this applies to. How useful is that?

It's interesting to note that Garmin Support states the latest release of GE function no longer works with BaseCamp...
https://support.garmin.com/faqSearch/en-US/faq/content/go8phBi0Lt6nSjgcTpm4r8

However Garmin neglected to date or list the GE or BaseCamp versions this applies to. How useful is that?

Which probably means that Garmin will remove that menu function from BC one day hence messing up those of us who still use it with a previouis GE version. Shame!

I have no problems using the latest Google Earth Pro (7.1.8.3036 (32-bit)) with the latest Basecamp (4.6.2) on two different Windows 10 PCs.

I did have to apply the /RegServer patch a while ago after an update.

Which probably means that Garmin will remove that menu function from BC one day hence messing up those of us who still use it with a previouis GE version. Shame!

We really don't know what it means (especially, given that there's no date on the announcement and the feature works fine with the latest version of Google Earth).

Being able to call Earth from other programs has little to do with Basecamp specifically. That is, Basecamp is using an Earth feature (Earth is not "supporting" Basecamp).

I don't think it's hard to provide the feature of calling Earth from other programs.

I suspect that Google Earth doesn't want to deal with Basecamp problems (Basecamp isn't their program).

BaseCamp to Google Earth

I have no problems using the latest Google Earth Pro (7.1.8.3036 (32-bit)) with the latest Basecamp (4.6.2) on two different Windows 10 PCs.

I did have to apply the /RegServer patch a while ago after an update.

I had the same problem reappear recently as well. Reissuing the patch fixed me up again.
In my case, my GoogleEarth.exe did not live in the exact same location specified in SUSSAMB's original solution. That may explain why the patch might not work for some people, if their install folder was also slightly different. I would advise using File Explorer to follow the directory path in the instructions to see if they find their GoogleEarth.exe in the right folder and if not, edit the RegServer patch to show the correct path.

View Google Earth doesn't work

I get the same error message as described above. I have Win 10 64 on a Dell Imspiron laptop. When I click View> Google Earth> Item or Selected Item, I get the error message to install Google Earth and have it open. It is installed and open. This problem just appeared about 2 weeks ago. It had been working fine up to that time. Google Earth open and then View> Google Earth> Selection or Item named.
Thanks
Larry

SUSSAMB - Thank you

I thought Google had resolved this but maybe not. Anyway, try this method:

From the Command Prompt type the following as applicable and press ENTER:
(Make sure you are in the C:\ root directory)

"C:\Program Files (x86)\Google\Google Earth Pro\client\googleearth.exe" /RegServer (works with Google Earth Pro in Win 7...10)

"C:\Program Files\Google\Google Earth Pro\client\googleearth.exe" /RegServer (Google Earth Pro in XP)

"C:\Program Files\Google\Google Earth\client\googleearth.exe" /RegServer (Google Earth in XP)

"C:\Program Files (x86)\Google\Google Earth\client\googleearth.exe" /RegServer (Google Earth non-Pro on Win 7, 8.x and 10)

Note for those not used to using the command line in Windows, the double quotes in all of the examples are critical. They MUST be there and in the indicated places or you'll get an error that the directory name is invalid. It won't harm anything; it simply won't work.

Just a quick thank you. I followed your instructions to add
"C:\Program Files (x86)\Google\Google Earth\client\googleearth.exe"
It worked.

Now on to the next thing to figure out.

+1 sussamb

Just a quick thank you. I followed your instructions to add
"C:\Program Files (x86)\Google\Google Earth\client\googleearth.exe"
It worked.
Now on to the next thing to figure out.

I was glad to find SUSSAMB's original post about this because I, too had GE break a couple weeks ago.
However, the fix did not work at first, so I thought I'd share what was a little different for me in case others have the same difficulty.

1. I wasn't in the root of C: . Been a long time since I had done much work in CMD and I forgot. The command to type is CD C:\ Gotta have that last backslash.
2. For some odd reason, GE on my hard drive did not live exactly where the instructions said it should be. Easy to figure that out; just right-click on the Google Earth (or Google Earth Pro) icon and select properties. It will show you the exact path in the 'Target' window. Edit the command string to match that exact path if it's different.
3.I had to open the command window as Administrator in order for the command to work. This is done by right-clicking on the icon and selecting "Run as Administrator". I didn't get any error messages when it failed, it just didn't work until I thought about trying it as Administrator.