Hi aa82,
Which user were you logged-in as when running the command (or were you running the command from a LabVIEW application)?
On the original post, there is also .zip file that can be placed on the host machine to install the fix via MAX, if you aren't as comfortable with the commandline interface.
Finally, the issue has been resolved in later releases of the base image, so if you install a later version of cRIO support (the December 2017 or later installer), the issue is resolved.
