Don't worry about those, those aren't real errors. The ADE queries the license status of all possible toolkits, which might or might not be installed. Some of the internal functions used report some of those statuses as errors, but from the point of view of the calling code, they're not really errors.
So, those profiler crashes were never resolved? Did you report them here in the forum, or to tech support?
Here's more info about this .uir problem on VB shares.
I also had a similar problem with another Windows executable and noticed it behaved properly on normal network shares. So I just tried to open that .uir from a network share and it worked. So it's a VirtualBox bug, or at least it's a VB limitation which is not handled properly by CVI.