Fatal Error when installing LabView 8.5

I encounter a fatal error when I attempt to install LabView 8.5. The error that occurs has the following in its details:
".\UberInstaller.cpp(1871): IInstallerError 10014
Fatal Error. A failure has occurred in NISystemInfo.
CoLoadLibrary failed on C:\lv8.5\bin\NISysInf.dll"
I am installing from a system that previously had LabView 8.2 installed, however everything was uninstalled before I began installing the new version.
No hardware is connected in my computer.
I copied the files from the DVD to my harddrive and am still failing to install it from there.
The disc should be fine as my supervisor had used the same disc to install on his computer. ( our licence allows this )
Any help would be appreciated.
Attatched is a screenshot of the error.
Attachments:
error5.JPG ‏165 KB

IInstallerError 10014 
I searched for and found the same error in this forum that I am experiencing. I am trying to install the NI Switch Executive and the install fails every time. This is a fresh install and I am not running any antivirus s/w. It is a DVD copy of the Switch Executive s/w. Has there been any conclusive explanation as to what is happening with this? I have included a .jpg of the error. Thanks in advance for any help.
Attachments:
Error_Message.jpg ‏96 KB

Similar Messages

  • Update Operation Fatal Error when installing Technical Preview Build 10041 Upgrade

    I posted this in the Microsoft Community forums and was redirected here.
    Below is the original post (URL: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/update-operation-fatal-error-when-installing/6eaff1b9-0223-4357-afc8-884382590e82 )
    Hello,
    In trying to perform an upgrade install of the Windows 10 Technical Preview Build 10041 (as is the latest available for direct download as of my writing), I am running into a problem I cannot find mention of anywhere else on the web.
    I fall into two categories with regards to this build: A) Product tester who actually needs to test application performance under Windows 10 on bare metal, B) Semi-crazy techie who loves using (usable) beta software as his primary environment ;)
    so it is rather important to me that I get this working on my machine in some non-virtualized respect. I am reluctant to do a full/fresh install if installation problems are happening, because my Windows 8 product key has been f***ed up from the
    start (likely some random database corruption) and I've had to utilize phone support to get around an "unknown error" the last two times I've had to use it. So, for fear of that key completely crapping out on me, I don't want to move to Win10 unless
    I'm confident it will install and I can stick with it (for better or worse) through the end. Problems within the Preview after I install it I can deal with.
    So, I first tried to install the Preview through the standard Windows Update method. The installer took about 7 hours (but from reading lots of internet discussions, stupidly long install times in that range seem to be a common problem with
    this builds separate from it actually failing). During the reboot between the "Setting up Devices" (Or is it Setting up Drivers? I forget) and "Taking Care of a Few More Things" (Again, possibly paraphrased), for about a split second, underneath
    the Windows logo and throbber, some error like this appeared:
    Fatal Error Performing Update Operation # of ##: ERROR CODE
    It only appeared for a fraction of a second, and I had no chance of reading the precise numbers or error.
    However, the installer then seemed to continue, and went until the main circle was at 100%. As soon as 100% hit, however, the screen went black for something like 30min. Then, I briefly saw "Attempting to recover installation" before "Restoring
    your previous version of Windows." And I was, quite impressively considering how far along that installer was, back in Windows 8.1 completely unharmed.
    I tried again by burning an ISO and doing a disc upgrade install. I let that one run overnight and was asleep for the error, but I was back in Win8.1 in the morning, so I can only assume a similar thing happened there.
    As for my system specs, I'm running on a MacBook Pro 9,1 under Boot Camp. I am upgrading from Windows 8.1.2 Pro with Media Center. I have found other online accounts of people quite successfully installing Windows 10 on Macs, so that isn't the issue.
    Does anyone have any clue as to what this error might have been/be, and how I might fix it? Or at least have it on good authority that a fresh installation would be unaffected (meaning it's software-related)? If not, I can try installing to a VHD,
    which would at least let me product test on bare metal, but wouldn't have the harddrive space to be my daily driver and would probably only get used occasionally.
    Thanks in advance to anyone who can help!
    So far, I have the yet-to-be-tried idea of a clean boot prior to installation.
    If anyone here has any more specific ideas, lemme hear 'em.
    Thanks!

    To the individual who proposed this as an answer to my problem: It's not even applicable. I specifically stated that I was trying to avoid doing a clean installation (at least without knowing more about the problem at hand). An answer saying to do the thing
    you're trying to avoid doing is not an answer. You can see my last reply for the current status of this issue. 6-8 hour blocks of time in which I can't use my computer (as is required to install build 10041) aren't super common for me, but I haven't abandoned
    this thread. There have simply been no more updates. If your motivation as a mod was that you simply don't like there being unanswered threads on this forum, then perhaps you could attempt to contribute rather than arbitrarily marking the first reply as an
    answer.
    I will continue to update this thread as I try new things and get more information.
    Thank you.

  • Fatal error when installing icloud on windows 7 PC

    Get fatal error when trying to install icloud on Windows7 PC.

    Does this happen in a new user profile.. and what version of windows 64 or 32 bit ?

  • Known Issue: Fatal error when installing the Windows emulators: 2147023293 (Windows 10 Insider Preview SDK and tools, April 2015 release)

    When installing the Windows 10 emulators, you may receive the following error:
    Error: Emulators for Windows Mobile 10.0.10069 : The installer failed. Fatal error during installation. Error code: -2147023293

    To resolve this issue, run Visual Studio setup again to add the emulators. To do this
    Reboot your computer
    Open Control Panel, and select Programs and Features. 
    Select Microsoft Visual Studio 2015 RC, click Change, and then click
    Modify.
    Select the feature “Emulators for Windows 10 Mobile”, and click Update.

  • Developer Error when Installing Labview 8.5

    Hi there,
    When I was installing Labview 8.5 directly from the CD, I had error message 1311. Following the recommendation posted on the discussion forum, I copied the CD to the C drive and installed Labview 8.5 successfully. However, when I tried to follow the same procedure when installing the device driver CDs,i.e. by first installing the CD to a folder in the C drive and installing it by launching setup.exe, I had the following error:
    "Developer error. The following errors were found in your ini file: 1 Specified file not found. [MSIEngine] WinNTPath = SupportFiles\WindowsInstaller-KB893803-v2-x86.exe       Correct the ini file and try again"
    When I checked the setup.ini file, under the [MSIEngine] entery, I found the following text:
    "[MsiEngine]
    WinNTPath=bin\WindowsInstaller-KB893803-v2-x86.exe
    RequiredVersion=3.0.0.0
    CommandLine=/passive /norestart"
    How can I correct the ini file? Should I change the WinNTPath to the one generated by the error message? Will this solve the problem? Your help would be very much appreciated.
    Regards.

    Hi Muks
    I have attached the niPie.exe from the Vision Development Module 8.5 installation CD. If you can still not install the software try downloading it from the link below. Let me know if this helps.
    Vision Development Module:
    http://joule.ni.com/nidu/cds/view/p/id/839/lang/en
    Thank You
    Eric Reid
    Applications Engineer
    Thank You
    Eric Reid
    National Instruments
    Motion R&D
    Attachments:
    niPie.zip ‏23 KB

  • Memory Error when installing labview 6.1

    I had labview 6.0, 6.1 and RT installed on my PC (windows 2000). I tried to install application builder but I got Error that I have no labview installed, so I tired to uninstall RT, but I was abe to. Then I found out that I can't install or uninstall any of the Labview versions. So I went and deleted the whole NI directory, all the keys related to NI in the registry file, and Labview.ini. Now I'm trying to install labview 6.1, but I'm getting memory error and setup terminates. What can I do!
    Attachments:
    LB_Setup_Error.gif ‏36 KB

    First, I recommend contacting NI support at ni.com/ask and starting an incident report.
    Second, I recommend either restoring your registry from backup, or wiping your system and starting over. I know it doesn't sound like fun, and it isn't, but it is probably the only way now you can guarantee a good clean registry. Alternatively, go through the registry again and make sure all National Instruments and LabVIEW entries are deleted.
    In the future, and I make this recommendation to everyone, you should, as a safe practice, make a backup of your registry before you install anything, and also periodically. Archive these and label them with the list of programs installed, or with any new programs that have been installed.
    The Windows registry is obsolete,
    and complete hopeless when it comes to a stable system. There is no automated backup of the registry to my knowledge. The registry is the biggest source of problems with Windows, followed of course by DLLs (everyone has their own version, and noone's is alike, much less works right.) The registry can be backed up by using "Export" from the regedit program. Backups can be restored with the "Import" function in regedit of course.
    Good luck.

  • Fatal error when installing Acrobat Pro subscription

    I have a subscription for Adobe Acrobat Pro and have never been able to install it.  When I try to install it, I get a Fatal Error message.  I've tried restarting the computer and re-downloading it.

    The message I get is as follows:
    Error Encountered
    Fatal error during installation.
    I am using Windows 7 Home Premium.
    This error occurs as the product is downloading, when the download is nearly complete.
    Thanks!

  • Fatal error when installing on "existing" m/w home

    Hi,
    I am trying to install Jdeveloper 11.1.1.5.0 using an existing middleware home (WLS 10.3.5). But it results into a fatal error. Precisely, the question is why jdeveloper installer tries to install WLS again even if I clearly instruct to "use existing middleware home"?
    As a workaround, I installed it with "create a new middleware home" instruction and it worked, but still the question remains that why it attempts to install WLS if it is already existing and instructed to use the existing one.

    Not sure if I read it in the release notes (check yourself) but the WLS which comes with jdev is wired up for adf usage already. And the WLS should not use for any other task then development.
    The installation of jdev always should go into a new home.
    Timo

  • Developer error when installing Labview 2010

    Dear Administrator,
    I uninstalled my old version of Labview 7.1 with Windows "Programs and Features", and try to install Labview 2010. However, error occurs. 
    It says:
    " Developer Error. The following errors were found in your ini file:
    1. Specified file not found: [Utilities] UpgradeManagerPostProcessro = bin\nipie.exe
    2. Specified file not found: [Utilities] NISysinfo = C:\Users\...\NI.LabVIEW.2010.v10.0\bin\NISysInf.dll
    Correct the ini file and try again."
    My system is WIN 7 English version.
    Help please.

    Hello,
    The first step I reccomend you try is to re-download the LabVIEW installer, and try to run it again.  Also, make sure you have Administrator access on your computer.
    You can download LabVIEW here.
    Regards,
    Matt M.
    Applications Engineer
    National Instruments

  • Fatal error when installing Bootcamp

    I am having trouble with installing bootcamp.
    I have installed windows xp 32bit, and about midway the installation of the bootcamp drivers/applet, I get a windows fatal error:
    STOP: c000021a {Fatal System Error}
    The Windows SubSystem process terminated unexpectedly with a status of 0xc0000005 (0x7c9101b3 0x0052f29c).
    The system has been shut down.
    Beinning dump of physical memory
    physical memory dump complete.
    Contact your system administrator or technical support group for further assistance.
    Anyone have any ideas why this is happening and how to fix it?
    Thanks,
    Gil
    P.S.
    Seems like the error comes right after it tried to install the sigmatel drivers...
    Message was edited by: giladal
    Message was edited by: giladal

    I am having the same exact problem. The bootcamp install crashes at the same point as yours, and the "try it three times" does not work for me.
    I had bootcamp installed on my 27" iMac i7; however, I could not install Microsoft Office 2007 or Wordperfect without removing bootcamp. Now I cannot get it to install again.
    Manually updating the drivers using the disk works fine, except I still cannot get my printer to work because of this. It claims there is no USB hardware/drivers, even though all my other USB peripherals work just fine!
    If anyone has a fix, please let me know.

  • Fatal error when installing master collection "[FATAL] Setup - Error installing C:\Users\Desktop\MasterCollection_CS6_LS6\packages\core\PDApp.pimx package. Return Value of pim_installPackage = -1

    Hi,
    When I try to install a trial product like photoshop cs6 or master collection cs6 I keep getting the error " Installer failed to initialized". I used Adobe cleaner to remove all cs6 products and tried again, but no luck, the same error.
    I opened  the  the log file and found that line :
    [FATAL] Setup - Error installing C:\Users\moshe-a\Desktop\MasterCollection_CS6_LS6\packages\core\PDApp.pimx package.
    Return Value of pim_installPackage = -1
    Any idea how to fix the problem?
    Thank you, Momu

    start at the top and work your way down applying applicable fixes until your problem is resolved.
    if cc (win):  https://helpx.adobe.com/creative-cloud/kb/creative-cloud-desktop-application-failed.html
    if, your error is:
    "Installer failed to initialize. File not found." or "Installer failed to initialize. This could be due to missing files."
    first, rename OOBE Folder to OOBE.old.
    to find OOBE:
    64 bit win OS: Program Files x86\Common Files\Adobe\OOBE
    32 bit win OS: Program Files \Common Files\Adobe\OOBE
    mac os: HD>library>application support>adobe>caps
    mac os: USER>library>application support>adobe>OOB
    if that fails or isn't the exact error you see, uninstall, clean (http://www.adobe.com/support/contact/cscleanertool.html) and reinstall.
    if you're using a dvd to install:
    copy the disc contents to a desktop directory and install from that directory.
    if you're using a mac:
    1. Try to Create a new user account in Mac with Administrator Priviledges.
    2. Login to the New user, Navigate to Mac HD> Application> Utilities> Adobe Installer folder, Locate products like Adobe Reader, Adobe Flash, Adobe Air and un-install them
    3. Navigate to User Library> Application Support> Adobe and move Adobe to Trash.
    4. Navigate to Mac HD> Library> Application Support> Adobe and move Adobe to Trash.
    5. Start the installation again.
    if everything applicable above fails, check your installation logs:
    http://helpx.adobe.com/photoshop-elements/kb/troubleshoot-install-using-logs-elements.html

  • Fatal error when trying to install AIR app on OSX

    A user of my application is getting a fatal error when trying to install on OSX. Most installs seem to go fine so I was surprised at this one.
    A portion of the OSX error report is below. Has anybody experienced anything similar? If so, were you able to identify the core problem?
    Thanks in advance for any thoughts!
    Daniel
    Date/Time:       2013-06-13 15:50:24.666 -0700
    OS Version:      Mac OS X 10.8.3 (12D78)
    Report Version:  10
    Interval Since Last Report:          1414734 sec
    Crashes Since Last Report:           30
    Per-App Crashes Since Last Report:   5
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
    VM Regions Near 0x8:
    --> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/SimpleDiagrams2.app/Contents/MacOS/SimpleDiagrams2
        __TEXT                 0000000000001000-0000000000007000 [   24K] r-x/rwx SM=COW  /Applications/SimpleDiagrams2.app/Contents/MacOS/SimpleDiagrams2
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.adobe.AIR                      0x02b43f72 0x2800000 + 3424114
    1   com.adobe.AIR                      0x02909628 0x2800000 + 1087016
    2   com.adobe.AIR                      0x02909853 0x2800000 + 1087571
    3   com.apple.AppKit                   0x95544970 -[NSApplication(NSAppleEventHandling) _handleAEReopen:] + 255
    4   com.apple.AppKit                   0x952ec824 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 378
    5   libobjc.A.dylib                    0x9a3c9628 -[NSObject performSelector:withObject:withObject:] + 77
    6   com.apple.Foundation               0x94e4473a __76-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_0 + 121
    7   com.apple.Foundation               0x94e44291 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 430
    8   com.apple.Foundation               0x94e4408e _NSAppleEventManagerGenericHandler + 173
    9   com.apple.AE                       0x97aeda35 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 331
    10  com.apple.AE                       0x97ac2fbe dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44
    11  com.apple.AE                       0x97ac2e7d aeProcessAppleEvent + 318
    12  com.apple.HIToolbox                0x9222fc58 AEProcessAppleEvent + 100
    13  com.apple.AppKit                   0x952e8d4d _DPSNextEvent + 1655
    14  com.apple.AppKit                   0x952e81dc -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
    15  com.apple.AppKit                   0x952de63c -[NSApplication run] + 855
    16  com.adobe.AIR                      0x0280a772 0x2800000 + 42866
    17  com.adobe.AIR                      0x0280aab8 0x2800000 + 43704
    18  libobjc.A.dylib                    0x9a3c95d3 -[NSObject performSelector:withObject:] + 70
    19  com.simplediagrams2                0x00002f97 start + 2567
    20  com.simplediagrams2                0x000025c5 start + 53
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib             0x9263d9ae kevent + 10
    1   libdispatch.dylib                  0x97b75c71 _dispatch_mgr_invoke + 993
    2   libdispatch.dylib                  0x97b757a9 _dispatch_mgr_thread + 53
    Thread 2:
    0   libsystem_kernel.dylib             0x9263c8e2 __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x996fb280 _pthread_cond_wait + 833
    2   libsystem_c.dylib                  0x99781095 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.AIR                      0x02d1b113 0x2800000 + 5353747
    4   com.adobe.AIR                      0x02b4d5dc 0x2800000 + 3462620
    5   com.adobe.AIR                      0x02d1b22d 0x2800000 + 5354029
    6   com.adobe.AIR                      0x02d1b2a7 0x2800000 + 5354151
    7   com.adobe.AIR                      0x02d1b342 0x2800000 + 5354306
    8   libsystem_c.dylib                  0x996f65b7 _pthread_start + 344
    9   libsystem_c.dylib                  0x996e0d4e thread_start + 34
    Thread 3:
    0   libsystem_kernel.dylib             0x9263c8e2 __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x996fb280 _pthread_cond_wait + 833
    2   libsystem_c.dylib                  0x99781095 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.AIR                      0x02d1b113 0x2800000 + 5353747
    4   com.adobe.AIR                      0x02b4d5dc 0x2800000 + 3462620
    5   com.adobe.AIR                      0x02d1b22d 0x2800000 + 5354029
    6   com.adobe.AIR                      0x02d1b2a7 0x2800000 + 5354151
    7   com.adobe.AIR                      0x02d1b342 0x2800000 + 5354306
    8   libsystem_c.dylib                  0x996f65b7 _pthread_start + 344
    9   libsystem_c.dylib                  0x996e0d4e thread_start + 34
    Thread 4:
    0   libsystem_kernel.dylib             0x9263c8e2 __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x996fb280 _pthread_cond_wait + 833
    2   libsystem_c.dylib                  0x99781095 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.AIR                      0x02d1b113 0x2800000 + 5353747
    4   com.adobe.AIR                      0x02b4d5dc 0x2800000 + 3462620
    5   com.adobe.AIR                      0x02d1b22d 0x2800000 + 5354029
    6   com.adobe.AIR                      0x02d1b2a7 0x2800000 + 5354151
    7   com.adobe.AIR                      0x02d1b342 0x2800000 + 5354306
    8   libsystem_c.dylib                  0x996f65b7 _pthread_start + 344
    9   libsystem_c.dylib                  0x996e0d4e thread_start + 34
    Thread 5:
    0   libsystem_kernel.dylib             0x9263c8e2 __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x996fb280 _pthread_cond_wait + 833
    2   libsystem_c.dylib                  0x99781095 pthread_cond_wait$UNIX2003 + 71
    3   com.adobe.AIR                      0x02d1b113 0x2800000 + 5353747
    4   com.adobe.AIR                      0x02b4d5dc 0x2800000 + 3462620
    5   com.adobe.AIR                      0x02d1b22d 0x2800000 + 5354029
    6   com.adobe.AIR                      0x02d1b2a7 0x2800000 + 5354151
    7   com.adobe.AIR                      0x02d1b342 0x2800000 + 5354306
    8   libsystem_c.dylib                  0x996f65b7 _pthread_start + 344
    9   libsystem_c.dylib                  0x996e0d4e thread_start + 34
    Thread 6:
    0   libsystem_kernel.dylib             0x9263c8e2 __psynch_cvwait + 10
    1   libsystem_c.dylib                  0x996fb280 _pthread_cond_wait + 833
    2   libsystem_c.dylib                  0x997810e0 pthread_cond_timedwait$UNIX2003 + 70
    3   com.adobe.AIR                      0x02d1b13f 0x2800000 + 5353791
    4   com.adobe.AIR                      0x02d60c0e 0x2800000 + 5639182
    5   com.adobe.AIR                      0x02d1b22d 0x2800000 + 5354029
    6   com.adobe.AIR                      0x02d1b2a7 0x2800000 + 5354151
    7   com.adobe.AIR                      0x02d1b342 0x2800000 + 5354306
    8   libsystem_c.dylib                  0x996f65b7 _pthread_start + 344
    9   libsystem_c.dylib                  0x996e0d4e thread_start + 34
    Thread 7:
    0   libsystem_kernel.dylib             0x9263d0ee __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x996f90ac _pthread_workq_return + 45
    2   libsystem_c.dylib                  0x996f8e79 _pthread_wqthread + 448
    3   libsystem_c.dylib                  0x996e0d2a start_wqthread + 30
    Thread 8:
    0   libsystem_kernel.dylib             0x9263d0ee __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x996f90ac _pthread_workq_return + 45
    2   libsystem_c.dylib                  0x996f8e79 _pthread_wqthread + 448
    3   libsystem_c.dylib                  0x996e0d2a start_wqthread + 30
    Thread 0 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x02b43f55  ecx: 0x95b40466  edx: 0x00000000
      edi: 0x00000000  esi: 0xbfffef18  ebp: 0xbfffee58  esp: 0xbfffeda0
       ss: 0x00000023  efl: 0x00210282  eip: 0x02b43f72   cs: 0x0000001b
       ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
      cr2: 0x00000008
    Logical CPU: 1

    Hi Daniel,
    Could you post or send me ([email protected]) the entire crash log?  I'll at least need the binaries section so I can properly symbolicate the log.
    Thanks,
    Chris

  • Fatal Error while installing

    I recently purchased a second itouch for my daughter and when I plugged it in to my computer it required that I download 9.2. I already had an existing version of itunes on my PC. While installing it stated "There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor". Then it continues to download Quicktime. The itunes icon appears on my desktop but when I click it I receive the "Fatal Error while Installing message". I have uninstalled/reinstalled, created a new user account on my PC, updated my Windows service pack. Nothing seems to solve this problem, now I can't even sync the other ipods I have. Any idea how to fix this so I can get itunes back to working?

    I followed the instructions in the exact order as they appeared. I get the following error:
    "There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor."
    When I click "OK" it continues to install Quicktime and that completes properly. Then it tells me itunes has been successfully installed. The itunes icon appears on my desktop, but when I click it, it goes through what appears to be a windows configuration setup, but then gives me the same message I was getting before: "Problem with shortcut: Fatal error during installation". Someone had suggested on another post to use Firefox instead of IE to download itunes, but that hasn't worked for me either.
    This is so frustrating, we have three itouch ipods in this house and we cant sync or add music to any of them since this occurred. I really appreciate your assistance.

  • Run time error while installing Labview 8.6.1 in Vista x64

    hai friends,
               i got an error( Run time error) while installing Labview 8.6 software. this software has bought from NI. it shows the error path as setup.exe. this software i had tried to install in vista x64. but when i am installing the same software in windows xp, it is installing fine...so what was the problem for this error. how to solve it, please help me....

    Thank You Mr.Jason Daming,
    Same error what post Mr.muks referred in the last reply....
    When the installation begins an error occurs (after the acceptance of licence step in the installation procedure) with the title on the error window "Microsoft Visual C ++ Runtime Library " and displays the program set up path with these statements " This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
    while installing the same Labview in windows XP..... it is installing fine... but in vistax64 only i am facing this kind of problem...

  • Fatal error when I open Itunes and Quick time.

    EventType : BEX P1 : QuickTimePlayer.exe P2 : 7.4.5.67 P3 : 47edaedf
    P4 : QuickTimePlayer.exe P5 : 7.4.5.67 P6 : 47edaedf P7 : 0000130d
    P8 : c0000409 P9 : 00000000
    cant uninstall quick time gives fatal error, stems from same error when I try to open Itunes.

    Checking on a possible cause of similar symptoms. Have you ever install an ACE or K-Lite Mega Codec pack, a copy of QT Alternative or QT Lite, or a copy of Storm Codec on that PC?
    (Checking on this because those programs, and some others, can install "QuickTime" componentry on the PC that can break a copy of the QuickTime on the PC, and as a consequence break iTunes. The "fatal error" when attempting to uninstall QuickTime is often a symptom of that, too.)

Maybe you are looking for