Cvirte.dll Not Found

[Abbie Pilz]

WhenI try to install my new version of our panel on machines that have the older panels, the installation seems to install fine using the build package wizard. However, when we run the application it fails with a

Additionally there doesn't seem to be an uninstall either. The program cannot be uninstalled from "Programs and Features". We have two workarounds. 1) Make sure we uninstall the old version of our panels before installing or 2)If you have already installed the new version and have the error, install NILWCVIRTE2010. You cannot reinstall the panel application because the installer looks at the build and believes it is already installed.

There are a few ideas that I have but it looks like for some reason when you build the installer, it uses an older version of the CVI Runtime Engine. I just want to make sure we tried the basics, such as going deleting the current build and going to Build>> Distributions>> Build name of project and then trying to install that. After you do that you, can check the version of the install that is used by going to the Control Panel and moving to Programs and Features, then selecting to remove/change NI software. This will bring up a menu of all the NI software on the computer. Let me know which version of the LabWindows/CVI Runtime Engine is installed to the computer. The one we need is 2010. I also found a KnowledgeBase that has some information that maybe useful: Here

I am not sure what you mean be deleting the current build. Do you mean simply uninstalling the current build on my pc using Control Panel>Programs and Features, do I delete the build file from the project directory, or do I delete the build configuration in the labwindows/CVI application by selecting Build>Distributions>Manage Distributions.

You can also verify the installed drivers on your machine by looking at the Control Panel's add remove software and modifying the install of National Instruments Software or if you have Measurement and Automation explorer you can see the list under the software tab.

I'm sorry you're still having this issue. I saw the screenshot of what you have installed on your development computer. Could you show us the same screenshot on the computer you are deploying your installer to? We need to see whether or not Run Time engine is installed on that one. If it is already installed then there is something deeper going on, if not then we can install it and see if that fixes the problem.

Luckily we had a build protocol that I had neglected to read prior to performing a build. I had missed several steps in the build process. The build configuration file was ok. I needed to perform the following steps prior to building:

Then I ran the build distribution. After a few successful tests, I concluded that one of these steps was the culprit. I am not sure which, but I suspect the "Ensure Run-time support" or "Application Title" are to blame.

I have a vb.net desktop app which makes call to a dll developed in LabWindows/CVI. I have version 9.0 cvi runtime engine installed. The CVI dll is actually developed by another company I am working on this project with. The crashing is not consistent but it most often ends up with an error "faulting module cvirte.dll" The problem is that it will run fine sometimes for a couple of hours making the same function calls then error.

What I do not understand is why it will make the same calls for a long period of time then all of sudden crash. Since it is so inconstent it's hard to explain this to the CVI developer since with his CVI only app it works.

The CVI Runtime Engine is backwards compatible so version 9.0 should work with DLL's built in an older version. However, it might still be helpful to know the exact version AND build of the runtime engine that you are using.

Also, there should be some useful information in the Windows Event Viewer that will help us determine what is going on. Right-click on My Computer, and select Manage. In the Computer Management window, expand Computer ManagementSystem ToolsEvent Viewer. If you are on Windows XP, select Application. If you are on Window Vista/7, select Windows LogsApplication. There should be an error listed here that corresponds to your application. If you cause the app to crash immediately before looking at the log, then your app should be the most recent error.

You already sent us the faulting module name and the offset, but any additional information, more specifically, exactly what your application is doing when it crashes would be helpful. If you could send all the details from that log, that will help us in resolving this issue.

I've added a zip file with two attachments which were files created from the crash. I've been attempting to duplicate this issue but have found it very inconsistent. I do not have access to the code of the cvi assembly so I'm not sure what function calls the module would be making especially since this crash is diffult to reproduce.

I took a look at the crash dump you posted, but was not able to make a lot of it because the dump you attached was a minidump (this is the default type of dump that's created). If you could follow the steps here to create a full WER dump, I'd appreciate it. The full dump may be too big to post to the forum - if that's the case, just upload it to and I'll take a look.

I have our netbook with xp on it that this program will run on. I setup Dr. Watson but it did not generate the dumps. There are a couple of microsoft support articles that reference this issue and there appears to be a hotfix so I am going to try to get that worked out.

Thanks for all your efforts. Based on your latest crash dump, we've implemented what we hope will be a fix. However, we would like you to test the fix for us if that would be possible. You can find an updated version of cvirte.dll at

Please rename your current version of cvirte.dll int c:\windows\system32 (or syswow64) and put this new version in it's place. Once you are confident the fix did or did not work, or you are unable to perform this test, could you please let us know?

I ran a test last night and your fix appears to have worked. Previously, my program would hang after x amount of time (sometimes a short time, sometimes 4 hours). Last night I allowed my program to run for 12 hours straight without hanging. I will be testing more over the next few days and will let you know if there are any issues.

I developed an application on my desktop with LabWindows CVI 9.0. It runs perfectly on my desktop. Then took that application to the target system to run it. Unfortunately, it won't load. An error pops up concerning "cvirte.dll". The dll is present on the target system, however, I'm wondering if it's not an older version. Here's the error:

You will need to run the installer for the run time engine on the target machine. The LabWindows/CVI Run-Time Engine must be installed on any Windowssystem where you plan to run executables or DLLs built usingLabWindows/CVI. Maybe you can get IT to install the run time for you. You will also need any drivers that you are relying on to be installed.

DLL problems with cvirte.dll most often stem from a corrupt or missing file associated with NI-DAQ Software. A large percentage of these file issues can be resolved with downloading and installing the latest version of your DLL file. Additionally, some cvirte.dll errors can be due to incorrect registry references, so we recommend conducting a registry scan to clean up any invalid entries.

Getting the cvirte.dll file location correct is critical in making sure these errors are resolved successfully, so it doesn't hurt to check to make sure. You can then re-open NI-DAQ Software to see if the error message is still triggered.

Usually cvirte.dll errors with NI-DAQ Software happen during startup or shutdown, while cvirte.dll related applications are running, or rarely during the OS update sequence. Notating when cvirte.dll errors occur is paramount in finding the cause of the NI-DAQ Software problems and reporting them to National Instruments for help.

Improper computer shutdowns or malware-infected cvirte.dll files can cause issues with NI-DAQ Software, leading to corrupt errors. After corruption, cvirte.dll cannot load, prompting NI-DAQ Software problems on running.

In other cases, registry problems with cvirte.dll can be the source of the NI-DAQ Software problem. Damaged cvirte.dll file path references to NI-DAQ Software prevent proper file loading, creating cvirte.dll errors. Moving a cvirte.dll, missing cvirte.dll files, or bad/leftover file reference from improper NI-DAQ Software install/uninstalls cause these to break.

Hello, I wrote a LabVIEW program to communicate with a hardware sensor using vendor-provided LLB and a DLL files. The program runs fine on my workstation both from LabVIEW IDE and from a compiled executable. The problem starts when I copy the entire executable folder to a target host without a LabVIEW IDE (only with a runtime engine). The application opens with a broken Run arrow and a "missing external function" error message appears for every function call I made to the DLL (see attached).

I have tested my application on 5 completely different Windows 10 computers managed by different people. On three of them with various versions of LabVIEW IDE my executable opened with a whole Run arrow and no error message. Two other machines previously had no LabVIEW, so I installed a Runtime Engine 2017f2 32-bit with default settings to match the version of my IDE. Both gave an identical error message.

The DLL is always included in the application build. I have tried placing the DLL in every conceivable location on the target host: in the executable folder, in the /data folder, in the c:\Windows and system32 folders... I even created a full folder tree matching the location of the project on the developer workstation. Same error. When I intentionally hide the DLL, my executable prompts me to point to it upon being opened, and when I do, I get all the same error messages.

3a8082e126