Hi Simon,

Please post in your own thread. You have a config issue by the looks of things. It's quite different to this users report and I will give you different instructions

Thanks

Thanks no need to remove before updates I was just being extra safe in previous discussions.

Sorry I forgot to post a link to the beta before!

The trace clearly shows your windows wmi database is still corrupt and that I forgot to add a workaround to one area of achiever. There is a new version 1403.25 here with the workaround https://visualmicro.codeplex.com/releases/view/106554

Thanks

Sorry to hear that. We can see in the recent visual micro traces that your machine certainly has a corrupted wmi database. 

The Visual Studio Shell error is also an indication that there are some problems with your pc and the fact that the Atmel installer can no longer run is again an indication of windows or hardware problems.

I'm sorry I can't be of more help. 

I explained that Visual Micro simply reads the wmi using the standard microsoft api which can be seen in the trace. Windows update has also failed for you previously and still shows an error for the mssql updater (if I recall correctly). Now we see the installer that Atmel uses is failing. The Atmel install is two installs in one. Usb Drivers then Atmel Studio which suggest that the two errors you see are a result of those two installers failing. 

I don't know what else to say except that the easiest discussion might be with Microsoft about the windows update wmi error. However, you report that a working AS6.1 suddenly lost a component, unless AS6.1 uses the wmi database, I guess that could possibly be a hard disk failing?

Either way I am here to help if you think I can. Best of luck

Does that mean you get an error on screen or just the apps list is empty?

If apps list then more diagnostics in this version now that we don't care about wmi errors

https://visualmicro.codeplex.com/releases/view/106554

Great. Are the provider load errors just in the trace or are you getting on screen dialog warnings?

I know that the wifi is disabled at the same time as the wmi corruption is detected. There will be a new visual micro over the next week which separates these two things. 

You will then be able to switch on Network Discovery in the Communication tools>options. 

It will have been switched off automatically by Visual Micro due to the wmi problem. I suspect you can not currently switch it back on without loosing your serial ports but you can try it if you want it's easy to switch off again and won't kill your config 

I have sent you a PM with a link to a 3 machine debugger for all your hard work. I think users with windows wmi issues are going to find a huge benefit from your persistence.

Thanks again

WiFi: fantastic!

Elsewhere: have notice a quirk which I took a quick look for in the forums and didn't find anything. I have a Uno connected to just one of two LCDs. The sketch has libraries for both, the LCD not being used commented out. Both LCDs use the Wire library. This does not build:

//LCD
/*
//Adafruit RGB LCD Shield
#include <Wire.h> //one must be commented out else cannot build
#include <Adafruit_MCP23017.h>
#include <Adafruit_RGBLCDShield.h>
Adafruit_RGBLCDShield lcd = Adafruit_RGBLCDShield();
*/
//Adafruit I2C backpack
#include <Wire.h>
#include <LiquidCrystal.h>

void setup()
{

  /* add setup code here */

}

void loop()
{

  /* add main program code here */

} 

And gives error message:

Compiling 'canbuild' for 'Arduino Uno'
System.ArgumentException: An item with the same key has already been added.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at processing.app.MCUTargetPlatform.getImportedLibsOfSketch(List`1 importedSketchHeaders)
   at processing.app.SketchBuilder.preprocess(String buildPath, PdePreprocessor preprocessor)
   at processing.app.SketchBuilder.preprocess(String buildPath)
   at processing.app.SketchBuilder.build(String lbuildPath, Boolean verbose)
   at processing.app.SketchBuilder.build(Boolean verbose)
   at Visual.Micro.Visual.Studio.Arduino.AddInApp.CompileDo(Project oProject, Boolean IsDebugStartCommand)
   at Visual.Micro.Visual.Studio.Arduino.AddInApp.Compile(Project oProject, Boolean IsDebugStartCommand) 

Commenting out one of the Wire.h -- doesn't matter which one -- and it builds OK. I.e.:

//LCD
/*
//Adafruit RGB LCD Shield
//#include <Wire.h> //one must be commented out else cannot build
#include <Adafruit_MCP23017.h>
#include <Adafruit_RGBLCDShield.h>
Adafruit_RGBLCDShield lcd = Adafruit_RGBLCDShield();
*/
//Adafruit I2C backpack
#include <Wire.h>
#include <LiquidCrystal.h>

void setup()
{

  /* add setup code here */

}

void loop()
{

  /* add main program code here */

}
 

Do not see this issue with Arduino IDE or Eclipse/Arduino.
And thanks for the offer of the debugger (which just incredible) for which I filled and sent the form.