It took 6 hours. I lost an entire workday. This is just nuts.
I suspect your issue with installation is due to a versioning problem. Unfortunately I can't share the discussion, but you might (if you have to do this again) have a better time if you first install NI Certificates version 21.0 before DAQmx (or install an older DAQmx version, but probably you'd prefer not to do that).
In general, the popup should only appear once (if you check the box), and the fact that it appeared repeatedly for you might be an indication the installed certification was older than the drivers you were installing.
Replying to your comment, I understand your position but you have to understand that not everyone thinks like you. I find LabVIEW a terrible programming environment, ...
I also thought LabVIEW was a strange-looking misfit when I first came across it (lab setting, a previous PostDoc bought a bunch of NI hardware, then I needed to program it... coming from C++, it seemed very unusual/unnecessarily screen-occupying).
After a couple of weeks, I changed my mind. Now I like it for basically all the non-web programming that I do, including in some cases data processing. Certainly for acquisition, storage and metadata additions.
Matlab (and other text based programming languages) are far superior in searchability, community size, availability of library functions for big data processing, and debugging. I'd go as far as saying that LabVIEW is not even a real programming language.
I personally don't care if I can make GUIs with lab view. I don't think any of my colleagues cares either. I just want to make my one-off experiment acquire some automated data and process it. I know how to code quite proficiently... [in MATLAB]. I'll process the data in Matlab anyways so why not use it for everything?
Fair enough. I tried using GUIDE once for MATLAB, that was a painful experience, and many of my colleagues functions involving UI clicks on graphs etc in MATLAB also cause grief, and make things harder to automate, but if you truly don't need a GUI, then ease of GUI development is indeed irrelevant.
Re why not use it for everything? - Because you want to use the NI hardware, would seem to be the reason, so you're choosing to also use the NI drivers (sensible, but not inherently required - you could reverse engineer the entire thing and write your own drivers if you had nothing better to do for the next few ... [appropriate timespan here, I'd expect years maybe, but perhaps that's optimistic, depending on the range of hardware you wanted to support]).
Why not process the data in LabVIEW? What operations are you carrying out? (For that matter, what types of data are you acquiring?)
My colleague and I do a sizeable chunk of processing with MATLAB, mostly by saving (to NI's TDMS files, although you could pick another format) from LabVIEW and then loading the file in MATLAB for the generation of other results.
You could also save from LabVIEW directly to .mat file, if you're willing to jump through a few dozen hoops.
The simplest solution would be something like CSV, but your data volume/rates might be prohibitive of non-binary storage formats.
From a later reply:
Coding is easier in text-based languages. Coding is, in this day and age, a survival skill; and text-based code is superior, hands down. You can be colorblind (like me) and not have to struggle to discern whether that solid green line in your VI is a double data type or whatever else. If you don't remember what a function does, you can google its name and always find precise information about its arguments and what it does. If you see somebody else's code and there's a function you don't know, it is trivial to find it online and find out what it does. Good luck doing that with the little box elements in Labview. Not even a google image search will do the job (I've tried). None of the experiments in my career ever needed a front panel. I just need to acquire some data and automate some motor/solenoid/light/switch/whatever. What you're proposing is a botched workaround at best.
Labview is an outdated language. There's no discussion about it. It was a good effort, but we moved on. NI is the only company that refuses to realize and, to some extent, you've become a cult. I am just expressing what others won't bother to or don't know any better. So far in my career, I've done experiments far more impressive than what could ever be possible in Labview by using Matlab. I get praise from my peers because I can do so much with my experiments in so little time while they're struggling to build a string with a lego-like system designed for 5-year-olds. If you want to do any non-trivial data analysis Matlab is THE industry standard. If you want your experiment to do such analysis as it runs itself, computing different information on-the-go to make decisions along the way of what cases to explore next, it is insurmountable to build with a graphical language. Graphical languages are a gimmick and they have to go. If NI didn't make the exceptional hardware it did, it would already be out of business.