CODEWITHSUNDEEP
visual-studio-2010crash
Tharik Kanaka
Tharik Kanaka

Reputation: 2510

Visual Studio crash at start-up

My Visual Studio began crashing at start-up. In my search for finding a remedy, I found these two suggestions, but neither worked for me:

However, I found that if I logged into a different Windows account, Visual Studio was able to run from that account without crashing.

Here is an error code that that I observed in the crash report:

LCID: 1033

Can anyone provide a solution for returning my Visual Studio to working order?

Upvotes: 20

Views: 43424

Answers (12)

oscar1919
oscar1919

Reputation: 139

I had the very strange phenomenon that both Visual Studio 2010 and 2013 on a Windows 7 machine crashed when run in a remote desktop session, started from a Windows 10 pc. Debugging the crash showed a CultureNotFound exception. It was caused by regional settings on the Windows 10 pc, which could not be translated in something understood by Windows 7. I had language English(Belgium) with an Azerty keyboard. I added and selected English(UK) with an Azerty keyboard and the crashes disappeared. No other programs suffered from this.

Upvotes: 1

El Richbo
El Richbo

Reputation: 1

I had a similar problem, both VS2015 and VS2013 would crash at startup. Tracked it down to an application I installed which put .net 4.7.2 on the system. Once i removed that app, removed .net, and reinstalled .net 4.6, Visual Studio started working again.

Upvotes: 0

DavidRR
DavidRR

Reputation: 19457

My colleague recently experienced a problem with Visual Studio 2013 crashing on start-up. Unfortunately, we found that the approach recommended in the answer by @Arun M did not solve the problem:

devenv.exe /ResetSettings

...however, using a different command line argument did:

devenv.exe /ResetUserData

An easy way to run devenv.exe is via the Visual Studio command prompt; on Windows 10, it can be found here:

Start Button => All Apps => Visual Studio 2013 => Visual Studio Tools =>
  VS2013 x86 Native Tools Command Prompt

For more about these command line arguments for devenv.exe, see this answer to this related question: How do I truly reset every setting in Visual Studio 2012?. ⚠ In particular, please note the cautionary statement in that answer about the /ResetUserData command line argument!

Upvotes: 4

binki
binki

Reputation: 8316

Once I accidentally pressed a random key combination (maybe something like ctrl+', but I didn’t realize I was holding ctrl down so I forgot what keys I hit by the time I realized something bad had happened) that resulted in VS Professional 2017 15.3.5 crashing within half a minute. After relaunching, I found that VS would be interactive for a few seconds before it would crash within half a minute. It was really too fast for me to try to figure out what I had accidentally activated or for me to disable it before VS would crash. Also, it would even crash if I didn’t open any solution, so I figured it was not something that deleting a .vs (per project/solution Solution Explorer/open files state) folder would fix.

To fix, I followed Arun M’s comment and renamed my %LOCALAPPDATA%\Microsoft\VisualStudio\15.0_3f4d04be folder. You will need to adjust the path for the edition/version of VS that is crashing. On my machine, I think 15.0_3f4d04be is Professional and 15.0_0fed6c59 is VS Community Edition. You’ll probably have to guess based on the folder’s modification timestamp which is probably going to reflect the date you last used that edition of VS.

After renaming the versioned dotfolder, VS launched without crashing. It started with default settings but automatically restored some of my settings through the cloud sync stuff after a minute of running and it even remembered my account information so I didn’t need to sign in.

I did not need to rename my %LOCALAPPDATA%\Microsoft\VSCommon folder (which Arun M had also suggested).

Upvotes: 0

stratovarius
stratovarius

Reputation: 3880

I just changed the windows language in the bottom right to "EN", then started as admin. And it worked, interesting..

Upvotes: 1

Oliver
Oliver

Reputation: 9508

For me it turned out to be the plugin that GitExtensions installed into Visual Studio 2013.

-- UPDATE: try this before uninstalling GitExtensions

@Enceradeira proposed in the comments to uncheck the Show current branch in Visual Studio option. In GitExtensions, you get there via Tools -> Settings -> Appearance:

enter image description here

-- END OF UPDATE

After uninstalling GitExtensions and reinstalling it with all VS plugin unselected my VS runs smoothly again.

I even put together a blog post about this issue because it bugged me so much.

Upvotes: 62

zax
zax

Reputation: 956

If coincident to these Visual Studio crashes you are getting "Heap corruption" (Exception code: 0xc0000005) errors in your Windows Application log (Faulting module name: WindowsCodecs.dll), here is something worth checking into: A faulty WIC component within Expression Blend can cause ALL versions of Visual Studio to crash upon launch, as well as cause Internet Explorer to crash upon visiting many, if not most sites. Even though Microsoft distributes this component, they call it a "non-Microsoft component". As such, a Visual Studio reinstall won't fix this,, an OS reinstall over existing Windows installation won't fix this, and a system file integrity check won't detect it.

If my case, the misbehaving codec was "C:\Program Files (x86)\Microsoft Expression\Common\Imaging\4.0.360.0\PSDCodec.dll", and simply unregistering this component got my Visual Studio working again from consistent startup launch crashes.

I post this in hopes this solution to one source of Visual Studio crashing might save others from the $500 Microsoft support incident fee and week of downtime this caused me.

Upvotes: 2

Saxon Druce
Saxon Druce

Reputation: 17624

I had a crash on startup (or soon after startup, before opening any solution) occurring in git2-msvstfs.dll, caused by placing a 3GB temp file into a directory within my solution. Deleting the file fixed it.

Upvotes: 0

Stefan Michev
Stefan Michev

Reputation: 5093

In my case VS used to crash on a single solution. I resolved the problem by deleting the respective solutions's user file: SolutionName.suo

Upvotes: 9

parliament
parliament

Reputation: 22954

For me it was being caused by Web Essentials and I was able to resolve by disabling it, restarting VS, enabling it back , restart again. Works now.

Upvotes: 0

jossif
jossif

Reputation: 409

Try to run VS as administrator. That's necessary in my case.

Upvotes: 3

Arun M
Arun M

Reputation: 1452

Since you're able to run with another user login, something may be wrong with your local settings, you can try to reset them: devenv /resetsettings in Start menu -> Run.

Warning: this will restore visual studio to default settings.

Upvotes: 23

Related Questions