I am having an issue where my Visual Studio randomly hangs. The issue does not occur during any specific task, but randomly throughout the day.
I have tried renaming %APPDATA%\Microsoft\VisualStudio\ folder to VisualStudio.backup\ to rebuild the folder from scratch. Also tried doing a repair.
Any help would be greatly appreciated.
This may not be the answer in your case but in my case the culprit was the service VSStandardCollectorService. I restarted this service without restarting Visual Studio and I was able to use Visual Studio 2015 again.
I found this out by looking in the Task Manager. Find the visual studio process then choose "Go to details" from the context menu. Then choose "Analyze wait chain" from the context menu of the details item. You will see all the stuff it's depending on in terms of wait, for any item that is hung. FYI: When something isn't hung (or waiting), it doesn't give a wait tree. This really takes the mystery out of hangs.
Related
While updating or uninstalling Visual Studio Installer Projects Extension Preview the step "Microsoft Visual Studio Preparation" is taking enormous amount of time. I may say it gets stuck.
My suspicion is the installer (Windows one, not the extension itself, since it is getting modified--updated or uninstalled) is making changes to the registry.
VS registry entries are too many to investigate them one by one. Re-installing VS is not an option. (I have VS 2013 Ultimate on Windows 8.1.)
So, my question is: is there any tool to repair, optimize, clean, or otherwise modify registry (VS portions only) to get the process quicker? Or some sensitive keys that need to be explored? Seems like there are timeouts involved? (Although I do not find this quite reasonable...)
Or, if I am wrong about the registry, Is there another reason for this symptomatic behaviour? UAC issues? NTFS security? Other?
Any advice?
Thanks.
I just solved a similar issue with installing Visual Studio 2013 Update 3. It was taking over an hour on the "Microsoft Visual Studio Preparation" step.
I fired up Process Monitor from Sysinternals and realised the installer was busy logging to C:\FusionLog. Killed the update process, changed the relevant settings under HKLM\Software\Microsoft\Fusion to turn off assembly bind logging, rebooted to make sure the new settings were recognised, and voila, the "Microsoft Visual Studio Preparation" step took on the order of 10's of seconds.
I hope this helps with your problem because this was extremely frustrating for me. I wasted most of my work day on this.
When "Microsoft Visual Studio Preparation" is shown, the installer is running "devenv /setup" to register any packages and templates. That can take a long time. Though it's not ideal, it's not a bug; it's how Visual Studio works.
See this blog posting: http://blogs.msdn.com/b/heaths/archive/2014/01/21/upgrading-visual-studio-2013-update-to-a-newer-update-may-be-slow.aspx
It basically says there's no workaround to save time, just sit tight:
"There is no current workaround that will save time. You might consider starting the upgrade before taking a lunch or heading out for the day."
It also says the issue has been resolved for future versions of VSUpdate and Visual Studio.
Try to block the antivir activity. As for me, it significantly raised the speed.
For the past couple of days, Visual Studio 2012 and 2013 have been hanging during debug mode. Most of the time, i dont get this issue until further into my project. When i press the Start Button, everything continues as normal, but then hangs with this message at the bottom of visual Studio statusBar.
Inside Task Manager, when i try to force taskkill, or end process/process tree, this continues to stay present in my running processes.
Even after a reinstall, nothing seems to help it. I did see somewhere on the Microsoft Developer forums where a person was told it was something to do with the windows sybmol server?. What do i need to do to fix this issue i am having?
After this occurs once, i am forced to reboot my computer. Even if i open Visual Studio after this happens, it still has the same issue.
I have an issue with Visual Studio 2010 and an ASP.NET 2.0 project.
I have searched StackOverflow for a possible solution to my problem, but even though there are alot of articles related to the Visual Studio debugger, none specifically solve my issue.
Every time I start debugging, Visual Studio tells me that "The breakpoint will currently not be hit. The source code is different from the original version.". In the past when I got this problem, I could solve it by doing a Clean Solution. Or if that didn't work, I could always restart Visual Studio or my machine and the problem would be gone. This, however, doesn't work anymore. The solution cleans and I can rebuild, but the debugger still complains about the source.
I found that if I delete the folder "root" in "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files", the problem is temporarily gone but only the next time I start the debugger, and only for the breakpoints that are currently set in the project. All breakpoints I add when the debugger is running are also not being hit due to the source/original difference.
I don't know how to solve this issue permanently because I don't want to delete that folder every time I have to start a debug session.
I also have a few ASP.NET 4.0 projects that debug just fine.
I use Windows 7 Enterprise (x64).
If someone has a suggestion I would very much appreciate it :)
Try this
Right click solution.
Click "Property"
Go to: "Common Properties" -> "Project Dependency"
Select your "project" from drop down list
Check every item in list of "Depends on"
Click "OK"
Now Open "Task Manager"
And kill all worker process i.e. "w3wp" in case of iis7
Or Kill all "WebDev.WebServer40.exe" process
Now run your application.
I've been using a solution since VS2010 was released. My solution has a number of projects in it. Until a couple of weeks ago, all was fine. All of a sudden, whenever I click the button to start debugging my code, the Visual Studio 2010 installer starts.
It takes around 5 minutes for it to complete and then I am able to debug as normal. If I restart the debug session then I have to wait for the installer again.
I haven't tried cancelling the installer, but I just want to stop it altogether.
Has anyone experienced a similar issue? How can I solve this? Its doing my head in!! :S
Thanks
Neil
I would recommend reinstalling Visual Studio. If that doesn't help something else might be wrong with your system and you may end up to re-image it. Being able to re-image a development PC can be a life-saver at times.
When you say "Visual Studio 2010 installer" do you mean the installer for Visual Studio 2010 or an installer project inside your solution? If it's the latter then you may want to check that that project isn't specified as the startup project (right'click Solution -> Properties -> Common Properties -> Startup Project -> Choose "Single startup project" and specify the project you want the debugger to run when you press F5 or the debugger button. Hope that helps.
EDIT #3 : Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
Sometimes when I run an application from Visual Studio and it crashes or I stop it using the stop button in the debug menu (Debug->Stop Debugging (Shift-F5)), the console of said application stays open... and never closes. I cannot close it by clicking the 'x' button in the top right corner. I cannot kill the process as it is not even listed in taskmgr.
I have seen this problem documented in different places on the web, but no solution so far.
I am running on windows XP SP3, using visual studio 2008 w/ SP1.
1- What could be causing this ?
2- Is there a fix ?
thanks alot.
JC
EDIT: There is no MyApp.vshost.exe process to close, and closing visual studio does not close the console either. Worse even, if I try to restart my computer windows will hang and never close, I need to do a forced shut down.
EDIT #2 : (from Brad Sullivan, Program Manager - Visual Studio Debugger on March 2nd)
[...] this issue is likely not in Visual Studio since it also occurs in scenarios where Visual Studio is not present. We are in the process of handing over our investigation to the Windows Servicing team.
But for now, removing the KB978037 update and it's related files seems to work.
This is a bug introduced in security update KB978037. Back out this update and you'll be back to normal.
Also see here:
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca
Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
There are a couple of things that could be happening here. Try closing down the following process and see which one, if any close down the Console application as well.
The Hosting Process: Typically named YourExecutable.vshost.exe
Visual Studio
If closing the hosting process fixes the issue then one quick work around is to disable the hosting process itself.
Right Click on Project -> Properties -> Debug -> Uncheck the hosting process
If closing down Visual Studio fixes the problem then it's potentially a bug in Visual Studio. Please file a bug on connect.
http://connect.microsoft.com
Visual Studio Debugger Team has already acknowledge this issues on their blog. check the below url for more information.
http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx