Today my VS2013 started crashing. The crash happens after 20 seconds or so. It loads up and I can interact with the application, but it crashes every time regardless of whether I click/type or leave the entire computer alone.
Tried /safemode and that crashes too.
Tried /resetsettings and /setup, but that didn't help.
Tried debugging the issue using VS2012, but then learned that that IDE crashes as well.
Uninstalled Git Extensions (commonly cited for causing startup crashes) but that hasn't helped.
Rebooted.
Deleted %LocalAppData%\Microsoft\VisualStudio and %LocalAppData%\Microsoft\VSCommon. No dice.
Tried starting VS with and without a solution open.
The event log contains this error and this info message. This is the WER log file, though I cannot construe anything useful from it myself.
Does anyone know how I might go about getting a working IDE again?
NsAppName=devenv.exe
Sig[3].Value=igdumd32.dll_unloaded
igdumd32.dll is the Intel HD driver. We just had a similar issue some time ago.
Go to Intel.com, download the latest driver and install it.
Late but could be useful to someone in future:
I had the same issue recently with VS 2010 64 bit.
My OS is Windows 8.1 64-bit.
The problem arises because of some compatibility issue between the Intel graphics driver and WPF. I solved the issue by following the workaround from here, https://support.microsoft.com/en-us/help/2894215/you-experience-performance-issues--product-crashes--or-rendering-issue
Related
Afternoon all,
I had been using the Visual Studio 2022 Preview. Recently I decided to switch to the Release version. I uninstalled VS2022 Preview and installed the 2022 Community Release.
The install runs fine and completes with no issues. However when trying to run VS2022 It comes up with the error attached below.
From my talks with MS found at https://developercommunity.visualstudio.com/t/Unable-to-launch-VS-Comunity-2022-after/1596301?entry=myfeedback&viewtype=all It appears VS2022 Community should be running version 17.0 of the .Threading DLL. However no matter what I have tried it refuses to load.
I have run the uninstaller with -F. Re-installed several times.
Attempted to install 17.0 to the GAC but this does not change the outcome
As per the post on the developer community pretty much everything short of re-installing windows (Which I am 100% trying to avoid)
I ran the FusionLog viewer (Attached) and it looks like there is something re-binding this to the 17.1 .threading version however I know very little about how this works and where I might find a solution, Hence, I am here :). Although my post on the DeveloperCommunity is still active I'm hoping a resolution here maybe faster!
Thank you!
I have this error too, and its becouse you dont have defined startup project.
Right click on your startup project and choose "set as startup project".
Actually the above is incorrect, you can't even get to the startup screen.
The correct answer is you need to remove the V15 version of the dll from the GAC. Instructions from MS can be found here.
just starting to look at the Cordova tools for Visual studio.
Creating a blank Cordova probject, I am able to run (F5 debug), for Android and IOS (emulators), and also x86 windows, but for either Any CPU or x64 I get the following error..
The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
So I have seen mentioned elsewhere that VS (32 bit) needs to run the above for 64 bit debugging. I have no problems running and debugging a classic desktop WPF.
I have tried disabling both my firewall (Zone Alarm) and any antivirus (Avast), but made no difference.
Anyone have any ideas what the problem could be here (or how to diagnose)
Thanks in advance for any help!
I have this same problem. I use the same applications as you do, Zone Alarm and Avast. If I try to debug and get that error, disabling or stopping the programs do not help. You need to close VS and restart it with the offending apps already disabled, then you'll be able to continue.
I stumbled across this question because I am looking for a way to keep from doing this.
Everything was going fine but the next day, when I opened the visual studio It showed error as
this error occur at every project files and at the starting.
I uninstalled and reinstalled the VS again but also nothing is improved. when I started my pc in safemode , in that case visual studio runs fine however when I opened in normal mode , It shows the error.
Also using command like devenv or devenv/safemode or devenv/resetsettings pops the same error message.
In my experience and from what I've heard from others, VS2005 has problems on newer OS's and needs to be run in a XP VM for reliable results. Some editions of Win7 have a nice transparent way of doing that for software that doesn't like newer OS's, but the VM component needs to be installed first.
I also recall VS getting fouled and needing to be ripped out and re-installed to work again. In your case, re-installing from original media did not include all the service packs and patches, and it probably only worked at all due to updates and a bit of luck. You might try restoring from a backup rather than re-installing, but it's really a lost cause.
Recently, I needed to refresh my Windows 8.1 PC, and now that I have finally finished getting all of my programs reinstalled and everything is back to normal, I am ready to finish work on my Windows 8.1 app, but I am having an issue with compiling my apps. Every time I try to compile, I get the following error.
Now normally when I need to refresh my developer licesnse, Visual Studio tells me, but this time I didn't get any prompt at all, and that is the error that I got when trying to compile. How can I fix this? I am installing updates for Visual STudio at the moment, and I am hoping that doing so will somehow magically fix the problem, but I am also aware that it probably won't.
EDIT: Now that I have updated, the message has been shortened to "Can't resolve Windows.metadata."
For some reason, even though the Windows 8.1 SDK is supposed to be installed with Visual Studio Ultimate 2013, it wasn't for me. I was able to find the Windows 8.1 SDK by Googling it, and it came up as the top result. I installed it, and suddenly all of my errors went away and Visual Studio started recognizing them as legitimate Windows 8.1 app code.
I am getting the following error when trying to install Visual Studio 2005 on my 64bit, Vista computer:
"1305.Error reading from file
C:\Program Files (x86)\Microsoft
Visual Studio 8\Microsoft Visual
Studio 2005 Standard Edition -
ENU\SITSetup.dll"
I have successfully used the same DVD's to install Visual Studio on my old XP machine, and I can find the file (SITSetup.dll) on the DVD...and copy it off...so I don't think this is a case of having a bad DVD. At the time the error message pops up, I can see the file on my hard-drive, but it has a 0 size.
I've Googled this problem, and found some ideas, but nothing has worked thus far. Any suggestions would be appreciated.
I have to confess on this..especially since someone voted for the question.
Everything I said in my original posting about using the disks successfully in the past -was true. However, after innumerable shots at trying to get this install to work, I finally went back and looked at the DVD, and found that either myself, or one of my kids, left traces of food stuck to the underside of the DVD. After cleaning the DVD off, the install worked fine. This is embarrassing.
I assumed the DVD was fine because I had used it before, as well as being able to copy files off it. However, the last time I used it was years ago, and sometime in between then and now...something got on it. I guess the lesson here is never skip the basic checks!
I just installed it yesterday on my Vista box (32-bit, which may be the problem). It seemed to go through fine so I don't know what to tell you other than than when I first launched the app it notified me of "known compatibility issues" and recommended that I install both the SP1 and Vista SP! updates. No further issues past that.
As such, I would suspect either a problem with the 64 bit OS (though Microsoft says it's fine...) or other software on your machine. If you have a virus scanner running, for instance, disable it while installing.
If your Vista machine is a guest running under VMware, try copying the entire DVD to your hard drive and install from there.
I don't know if the same random glitches occur on real machines.
I can confirm that this is a problem for me on Windows 2008 Server while not on XP or Vista (all 32-bit). Not sure why there's any kind of issue here but it seems to be permissions related.
Also tried run as administrator etc but no luck.