Unable to run BaseCamp

No idea. BaseCamp is still running perfectly on both my PCs, one with Win7 and one with Win10.

Have you recently done a Windows update? What happens if you go back to an earlier restore point?

Have you recently done a Windows update? What happens if you go back to an earlier restore point?

This would only mean downloading the Windows updates again. What would that achieve? As it's happening on two PCs, it's most unlikely that a corruption would occur on both

The current version of BaseCamp stopped working on two different home computers, both running Windows 7 Pro. Incidentally, this happened after downloading map updates.

An old version 4.2.4 will run on both computers, after removing the current version.

The current version continues to run on my new mobile Surface Pro 4, but the databases are not compatible.

This suggests a difference between 4.2.4 and the current version.

Now after over a month, Garmin technical support can't offer a solution. Yesterday's suggestion was - "Full uninstall of Garmin Express". ! ! ! ! ! Express was removed on one PC a month ago, incase there was any interconnection.

Looking at the error message - 'not registered |2633', as a retired programmer, I would expect '2633' to point to part of the code where the error is happening. Also 'not registered', should also give a clue. Is one of my many Garmin GPSrs not registered (they are all registered) or has a downloaded map update lost it's registration on those two PCs?

So another disadvantage of BaseCamp over MapSource is that suddenly one looses access to all of ones waypoints and tracks. Fortunately I still have all of my MapSource data files.

As version 4.2.4 will run, and 4.6.2 will NOT run; does anyone know where I can download an in-between version 4.6.0 through to 4.6.1? I could then try and access my database using one of them.

Going back to a previous restore point doesn't mean you need to download the Win update again, at least not initially. If BC then works it'll point to a Windows rather than BC issue, as I said previously I've never had issues.

Previous versions of BC are available through http://gawisp.com/perry/mapsource/ if you want to try an intermediate version.

Previous versions of BC are available through http://gawisp.com/perry/mapsource/ if you want to try an intermediate version.

Thanks. I've edited my last post to correct version numbers.

I have downloaded the .EXE for 461, 452, 447,435 and 425 from that archive website. Installing one, then deleting it before downloading and installing the next one. Each being the highest minor version before the next higher version release.

After 461, I decided to download the current 'USBDrivers_2311.exe' to see it that made any difference as I had been using 2310 previously. It made no difference.

461, 452, 447 and 435 all failed with the same error. However 425 does run, so I've got one minor version higher that will run!

I have Ozi Explorer and QuoVadis 7 www.quovadis-gps.de , so I'll give up on BC, if Garmin Support can't solve the problem, in the next few days.

Incidentally, QuoVadis 7, has the same HERE mapping as used in Garmin GPSrs www.quovadis-gps.de/HEREZ-vectorial-Maps , so one can navigate while viewing ones waypoints and tracks. It is also possible to overlay the HERE vector maps with raster maps.

Remember the ability to navigate on a laptop with the early versions of MapSource, before it was removed.

I have been running BC for years on multiple computers running XP pro and home, Win 7 pro, Win 8.1 home, and Win 10 home. Never had the problem you are having.

Agreed, it'll be a system issue on his PC but exactly what is pretty much impossible to determine remotely.

Agreed, it'll be a system issue on his PC but exactly what is pretty much impossible to determine remotely.

Its not a single PC issue. I've been busy producing e-mails to Garmin Support on this problem.

Chris, mentioned that Microsoft .NET Framework 4.5.1 was required a little while ago. I checked to confirm that I was using a suitable version at that time.

However, yesterday, I checked and discovered that both CF-31 & CF-53 were updated by the regular Microsoft updating of Windows on 24-06-2017 to version 4.7.02053.

So this could be what has triggered the problem?

Later today, I had a look at some files that I've saved on my PCs. I use a program that will produce a screen dump when pressing a certain key. The filenames include the date and time of the screen dump. I normally keep them for later confirmation of certain events if required.

I've found three files showing the display error panel produced by BC, giving details of the error.

The oldest two, one from the CF-31 and the other from the CF-53, are dated 25th June. This is the day after the Windows update.

I would suggest that this is a very strong indication that here I've found the area of the problem.

I passed this information to Garmin Support yesterday.

So it's a system issue at your end then? Well done though on tracking it down.

However I don't believe that the MS update alone has caused your issue as I keep all my systems fully up to date and they're working fine, I suspect something else is going wrong. It will be interesting to hear what eventually is found to be the cause.

I normally update my Windows 7 Pro PCs on a monthly basis, using the Microsoft monthly roll-up. It's a a repeating entry in my diary. Today, I used an old Dell running Windows 7 Home, which only gets an update when it's used. I noticed that Microsoft had a .NET update. BC is not on this PC.

So I did an extra update on my CF-53, which included the .NET update. Then I did a clean install of a today's BaseCamp download. (incase Garmin had done a hidden update. i.e. keeping the version number unchanged.)

The current version of BC now works. The CF-31 is being updated as I type!

SO PROBLEM SOLVED.

Great!