33 | | For whatever it's worth, attempts to import a new VM yielded three separate Administrative elevation prompts, all of which I approved, yet it made no difference. Furthermore, I tried elevating the Powershell console to Administrator-level access before booting the VM with Vagrant, which made the prompts disappear (because they are of course unnecessary given Powershell's the elevated access), but the error condition did not change. |
| 33 | For whatever it's worth, attempts to import a new VM yielded three separate Administrative elevation prompts, all of which I approved, so this wasn't a case of VirtualBox having insufficient permission to do whatever it was trying to do. Furthermore, I tried elevating the Powershell console to Administrator-level access before booting the VM with Vagrant, which made the prompts disappear (because they are of course unnecessary given Powershell's the elevated access), but the error condition did not change. |
| 34 | |
| 35 | Also, running the 5.2.6 installer's "Repair" option, which did require a restart (and I obliged), had no bearing on the observed behavior. |