crash in visual studio


I have a  crash in visual studio that I am able to capture via devenv.exe to a logfile. What does the error seem to indicate and how can i fix it?

Please see the logfile below.

    <time>2015/06/27 20:41:29.619</time>
    <source>Microsoft Visual Studio</source>
    <description>Loading UI library</description>
    <path>C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\*\msenvui.dll</path>
    <time>2015/06/27 20:41:29.643</time>
    <source>Microsoft Visual Studio</source>
    <description>Error checking App Path</description>
    <hr>80070005 - E_ACCESSDENIED</hr>
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jacques Bourgeois (James Burger)PresidentCommented:
E_ACCESSDENIED indicates that the system is trying to access a directory that is not accessible for the current user, probably one of the sub directories under C:\Program Files (x86)\Microsoft Visual Studio 9.0.

You might try running Visual Studio as an administrator.

Or check the security configuration of the directories and files under C:\Program Files (x86)\Microsoft Visual Studio 9.0, since from the first part of the log, it seems to be where the thing is looking.

Unfortunately, I do not have VS9 anymore, and newer versions do not use this dll, so I cannot tell you exactly in which directory it is located.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Never saw your problem, so I can only make a WAG about this. My guess is that you do not have access to the file:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\*\msenvui.dll

Try running VS as administrator to see if the E_ACCESSDENIED error goes away.
Looks like after I added zones, and then tried to research your problem, Jacques Bourgeois (James Burger) came to help.
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

AndyAinscowFreelance programmer / ConsultantCommented:
>>C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\*\msenvui.dll

Just another point.  A '*' in a path is not a valid symbol - have you entered this path somewhere yourself.
LuckyLucksAuthor Commented:
I have not entered the * in the path myself. But while i was scouring the web, i looked over other people's crash logs and they seemed to have a * in their paths as well, sometimes to dll other than msenvui.dll

So i suspect that the addition of a * might be a microsoft thing.
LuckyLucksAuthor Commented:
Also, on my actual filesystem , I found the msenvui.dll in
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\1033

Also, in

C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\1033  (visual studio 2013)
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\1033  (visual studio 2012)

and so on.
So this msenvui.dll seems to be used in other visual studio versions ?
Jacques Bourgeois (James Burger)PresidentCommented:
You are right. It also does in 2015.

When I go to look directly in the directory, there it is. But for some reason it does not appear on a search on my C drive, which prompted my first comment.

This being said, did you solve your problem?
AndyAinscowFreelance programmer / ConsultantCommented:
When searching for the crash logs - did you find any solutions to the problem?
AndyAinscowFreelance programmer / ConsultantCommented:
Also consider running the 'repair' option of the Visual Studio installation.  

ps.  I assume other projects/solutions compile & build without problem.
LuckyLucksAuthor Commented:
It seems running as administrator gets rid of the error. But I am surprised that it take Admin powers to get rid of the error in the first place. Generally, people would be running VS as regular users, not admins.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.