I never had this problem with any MpLabX installation including 4.10 and 4.15, or XC8, XC16, XC32.
But today it caught me on another Windows 10 x64 PC, where I use MpLabX 4.10 and XC16 1.33 without any problems since installation 3 months ago. Waiting for v 4.20 is not an option and who knows what will change.
Here is a short step by step history of today (no PC restart during the experiments).
I always do all my compiler installations outside of MpLabX and avoid that MpLabX is running
and of course my internet connection is stable, whatever MpLabX tells)
a) I installed XC32 v2.05 (first time installation). -> no problem, everything working as usual.
b) Decided to install side by side MpLabX 4.15. (allowed the installer to reuse settings from previous installation).
Active project was a PIC32 project with XC32 v2.05.
-> problem appeared immediately. It did not just appear when opening the project configuration, it appeared more often, way too often, not possible to seriously work.
As said, I just installed the most recent XC32 version just 15 minutes before, so the Toolchain was up to date.
c) Deactivated the Notification PlugIn as described in #11. Also restart of MpLabX (which MpLabX also tells you need to do). But No change, dialog still popped up with same frequency. (I also verified that Plugin appeared deactivated now)
d) Decided to install XC32 v2.05 again (same installation file). I'm not sure whether it should, but it did not tell me, that this version is already installed.
-> Start MpLabX 4.15, problem gone !
e) Very soon, after 1 or two minutes I got the notification bubble, that a new XC16 compiler 1.34 is available.
That's correct, because I only have 1.33 installed. So this has nothing to do with the annoying popup dialog. I only mention it, because it appeared in spite of the "Notification" PlugIn deactivated. what's the PlugIn good for then ?
Anyway, I reactivated it.
Whatever is the real reason / bug, a solution might be to reinstall the tool(s) = compiler manually outside of MpLabX.
FWIW, I did install the compilers stand-alone, the error pops up when I'm trying to select the correct toolchain.
Yes, I did and also got the error then. So in my case the difference was to do the installation once more although this logically would not be required.
post edited by rodims - 2018/05/19 05:44:27