garmin POI loader won't run

 

I chkd other threads and I don't find the exact same issue, so I started a new one. I am rebuilding my laptop system and installed POI loader. When I clk on the exe file I get nothing but a quick flash of a loading icon.
Webupdater does the same thing. Garmin Express & Mapsource both run.
I tried installing & running in compatibility mode and as admin. Nothing. I am running on an HP i7 laptop, 256GB SSD, 8GB ram, and W7 ultimate.
Any ideas please

install from

I also found it does not install from my NAS unit - I had to move it to a local drive first.

Download anew

solved

interestingly I did not realize the webupdater had actually opened and was waiting for input.

In that condition, the POI loader will not open.
Bottom line u can't run both at the same time.

Interesting

ruggb wrote:

interestingly I did not realize the webupdater had actually opened and was waiting for input.

In that condition, the POI loader will not open.
Bottom line u can't run both at the same time.

Very interesting. You are correct. WebUpdater and POI Loader can't simultaneously be running, at least for you and me on Windows PCs. For me, the first program opens just fine, but the 2nd does nothing.

Same

Same for me with Windows 8 64bit.

--
Nuvi 350, 760, 1695LM, 3790LMT, 2460LMT, 3597LMTHD, DriveLuxe 50LMTHD, DriveSmart 61, Garmin Drive 52, Garmin Backup Camera 40 and TomTom XXL540s.

I had this issue before, I

I had this issue before, I had to shut down both apps and once I ran them at different times, problem solved. I guess somewhere this is a conflict with those programs

--
NickJr Nuvi 3597LMT

Is this a newer Garmin?

I had a bunch of POI files for an older Garmin 780. When I got a 1490 the files wouldn't load, but I got some errors. After a little noodling I realized that it was the files that started with a number that didn't load. I had numbered files like: 1_favorites.csv and 2_family.csv. I changed the names to use letters like: a_favorites.csv, etc. and it works again.

I'm guessing it is the fact

I'm guessing it is the fact that both apps want to access a unit on the USB port. It would be nice if the issue popped an error telling u that.