VsVim is disabled every time I start up VS

Created on 5 Jul 2016  ·  4Comments  ·  Source: VsVim/VsVim

I have to go into Extensions and enable it, then restart Visual Studio.

Any ideas as to why this would be happening?

Most helpful comment

Same was happening here - this began happening within the past month or so.

Ended up not being the extension. I somehow ended up with multiple versions of VsVim installed and this would cause a conflict when loading.

The solution was to uninstall all versions of VsVim and then reinstall. Keep going to Tools -> Extensions and Updates and uninstalling VsVim/restarting until VsVim no longer appears in the list. Took me 3 uninstalls.

Reinstalled and now works fine :) I've heard of this happening with other extensions as well.

Hope that helps!

All 4 comments

Same was happening here - this began happening within the past month or so.

Ended up not being the extension. I somehow ended up with multiple versions of VsVim installed and this would cause a conflict when loading.

The solution was to uninstall all versions of VsVim and then reinstall. Keep going to Tools -> Extensions and Updates and uninstalling VsVim/restarting until VsVim no longer appears in the list. Took me 3 uninstalls.

Reinstalled and now works fine :) I've heard of this happening with other extensions as well.

Hope that helps!

I've seen this behavior before myself on a short term basis on one of my machines. I always assumed that because of all of the extension work I do I had somehow gotten Visual Studio in a bit of a corrupted state. Based on this though it seems to just be an issue with Visual Studio itself.

Unfortunately though this is not anything that I control. This is controlled by Visual Studio itself and hence I can't really do anything to fix this. I will follow up internally though, see if this is known problem, and potentially how to work around it.

Same was happening, too.

thanks @jacres ! it works for me

This happened to me too. I followed @jacres advice and uninstalled VsVIM and restarted. I had to do this twice before it finally disappeared. It's working fine now. Thanks!

Note that my first attempt failed because I stupidly had another instance of VS open at the same time.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jnothstine picture jnothstine  ·  7Comments

thelamb picture thelamb  ·  5Comments

drhoda picture drhoda  ·  7Comments

myopicmage picture myopicmage  ·  5Comments

academician picture academician  ·  3Comments