Unable to install Extension Pack 4.1.14-77440

[parky128]

Hi,

I have just updated my Virtual Box to the latest 4.1.14 build and am trying to update the Extention Pack.

Currently I have an old version of the pack installed, 4.1.6. If I try to remove this using the GUI by selecting the installed pack and clicking the remove button, I end up with this error message:

Code: Select all

Failed to uninstall the Extension Pack Oracle VM VirtualBox Extension Pack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the extension pack directory: VERR_ALREADY_EXISTS

rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

If I just try and intall the 4.1.14 pack by manally downloading the file and double clicking it to install I end up with this error message:

Code: Select all

Failed to install the Extension Pack C:/Users/Rob/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.1.14-77440.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the extension pack directory: VERR_ALREADY_EXISTS

rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

I have also tried installing the pack through the GUI by clicking the add button and selecting the downloaded file, but I get the same error above.

So it seems I am stuck, what can I do further? Am I best off completely uninstalling and re-installing Virtual Box?

I am running on a Windows 7 64 bit system in case this is important.

Thanks

[Perryg]

Make sure that VirtualBox & all guests are shut down and then use the Windows Command window to remove the current Extension Pack

See the bottom of Window in the following post.
How to install Extension Pack

Note: Windows users need to be in the directory that has VBoxManage for the command to work.

[kevinrutan]

I deleted everything in C:\Program Files\Oracle\VirtualBox\ExtensionPacks\ then re-ran the installer with no VMs running. That fixed it for me.