MS Visual C++ Runtime Library crashes when I run LabVIEW as Non-administrator (User Group Only) Windows 7 Account

[FWRay-wjbroc]

Using Windows 7 and LabVIEW 2009. Customer has requested that our test software runs from a Windows User Group Account (Non-Administrator).  First issue that came up is we use the LabVIEW Instrument Pallets, IVI Library for DMM, RF Power Meter...etc. When I execute some simple code that creates a session with the IVI DMM (Initialize, Reset, then close), this code crashes during the initialize operations (off pallet) when it calls down to the Ivi.dll found in the c:\Windows\System32 folder. 

The message is MS Visual C++ Runtime Library pop up with X that says "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information". Click OK to close and then LabVIEW 2009 closes.

I've tried setting file control privileges for all locations but not the entire C:\Windows\System 32 folder....

I've proven that I can simply change the windows login account to administrator and the LabVIEW snippet runs. 

Anyone else experienced this problem?

[Bob_Schor]

According to NI, the first version of LabVIEW that is compatible with Windows 7 is LabVIEW 2009 Service Pack 1.  Most people do not install the Service Packs, so I'm guessing you are running LabVIEW 2009f0, which may be missing some hooks in IVI or other things.

You should suggest to your Customer that he really should consider using a more recent version of LabVIEW, one that is compatible with more modern, more supported Windows Versions such as Windows 10.  The "least modern" version of LabVIEW that NI certifies for Windows 10 is LabVIEW 2015 SP1.  My recommendation would be to get the current release, LabVIEW 2018.  A lot of improvements and new features have been added to LabVIEW in the succeeding 9 years ...

Bob Schor

[rolfk]

The real solution to this is possibly mentioned in this Knowledgebase article. Although it mentions Windows 10 but Windows 7 may be affected too.

Certain language settings (most likely for locals using a decimal comma instead of a decimal point) will mess up the Microsoft C runtime initialization.