Hi,

Sorry to hear about this problem. It is caused by Atmel Studio re-creating registry keys which it does not normally do.

I expect the setup error is also related to some conflict causing Atmel to attempt re-initialization.

You will have seen in previous posts that normally this issue is a one off. 

Unfortunately Visual Micro has no control over the Atmel registry and only writes to the Atmel registry during install or repair of Visual Micro.

Another point of interest is that in a couple of rare cases we see the CM_SETUP error due to a clash of "some sort" behind the scenes of Visual Studio. The problem manifests itself by instructing an already installed add-in to commence first time setup. It is important that Visual Micro detects this invalid request from Visual Studio to re-initialize the addin because as per the Microsoft documentation this must happen only once.

So sorry for so much useful background info but I thought it useful to explain as much as possible. Obviously I mention Visual Studio because Atmel is Visual Studio and the setup issue has happened on a couple of occasions in both products. I only ever encountered it personally once and that was after installing another add-in. Art the time I had a number of other add-ins installed so it is not a general issue with other addins.

I can say that Visual Studio relies heavily on the office toolbar/command system so ensuring that your windows and ms office are up to date might be a potential solution.

Do you have other addins installed in Atmel? Please look at "Tools>Addin Manager" and "Tools>Extension Manager" to determine the answer to this question.

Thanks