Google Earth custom MSI from EXE

Hi my first post, so please be gentle.

What I wish to do is create a custom MSI from a exe or if someone knows of an easier way to run Google Earth with no user intervention, I have extracted the GE.exe to a folder on the C: Drive which gives me around 70mb of files and the like, these include the GoogleEarth.MSI, Program Files folder and an LocalAppData folder.

I am using Wise Installation Express 7.0, I have tried to ammend the actual GE.MSI and incorporate the above said folders, and also tried to add the GoogleEarthWin.exe in a New Project to then install the exe using a command prompt, all to no avail.

Could someone shed some light in waht I am doing wrong or am I nearly there.

Hope the above makes sense as the hair from the cranium is slowly and painfully being extracted.

Cheers again in advance for any help or advice.


0 Comments   [ + ] Show comments

Answers (4)

Posted by: dunnpy 12 years ago
Red Belt

Have you tried the steps in the Package KB for Google Earth?


Posted by: @it 12 years ago
Yellow Belt
Many thanks for the info and pointing me in the direction of the link, now I need to get my head down and understand all the linked.

Cheers again Dunnpy.

Posted by: zzpack 11 years ago
Orange Senior Belt
I´m reusing this old thread...
I´m making a package of Google Earth 6, and it works just fine. But the font in the installation dialog window is messed up,
something along the way like this "[font="times new roman"]▫▫▫▫▫▫ ▫▫▫▫▫▫ ▫▫▫▫▫▫". The same goes for the self repair dialog window.

The command line is: msiexec /i "Google Earth.msi" /qb (I know I can use /qn)
or if I want another language its msiexec /i "Google Earth.msi" Transforms=1053.mst /qb
Same problem, on both.

Do you guys have any clue to why this is happening? Bad msi creation only?
Posted by: jmaclaurin 11 years ago
Third Degree Blue Belt
Messed up text can sometimes be caused by something that has hooks into the OS, usually into a driver. The cases where I have seen it happen most are with a faulty NIC driver and very poorly made VPN software. I know this doesn't make a lot of sense, but there it is.

And yes, it could also be the font used when creating the software package in the first place. You can usually determine if this is the case if you build a vanilla OS, unpatched and no software and just the most basic drivers to just make it function and then test your software again.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ