A regular install is best because sometimes there are things other than code (palettes, etc.) that are either needed or at least helpful.
However, a short-term thing that might help you get by is to copy the respective .llb files from the LV2012 installation folder hierarchy into the corresponding folder in the LV2018 hierarchy. The Agilent instrument code is being found under the instr.lib folder while the other missing item is somewhere under user.lib
No guarantees, but I've found that such moves often work. (Note: the first time you close any of these vi's from your 2018 project, you'll be prompted to save. Do it, though I'd probably first check to make *sure* the save location is under the LV 2018 hierarchy rather than 2012. It very likely will be but it doesn't hurt to make sure.)
-Kevin P
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
