Runtime error r6034 microsoft visual c++ runtime library explorer.exe

Question

Hi!

I encountered a problem with my Windows 7 SP1 Professional x64 computer. Problem started two weeks ago after I installed the monthly Windows updates. After the updates every time I restart or login to my computer I get the error message saying "Runtime error r6034 microsoft visual c++ runtime library C:\windows\explorer.exe".  After I hit "ok" in the error screen I can use Windows normally.  I also get the same message when I try to use Explorer in different programs, for example notepad. Only difference is that now the path in the error refers to notepad. And again, I can still pick a file to be opened after I press ok in the error screen.

Problem occurs also in Safe mode and clean boot didn't help either. I also tried system restore to a previous configuration with similar results. I re-installed Visual C++ Library 2010, but it didn't help. I tried to install every single Visual library version (both x86 and x64 ) from 2005 to 2012 without success. Event log shows no errors so no help from there.

Can you give me any advice, what to try next?

Answer 1

Here's a simple solution which worked for me:  I right-clicked on the offending program, selected "Properties," clicked on the "Compatibility" tab, in the "Privilege Level" section, I checked the box for "Run this program as an administrator", then clicked the "Apply" button.  Presto.  Problem solved.  I have no idea why this worked, and I don't want to hurt my brain trying to figure that out.

Answer 2

I found the guilty for the problem, which was my backup software. I informed the software developer about this and they said that the problem will be repaired in the next patch.

Answer 3

I encountered the same error. I tried to run the program as an administrator but the same error persists. What mothod else can I try?

Answer 4

OK, I fixed the problem myself. the program that causes the R6034 error tried to load the VC++ run time library msvcr90.dll. The thing is, there is an entry "C:\Windows\CCM" in the PATH so the dll in this path is loaded. The dll in this path, however, is the culprit because it is problematic; its size is different from the one in the C:\Windows\winsxs folder. So I removed the CCM entry from my PATH variable and, boom, there is no R6034 error any more. PS: I found the problem using a tool called Process Explorer.

Answer 5

Fact: This is a pretty generic problem, many things can cause it, so there is really no point on reverse engineering for every single case.

I had it with Ableton Live 9, when I tried to load the Nexus PlugIn... 

What I did was as follows: 

NOTE: Of course I did not know and I didn't even try to find the technical reason which caused this problem, I was just trying to make a software run, not to investigate anything at all, but here is what I did and it worked perfectly, now everything is running normally.

1. Set the program which caused the problem to run as administrator (In this case the host program "Ableton Live", because it wasn't Ableton who caused the issue but a couple of files from the Nexus plugin) Just go to the icon on which you click when you wish to launch the program, right click on it and go to properties... then to "compatibility" tab and check the box at the bottom, that says "Run this program as an administrator", then just in case press the "Change settings for all users" button just below and check the same box in there, then press on Apply and OK... That should make the program to run as administrator from now on.

2. Run the program: It should tell you which file is failing to load or causing some issue every time a file causes one and each time it should offer you to either continue or to cancel (In order to stop trying to load that problematic file) That's exactly what you must choose: CANCEL so it won't try to load it again... Then perhaps it also offers you to try to find a solution online and then to send the information to Microsoft or to Whomever else, for them to know and try to solve the issue. Say yes to that, why not, right? After all these guys are working. Anyway...

3. Every time you do the step 2, most likely the program won't run correctly but will stop with the same or with a new error message (It's always better to read in any case) but just go on running it, which means: every time you run it, since you are running it as administrator, it will try to load correctly and, every time you CANCEL the loading of a faulty file, it won't load it again the next time, so it's like a step by step correction, which in the end will avoid loading all that which causes problems until it finally runs the software correctly.

ODDS:

A: PROBLEM SOLVED (The faulty files are very few and unimportant, so in a couple of attempts the soft will run and will do it correctly, leaving only a few possibilities for future failure, already whilst the software is running.  Anyway problem solved.

B: The faulty files are to many or too important, so the problem won't be solved or the solution won't be satisfactory enough.

In any case, trying these simple steps won't take you more than a few minutes and you may get things working very well as it happened to me.

Go on, try this out. Patience is the key to  solve all software problems.