I'm running Visual Studio 2017, version 15.0.0+26228.9
When I'm trying to create a new project via File > New > Project... in Visual Studio 2017, I'm receiving the following error message and the project is not created:
Access denied (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Don't mind the german message text in the screenshot:
This happens for every project template I use (e.g. C# WPF, VB WPF, C# Console App...).
If I try to create a project via the quick search box on the starting page of visual studio, VS just crashes instantly with no exception message at all:
Has anybody else ran into this issue and might know how to fix it?
I had the same error.
I solved it by following the procedure :
Shutdown all instances of Visual Studio
Delete %LocalAppData%\Microsoft\VisualStudio\15.0_f4938f75\privateregistry.bin file (the ID after 15.0_ may be different per machines)
Start VS as normal user
all credit for this should go to https://developercommunity.visualstudio.com/content/problem/31188/access-denied-error-1.html
Ok, I fixed it.
Long story short, the reason for the problem was an incomplete and/or corrupted setup.
But it was a rather bumpy road to the solution, including several un-installations and re-installations until I eventually figured out why the setup was indeed faulty.
Sometimes I got an exception during the installation, other times it finished just fine, but the HRESULT-error persisted when I tried to create a new project.
I my special case, this was caused by the corporate firewall, that blocked some of the setup packets from being downloaded by the web installer. I solved the issue by connecting to an open WiFi, that's not filtered by the firewall.
As I'm working with a standard user, UAC kicks in when I start any installation routine. When I first started the setup via UAC and connected to the free WiFi, it wasn't able to find the packet servers.
It took me a minute to realize that the admin user I used for UAC had his own internet proxy settings, that wouldn't work with the open WiFi.
After I logged on as administrator, disabled the proxy and logged on as my main user again, I ran the setup again - and it failed again with a bunch of "incomplete workload" messages. As frustrated as I was at this point, I simply ran it again via the "Change" button without even closing the webinstaller and this time it finally completed without any errors!
After this, I could start VS just normally and creation of a new project was possible.
So, if you experiencing any troubles like this, I would strongly recommend to run a "Repair" or "Change" installation just over your existing one but try to avoid any firewalls between you and the internet.
1/ open control panel -> program and future - > IIS Express -> select Repair
2/ Refresh some time -> open Visual Studio
This 's about IIS Express in your computer . you only need to repair it in control panel is ok .
I tried and success.
My solution,
The Clang-format caused this. just disable clang-format:
Options->Text Editor->C/C++->Formatting->General->Eable ClangFormat Support
I had the same error when I tried to create a test certificate.
I have just launched VS as administrator.
And everything is Ok
The below solution worked for me
Make sure all the instances of Visual studio are closed.
Go to %LocalAppData%\Microsoft\VisualStudio\15.0_****
Delete the file privateregistry.bin
I tried changing the version of .Net Framework from 4.0 to 3.5 while creating the project. This solved my error.
enter image description here
Changing version of Net Framework
Started getting a new error when starting a debugging session in VS2015. It's an ASP.NET MCV project that also exposes a WCF service (don't know if that's relevant).
The debugging session takes ages to start up and then I get a message box saying:
Specified argument was out of the range of valid values.
Parameter name: Type ISession cannot be resolved. Interfaces of
abstract classes should be registered first.
After that the debugger works as expected.
If I do the same thing from VS 2013 then it takes a long time to load but I get a message saying:
Loading symbols for WebActivatorEx.dll from:
d:\Code\GitHub\WebActivator\WebActivator\obj\Debug
This is strange because I haven't knowingly installed WebActivator and my D: drive is a DVD that I haven't opened since I got the PC.
Yesterday I installed OpenCover, but it didn't work so I removed it.
Anyone out there who might have an idea of what's going on???
Thanks
I had the same problem in my local workstation while my colleague was able to debug and run his web application fine. The said error message was thrown from visual studio 2015, but application used to launch fine and run. This was happening only in debug mode (either with "Start debugging" - F5 or debug mode of the project). The other side effect was that this problem was not occurring for the very first time after every system restart.
This thread along with the link How do you clear your Visual Studio cache on Windows Vista? and the link https://blogs.msdn.microsoft.com/willy-peter_schaub/2010/09/15/if-you-have-problems-with-tfs-or-visual-studio-flush-the-user-cache-or-not/ pointed me in right direction.
I was finally able to resolve the issue by clearing the contents from the following three directories on my local workstation:
a) <System drive>:\Users\<user id>\AppData\Local\Microsoft\Team Foundation
b) <System drive>:\Users\<user id>\AppData\Local\Microsoft\VisualStudio
c) <System drive>:\Users\<user id>\AppData\Local\Microsoft\VSCommon
The resolution makes me think on the lines of the accepted response provided with the first link above. There Visual Studio and Team Explorer cache might have gone out of sync. Hope this answer helps people facing similar issues.
When I debugging in VS2013 update3, msvsmon.exe crashed when hit at a breakpoint.
It shows "The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted".
I'm not using remote debug.
Is it possible to shut down the msvsmon.exe to avoid calling it when debugging ?
Deleting all of the breakpoints solves the problem when I hit this error. Disabling the breakpoints was not enough - they had to be deleted.
I was able to attach to a process numerous times. Once I added a conditional breakpoint (with a few checks), I started getting this error when attempting to attach to that same process.
The error provided in the question is one problem. I also received an error stating that a debugger was already attached when I tried again. Either way, deleting breakpoints solved it.
Try turning on Options > Debugging > General > "Use Managed Compatibility Mode"
I got this error/crash too while debugging and trying to inspect a variable with 50 MB of text data in it. This option worked in both VS2013 and in VS2015 to allow me to debug and inspect the variable with large data.
A couple of things that worked for me:
Try Closing VStudio and relaunching.
If not, reboot helps.[I know thats generic, but its worth a shot]
Disable unnecessary break points.
I had this error also, and I too have Astrill installed. Completely uninstalling Astrill fixed the issue.
I reached out to Astrill support, and they answered (within 2 hours) saying the correct fix is to hold Ctrl and press the "Help" button on the Astrill application, and then choose "Uninstall LSP". This has fixed the issue without needing to un-install Astrill.
I don't know what LSP is, but I presume it's some sort of proxy.
In my case, it was caused by a VPN software. It changed my hosts file and my localhost was not 127.0.0.1 anymore.
So check your localhost in the hosts file (e. g. %WINDIR%\System32\drivers\etc\hosts) and make sure it is 127.0.0.1.
This error just occurred for me with visual studio 2015 RTM. Deleting all the breakpoints resolved the "The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted" condition.
So If you clear all your breakpoints, in your version, you will not need to avoid using MSVSMON.exe.
I was using the OzCode debugger extension. Unfortunately they don't have a way to completely disable the extension - you can only disable certain features - so I had to completely uninstall it to confirm it was what was contributing to the crashes.
I got the same error. No effect after deleting all breakpoints and repairing Visual Studio (I have 2013 Community Edition). The problem was the Bitdefender software. I have Bitdefender Internet Security 2016 and had set Active Thread Control (Modules->Antivirus) to Normal level. But after setting this settings to Permissive the error doesn't show up anymore.
This error occured to me, when I tried to debug with Visual Studio / Service Pack 3, when Service Pack 4 was already released. After updating to the Service Pack 4 I was able to debug.
So, try installing the newest version of Visual Studio
Regards
This (or something that manifests in exactly the same way) is still an issue in VS2017. In my case it was caused by a dependency being too large to debug. The dependency in question was a generated client for a large REST API. I was able to debug again after slimming down that dependency.
Here's yet another answer: I changed my project from "Platform Target: Any CPU" to "Platform Target: x86". Went from needing about 5 attempts to debug to working every single time.
I had previously tried every suggestion in this thread: I reinstalled, I killed all breakpoints, and looked for fishy software interactions.
I started getting this exact error today in my VS2019 project. Attempting to expand/inspect simple data structs in VS debugger would make it freeze for a minute and then I'd get that "The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted" message:
If I add msvsmon.exe process to windows defender exclusions list, then the problem disappears.
I hit this in Visual Studio 2019 (16.4.3) (C++) with a cause that I have not seen mentioned: I had accidentally added a Watch with incorrect syntax that was attempting to instantiate a singleton rather than returning the existing instance.
Repeatedly choosing right click > Clear All in the Watches view while debugging fixed the issue.
Fixed by changing Options->Projects and Solutions->Web Projects -> Use 64bit version of IIS......... to False.
In my case i am using the wcf Service on the wpf application and inputting parameters from here.The Wpf Application Execution on Facing this error "The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted".
That case i am hosing the Wcf service and run the wpf application exe
In this type of Execution on I didn't Facing any Error like -- "The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted"
please,try this proceed error solved because some execution process didn't supporting the debugging..... we are removing the Debuggers on also we face same error.
that case on helped this process.......
I just experience this with VC2017 Community Edition 15.7.2. Turning off the Microsoft Symbol Server lookup while debugging fixed it for me.
I've just had the problem in VS 2015. I hadn't noticed that one of my breakpoints was bogus - I had inadvertently pressed F9 to set a breakpoint when the disassembly window was showing in the previous debugging session. The solution was simply to delete that one bogus breakpoint - I got to keep all my others.
I tried almost every answer in here, but for my case, nothing worked.
Switching to 32-bit just made Visual Studio 2019 crash instead of msvsmon.exe crashing.
What did work for me is to set a very early breakpoint and use that opportunity to close the "Parallel Stacks" window. I didn't need that anyway, but it was open by default in my layout.
In my case, I had this error when I had the "Locals" tab opened during debugging and hitting a breakpoint. For some reason VS might've been unable to display one of the local variables. The error disappeared when switched to a different tab before hitting the breakpoint where the error was occurring.
My problems started after moving a project to a new folder. I wasn't having any luck with any of these answers using VS2019. I even deleted the entire .vs folder thinking maybe something got corrupted. No luck.
But on a whim I tried starting the project with CTRL-F5 instead of just F5 and that actually worked. It's consistent. CTRL-F5 runs fine. F5 gives me the msvsmon.exe error.
I have no idea what's going on, but at least I can get the project to run again.
This problem is at least 1 1/2 years old maybe more. Today is 6-11-22 and I have the problem in Ms Studio Pro 2022 with a fresh install of windows 11 not much of anything else in the computer. Then I uninstalled it and install Ms Studio Community 2022 put in 1 breakpoint at the beginning and I got the error.
Today 6-12-22 I reinstall Ms Studio Community 2022. For some reason I switch from x86 to x64 went through a about 1000 changes of errors and a crashed form1.resx file thank goodness for a backup I had or I'd be done again. anyways so far have several break points with no problems.
I deleted all my watch variables. That fixed the problem for me.
I know it doesn't directly address the error, but as a workaround, I'm using the Rider IDE from JetBrains, and am not encountering the error (code, system, etc. the same).
Visual Studio version: Professional 2017, 15.5.4
Rider version: 2017.3
None of the other answers worked for me, when I encountered this error. If you are not actually remotely debugging, you can use another editor until you figure out the problem or it resolves itself (the latter was the case for me).
I have encountered an error while debugging a VB.Net application in Visual Studio 2008. While debugging the console application in Visual Studio, when the application instantiates a Crystal Reports 'ReportDocument' object, VS2008 hangs. Even when the devenv.exe process has been killed, I am unable to kill the still running vshost.exe process for the console application. The console application is a port from a legacy VB6 application, and I suspect that a underlying COM call may be responsible for VS2008 hanging.
Can anyone offer any advice on how to identify the cause of this problem? If you can offer an exact answer for this specific problem, fine, but I am more interested in the process of debugging this issue further, specifically around identifying any COM interactions, I do not have any experience in this field.
Thanks, MagicAndi.
Note
I am using the Crystal Reports 2008 Redistribution installer
I had a problem a couple of weeks ago with visual studio crashing at a certain point. I opened a second instance of VS with break on all errors switched on then attached to process of first instance of VS and hit the problem again. The exception was caught and this gave me an idea as to what was wrong.
It may not work in this instance but it is worth a try.
When trying to execute from within Visual Studio 2008 your application and you get the (uninformative) message "The operation could not be completed".
The solution to this is to turn off the "Visual Studio Hosting Process".
The problem with turning off this "hosting process" is that all the "run and rewrite" functionality is no longer available. OK, so this isn't a big deal, but I'm always getting this message no matter what machine I use (and it might be nice once in a while to use the rewrite and execute functionality).
Am I doing something wrong? How come this "feature" within VS seems to complain so readily? Do other people have success with enabling the hosting process and making use of it?
The problem with turning off this "hosting process" is that all the "run and rewrite" functionality is no longer available.
The Visual Studio Hosting Process is not needed to allow Edit and Continue. It is used for "Design time expression Evalutation" in the case where the project is a dll rather than an EXE. It is also used to provide debugging for partial trust scenarios. See the documentation for everything it does.
It is highly unlikely it does anything you need, so don't feel bad turning it off.
Is your project output folder set to a network share?
If so, try changing it to a local folder and see what happens. It appears that VS is not always able to terminate the process if the host exe is running from a share.
The other possibility is that the project is open and running in debug mode on another instance of Visual Studio - although I suspect you will allready have ensured this is not the case.
I honestly have never seen this message and I work with Visual Studio for at least 8 hours a day. Is this reproducible on other machines? If so is there anything weird or abnormal in your code that could cause this to crash?
I use 4 different machines and have got this situation on all of them. I understand what is causing the problem - it is that the VS hosting process isn't terminating after the first debug session ends, which means that the next time that you try to compile the exe the hosting process is locking the exe and preventing compilation. Another solution therefore is to use Task Manager to kill the VS hosting process and compile and debug as normal but thats even more of a hassle!
I can't think that its anything in my code that would be causing this - its probably a VS issue itself isn't it?
Here's the anwser: disable "Enable he Visual Studio hosting process" in he debug tab of your projects properties.
I found it here:
http://social.msdn.microsoft.com/Forums/en-US/vbide/thread/40d2d241-a0c0-4137-9da9-e40611972c0e/
There are several causes and workarounds regarding to this problem and you might try the following ones that are useful most of the time:
Delete the "Your_Solution_FileName.suo" file and restart Visual Studio.
or
Right click on the project and select Unload Project and then click Reload Project by right clicking on the project again might also fix it.