Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix R6034

Runtime Error R6034: An Application Made an Invalid Attempt to Load the CRT

11 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

The C runtime stopped the process rather than run in a state it does not trust. Microsoft’s current runtime error list documents R6002, R6025 and R6030 but no longer publishes anything for R6034, so treat that one by what you can observe: which copy of the runtime the application is loading, and where it came from.

Run these from a Command Prompt while the application is closed

where msvcr90.dll
where msvcr100.dll
where msvcp100.dll
tasklist /m msvcr*
  1. Look in the application’s own folder for files named msvcr*.dll, msvcp*.dll or mfc*.dll. A copy sitting beside the executable that the vendor’s installer did not put there is the usual suspect.
  2. Rename any such file to add a .bak extension rather than deleting it, then start the application again.
  3. If the folder is clean, read the where output. A hit in a folder belonging to unrelated software – a printer utility, a database client, an old development tool – is the next thing to move off the search path.
  4. Install the Visual C++ redistributable the application was built against, in the matching architecture, and restart the machine.

Rename rather than delete. Some vendors ship a deliberately modified runtime and the application will not start without it, in which case the vendor’s own updater is the right route.

If the application starts and stays up, you are done. If the code is R6025, R6030 or R6002, the next section explains why those are different problems with different owners.

Why it happens

The generation of Microsoft C runtimes that shipped before the universal CRT were deployed as side-by-side assemblies. Rather than a file in a system folder, they live in the component store and an application asks for one by declaring a dependency in its manifest. The loader then binds the correct version. That design existed to end the era of applications overwriting each other’s runtime files.

R6034 belongs to that world. Microsoft’s current list of C runtime errors runs from R6002 to R6035 and does not include it, and no Microsoft documentation page carries its message text, so anything you read about the precise mechanism – including here – is not something the vendor publishes today. What is observable is straightforward enough: the message appears when an application is using a copy of an old runtime that did not come through the normal resolution, and it stops appearing when that copy is out of the way.

The neighbours are documented, and they are not variations on the same theme. R6025 is published as “pure virtual function call”, which is a defect in the application’s own code. R6030 is “CRT not initialized”, which means code ran before the runtime had finished starting – typically from a DLL doing too much work in its entry point. R6002 is “floating-point support not loaded”. None of the three is fixed by moving a DLL around.

One practical consequence is worth stating plainly. Applications built against the universal CRT introduced with the 2015 generation do not use the side-by-side mechanism this error belongs to. Seeing R6034 at all tells you an older component is still in the chain, and in a modern estate that is more often a plug-in or an add-in than the main program.

A loose runtime DLL sits beside the executable

You have this one if The application folder contains a file such as msvcr90.dll that the vendor’s installer did not create – often left by a plug-in or an update tool.

  1. Close the application completely, including any tray component.
  2. Rename the file by appending .bak so you can restore it if you were wrong.
  3. Start the application. If it now runs, install the matching Visual C++ redistributable so a properly registered copy serves it.
  4. If it does not run, restore the renamed file before moving on.

A third-party folder on PATH is exporting a runtime

You have this one if The application folder is clean, but where msvcr90.dll returns a hit in a folder belonging to unrelated software.

  1. Run where for each runtime name and record every path returned.
  2. Open the system environment editor and inspect PATH, both the system and the user variable.
  3. Remove the offending directory if nothing depends on it, or move it below the system entries so it is searched later.
  4. Sign out and back in, then retest. PATH is read at process start, so a shell that is already open keeps the old value.

The correct redistributable was never installed

You have this one if No stray copies exist anywhere, and the application is a vendor build that has always failed on this machine.

  1. Check the vendor’s system requirements for the runtime generation the application needs.
  2. Install that redistributable in the same architecture as the application.
  3. Install both architectures if the application loads 32-bit plug-ins into a 64-bit host or the reverse.
  4. Reboot and retest.

R6025, a pure virtual function call

You have this one if The code is R6025 rather than R6034, and it appears at a repeatable point such as closing a document or exiting the program.

  1. Update the application to the newest build the vendor offers. This is a coding defect and only the vendor can fix it.
  2. Note the exact sequence that triggers it and send that to their support channel.
  3. Check whether a plug-in is involved by starting the application with add-ins disabled if it offers that option.

Do not attempt to patch the runtime to suppress it. Replacing runtime files to hide a crash produces a machine nobody can support.

R6030 or R6002, with several applications affected

You have this one if The code is one of those two and more than one unrelated application is failing.

  1. Repair every Visual C++ redistributable entry from Settings, Apps, Installed apps, Modify, Repair.
  2. Run sfc /scannow from an elevated Command Prompt.
  3. Follow with DISM /Online /Cleanup-Image /RestoreHealth if sfc reports files it could not repair.
  4. Reboot and retest.

Full reference

What Microsoft publishes, and what it does not

Code Published message Whose problem
R6002 floating-point support not loaded The application’s build
R6025 pure virtual function call A defect in the application’s own code
R6030 CRT not initialized Code running before the runtime finished starting, usually from a DLL entry point
R6031 Attempt to initialize the CRT more than once. This indicates a bug in your application. The application
R6033 Attempt to use MSIL code from this assembly during native code initialization The application
R6034 Not published by Microsoft in its current runtime error list Diagnose by observation

The absence of R6034 from Microsoft’s current list is a fact worth carrying into any conversation about it. A great deal is written about this error, and none of it traces back to a page the vendor maintains. That does not make the error unreal – it makes the diagnosis empirical, which is why the steps here are about finding and moving copies of files rather than reasoning from a published mechanism.

Diagnostic commands

Command What it does
where msvcr90.dll Lists every copy of that runtime on the search path in resolution order
tasklist /m msvcr* Shows which running processes have a runtime of that family loaded
sxstrace trace -logfile:C:\temp\sxs.etl Records side-by-side resolution while you reproduce the failure; stop it at the prompt, not with Ctrl+C
sfc /scannow Verifies protected system files, including system-installed runtime components

tasklist /m is the underused one. Run it while the application is up, or while a related process is, and it shows which module is actually loaded rather than which one you expect. On a machine with several copies on disk, that is the difference between a guess and an answer.

Working out which family an application needs

  • The vendor’s system requirements are the first source and usually the only one you need.
  • Failing that, the file names give it away: the runtime DLLs the application ships or asks for carry the generation in their names.
  • Microsoft’s current guidance is that Visual Studio 2017 and later share the same redistributable files, and that the installed Redistributable must be the same version as, or later than, the build tools used.
  • Older families are separate products. Installing the newest package does nothing for an application that needs one of them.
  • Architecture is separate again: X86, X64 and ARM64 are published separately, and the X64 package contains both ARM64 and X64 binaries.

When only one user is affected

PATH exists as both a system variable and a per-user one, and the per-user entries are appended to the system ones for that account only. A runtime copy in a folder listed only in one user’s PATH produces a failure that follows that person between applications and does not reproduce for anyone else. The system environment editor shows both lists; compare them before concluding the profile is corrupt.

Things not to do

  1. Do not copy a runtime DLL from another machine into the application folder. That is the arrangement that produces this error, not the cure for it.
  2. Do not delete runtime files from system folders. If one is genuinely wrong, repair or reinstall the redistributable that owns it.
  3. Do not disable the application’s own updater to stop it replacing a file. It is usually replacing it for a reason.
  4. Do not chase R6025 with runtime work. It is a null call to a pure virtual function inside the application and no environment change fixes it.
  5. Do not leave a .bak file in place indefinitely. Once the application works, decide whether the file should be there and remove it or restore it properly.

Every code this article covers

Code What it points at Source
R6034 Reported by the C runtime when it will not continue in the state it was loaded in. Microsoft’s current runtime error list does not include it, so it is described here by what can be observed rather than by a published meaning not published by the vendor
R6025 pure virtual function call – a defect in the application’s own code Microsoft Learn
R6030 CRT not initialized – code ran before the runtime had finished initialising Microsoft Learn
R6002 floating-point support not loaded Microsoft Learn

Confirm the fix worked

  1. Start the application and confirm it reaches its normal interface with no runtime dialog.
  2. Run where msvcr90.dll again and confirm the only results are in system directories.
  3. Run tasklist /m msvcr* while the application is running and confirm it has loaded the copy you intended.
  4. Exercise the action that previously triggered the error, such as opening a document or closing the program.
  5. Restart the machine and repeat the test once, so you know PATH and any service-launched instances are also clean.

Questions people ask about this

Is there anything to buy to fix R6034?

No. Every Visual C++ redistributable is a free download from Microsoft, and everything else here is a rename or a built-in repair command. A tool offering to sell you a runtime fix is selling you something you already have.

Does Microsoft document R6034?

Not in its current C runtime error list, which runs from R6002 to R6035 and omits it. Its neighbours R6002, R6025, R6030, R6031 and R6033 are all published. That is worth knowing because most of what is written about R6034 is not traceable to the vendor.

Can I just copy a working msvcr90.dll from another PC?

No. That is precisely the arrangement that produces this error. The runtime is meant to be installed by its own installer rather than placed as a loose file.

Why does the error only appear for one user on a shared machine?

PATH can be set per user as well as system-wide, and per-user application folders differ. Check the user PATH in the environment editor and look for runtime copies under that profile.

Do modern applications still hit R6034?

Rarely. Applications built against the universal CRT introduced with the 2015 generation do not use the side-by-side mechanism this error belongs to. Seeing it usually means an older component is still in the chain, often a plug-in rather than the main program.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix MSI 1402 and 1406: Could Not Open Key or Write Value During Installation Free Fix MSI 1638 and 0x80070666: A Newer Version of This Product Is Already Installed Free Fix MSI 1335: The Cabinet File Required for This Installation Is Corrupt Free Fix 0x800B0100: MSIX Package Is Unsigned or Its Certificate Is Not Trusted
โ† Back to Knowledge Base