Complete uninstall Virtualbox The Next CEO of Stack OverflowHow to uninstall Virtualbox on...

How do I solve this limit?

How to count occurrences of text in a file?

How do I go from 300 unfinished/half written blog posts, to published posts?

Is it okay to store user locations?

Rotate a column

What do "high sea" and "carry" mean in this sentence?

Can I equip Skullclamp on a creature I am sacrificing?

How to write papers efficiently when English isn't my first language?

Too much space between section and text in a twocolumn document

Describing a person. What needs to be mentioned?

Why were Madagascar and New Zealand discovered so late?

Can a single photon have an energy density?

Visit to the USA with ESTA approved before trip to Iran

Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?

Is a stroke of luck acceptable after a series of unfavorable events?

Is it my responsibility to learn a new technology in my own time my employer wants to implement?

Why does standard notation not preserve intervals (visually)

How to start emacs in "nothing" mode (`fundamental-mode`)

How to use tikz in fbox?

Error when running sfdx update to 7.1.3 then sfdx push errors

Unreliable Magic - Is it worth it?

Grabbing quick drinks

I believe this to be a fraud - hired, then asked to cash check and send cash as Bitcoin

What is meant by a M next to a roman numeral?

Complete uninstall Virtualbox

The Next CEO of Stack OverflowHow to uninstall Virtualbox on windows10?What is the right way to configure Ubuntu on VirtualBox?Can't access CentOS in VirtualBoxVirtualBox kernal error in Windows 10 trying to run VagrantSymantec Endpoint Protection Prevents VirtualBox Guest From StartingVirtualBox with inaccessible snapshotCannot uninstall SQL Server 2008 from Windows Server 2012 r2Clicking on “install CentOS” on VirtualBox causes black screen to appear?Virtualbox can't detect any network adapter after upgrade windows 10VirtualBox Host-Only adapters and bridged networkCentOS 7 Virtualbox VM SSH Connection Suddenly Refused

Few days ago my VirtualMachine Centos refused to launch. It says an "an unexpected shutdown happened before" so it refuses to start and gives error. Now, after unsuccessful, side by side searching internet for a solution, i decided to uninstall it completely and to install everything from scratch. But however i uninstall the the Virtualmachine and next, Virtualbox it is doesn't help. After i install it again it still keeps the old settings and still gives that error. So, i am very upset, and really need help. I also
followed Virtualbox uninstall documentation and no success because it just says to uninstall it ordinary way from Control Panel. I have also deleted all related folder also, but again no success. Plz help me. Thank in advance! (i can provide any info upon request)

asked May 23 '17 at 21:06

Cliff Cliffer

18113

you don't uninstall virtual machines, you either delete them, or mount a Centos install disk to the VM, and boot from it to reinstall the OS over the existing one. as for your virtualbox settings, they are likely in your user profile in your %appdata% directory, so check in `C:UsersyourusernamehereAppdataLocal.virtualbox`.

– Frank Thomas
May 23 '17 at 22:23

add a comment |

asked May 23 '17 at 21:06

Cliff Cliffer

18113

you don't uninstall virtual machines, you either delete them, or mount a Centos install disk to the VM, and boot from it to reinstall the OS over the existing one. as for your virtualbox settings, they are likely in your user profile in your %appdata% directory, so check in `C:UsersyourusernamehereAppdataLocal.virtualbox`.

– Frank Thomas
May 23 '17 at 22:23

add a comment |

asked May 23 '17 at 21:06

Cliff Cliffer

18113

virtualbox

asked May 23 '17 at 21:06

Cliff Cliffer

18113

asked May 23 '17 at 21:06

Cliff Cliffer

18113

asked May 23 '17 at 21:06

Cliff Cliffer

18113

asked May 23 '17 at 21:06

Cliff Cliffer

18113

asked May 23 '17 at 21:06

Cliff Cliffer

18113

you don't uninstall virtual machines, you either delete them, or mount a Centos install disk to the VM, and boot from it to reinstall the OS over the existing one. as for your virtualbox settings, they are likely in your user profile in your %appdata% directory, so check in `C:UsersyourusernamehereAppdataLocal.virtualbox`.

– Frank Thomas
May 23 '17 at 22:23

add a comment |

you don't uninstall virtual machines, you either delete them, or mount a Centos install disk to the VM, and boot from it to reinstall the OS over the existing one. as for your virtualbox settings, they are likely in your user profile in your %appdata% directory, so check in `C:UsersyourusernamehereAppdataLocal.virtualbox`.

– Frank Thomas
May 23 '17 at 22:23

you don't uninstall virtual machines, you either delete them, or mount a Centos install disk to the VM, and boot from it to reinstall the OS over the existing one. as for your virtualbox settings, they are likely in your user profile in your %appdata% directory, so check in `C:UsersyourusernamehereAppdataLocal.virtualbox`.

– Frank Thomas
May 23 '17 at 22:23

add a comment |

4 Answers
4

active

oldest

votes

After you uninstall Virtualbox from control Panel

You also have to delete the folder:

C:Users[Your User Name]AppdataLocal.virtualbox

You may have to enable Show hidden files and folders option for Appdata folder to be visible (see here for how to do this on Windows 7).

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

add a comment |

Disclaimer: this procedure is dangerous and can break your host system. Please backup your data or/and take a system image first. (That said, I've applied this procedure twice to my main Windows 7 machine, and the operating system is still running fine.)

My situation: I wanted to update from VirtualBox 5.1.22 to 5.1.28. The installer of newer version hanged near the end, so I needed to properly uninstall 5.1.22 first to get it work:

Download psexec.exe and CCleaner. Then unplug network cable, turn off wifi. Kill google drive, dropbox, and other system-invasive tools (and do this again if you restart during the procedure).

Uninstall using the VirtualBox uninstaller from Control Panel (for some reason I didn't have one on my machine).

Remove the folders C:/Program Files/Oracle/VirtualBox and %userprofile%.VirtualBox

Remove virtual box drivers (files starting with VBox..) from C:Windowssystem32drivers

Clean up windows registry: start regedit.exe as an administrator, search for VirtualBox everywhere and thoughtfully but carefully (don't break other stuff) delete the corresponding folders, keys and values.

At this point, I was blocked because I couldn't remove the children folders (which are VirtualBox network drivers) of Computer/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Enum/Root/NET/ folder. For me, the workaround consisted in

Download PsExec.exe to your desktop

Go Start and in "Start search" type in: cmd. Hold CTRL and SHIFT keys, press Enter. Command prompt window will open.

Copy and paste following command:
"%userprofile%desktoppsexec" -i -d -s c:windowsregedit.exe

Using such the empowered version of regedit, you need

Take the ownership of ../NET folder (right click, "Permissions...", Advanced, Owner tab, check on "Replace owner on subcontainers and objects")

Add Full Control to OWNER RIGHTS

Remove all the children folders of ../NET
Maybe you'll need to play around with the permission further, machine restarts might help.

Goal: ../NET should be clean of VirtualBox driver folders, and have the Full Control permissions for administrators and OWNER RIGHTS as well.

Then several passes of CCleaner followed by restarts, and finally you are clean. If everything was done correctly, you now will be able to successfully install the newest version of VirtualBox, if necessary.

Related question:
How to uninstall Virtualbox on windows10?

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

add a comment |

It seems you need the original VB installer that matches the version that you Trashed. The VB installer has an uninstaller that systematically vacuums up all the VB install items. Run that.

On my macOS, I tried to remove extra VB files using the following suggestion:

Open Terminal

Type cd /Users//Library

Type ls an see if VirtualBox directory is there (should be)

rm -rf VirtualBox

Hope it may help someway.

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

add a comment |

The only thing that worked for me was to extract the original installer to the path.

This is what I did:

Download the installer

Open Command Prompt

Change to dir containing the installer

Run the installer with the --extract parameter. eg: VirtualBox-5.1.22-115126-Win.exe --extract

Uninstall VirtualBox in the usual way (using "Add or Remove Programs" / "Apps & Features"), or you should be able to run the installer for your new version of VirtualBox.

answered 15 mins ago

David Gallagher

1313

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1212182%2fcomplete-uninstall-virtualbox%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

4 Answers
4

active

oldest

votes

4 Answers
4

active

oldest

votes

After you uninstall Virtualbox from control Panel

You also have to delete the folder:

C:Users[Your User Name]AppdataLocal.virtualbox

You may have to enable Show hidden files and folders option for Appdata folder to be visible (see here for how to do this on Windows 7).

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

add a comment |

After you uninstall Virtualbox from control Panel

You also have to delete the folder:

C:Users[Your User Name]AppdataLocal.virtualbox

You may have to enable Show hidden files and folders option for Appdata folder to be visible (see here for how to do this on Windows 7).

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

add a comment |

After you uninstall Virtualbox from control Panel

You also have to delete the folder:

C:Users[Your User Name]AppdataLocal.virtualbox

You may have to enable Show hidden files and folders option for Appdata folder to be visible (see here for how to do this on Windows 7).

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

After you uninstall Virtualbox from control Panel

You also have to delete the folder:

C:Users[Your User Name]AppdataLocal.virtualbox

You may have to enable Show hidden files and folders option for Appdata folder to be visible (see here for how to do this on Windows 7).

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

edited May 24 '17 at 4:32

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

answered May 24 '17 at 4:26

Ahmed Akhtar

1956

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

add a comment |

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

@CliffCliffer Welcome, glad that it did. It's my first answer on superuser.

– Ahmed Akhtar
May 25 '17 at 11:37

add a comment |

My situation: I wanted to update from VirtualBox 5.1.22 to 5.1.28. The installer of newer version hanged near the end, so I needed to properly uninstall 5.1.22 first to get it work:

Download psexec.exe and CCleaner. Then unplug network cable, turn off wifi. Kill google drive, dropbox, and other system-invasive tools (and do this again if you restart during the procedure).

Uninstall using the VirtualBox uninstaller from Control Panel (for some reason I didn't have one on my machine).

Remove the folders C:/Program Files/Oracle/VirtualBox and %userprofile%.VirtualBox

Remove virtual box drivers (files starting with VBox..) from C:Windowssystem32drivers

Clean up windows registry: start regedit.exe as an administrator, search for VirtualBox everywhere and thoughtfully but carefully (don't break other stuff) delete the corresponding folders, keys and values.

Download PsExec.exe to your desktop

Go Start and in "Start search" type in: cmd. Hold CTRL and SHIFT keys, press Enter. Command prompt window will open.

Copy and paste following command:
"%userprofile%desktoppsexec" -i -d -s c:windowsregedit.exe

Using such the empowered version of regedit, you need

Take the ownership of ../NET folder (right click, "Permissions...", Advanced, Owner tab, check on "Replace owner on subcontainers and objects")

Add Full Control to OWNER RIGHTS

Remove all the children folders of ../NET
Maybe you'll need to play around with the permission further, machine restarts might help.

Goal: ../NET should be clean of VirtualBox driver folders, and have the Full Control permissions for administrators and OWNER RIGHTS as well.

Related question:
How to uninstall Virtualbox on windows10?

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

add a comment |

My situation: I wanted to update from VirtualBox 5.1.22 to 5.1.28. The installer of newer version hanged near the end, so I needed to properly uninstall 5.1.22 first to get it work:

Download psexec.exe and CCleaner. Then unplug network cable, turn off wifi. Kill google drive, dropbox, and other system-invasive tools (and do this again if you restart during the procedure).

Uninstall using the VirtualBox uninstaller from Control Panel (for some reason I didn't have one on my machine).

Remove the folders C:/Program Files/Oracle/VirtualBox and %userprofile%.VirtualBox

Remove virtual box drivers (files starting with VBox..) from C:Windowssystem32drivers

Clean up windows registry: start regedit.exe as an administrator, search for VirtualBox everywhere and thoughtfully but carefully (don't break other stuff) delete the corresponding folders, keys and values.

Download PsExec.exe to your desktop

Go Start and in "Start search" type in: cmd. Hold CTRL and SHIFT keys, press Enter. Command prompt window will open.

Copy and paste following command:
"%userprofile%desktoppsexec" -i -d -s c:windowsregedit.exe

Using such the empowered version of regedit, you need

Take the ownership of ../NET folder (right click, "Permissions...", Advanced, Owner tab, check on "Replace owner on subcontainers and objects")

Add Full Control to OWNER RIGHTS

Remove all the children folders of ../NET
Maybe you'll need to play around with the permission further, machine restarts might help.

Goal: ../NET should be clean of VirtualBox driver folders, and have the Full Control permissions for administrators and OWNER RIGHTS as well.

Related question:
How to uninstall Virtualbox on windows10?

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

add a comment |

My situation: I wanted to update from VirtualBox 5.1.22 to 5.1.28. The installer of newer version hanged near the end, so I needed to properly uninstall 5.1.22 first to get it work:

Download psexec.exe and CCleaner. Then unplug network cable, turn off wifi. Kill google drive, dropbox, and other system-invasive tools (and do this again if you restart during the procedure).

Uninstall using the VirtualBox uninstaller from Control Panel (for some reason I didn't have one on my machine).

Remove the folders C:/Program Files/Oracle/VirtualBox and %userprofile%.VirtualBox

Remove virtual box drivers (files starting with VBox..) from C:Windowssystem32drivers

Clean up windows registry: start regedit.exe as an administrator, search for VirtualBox everywhere and thoughtfully but carefully (don't break other stuff) delete the corresponding folders, keys and values.

Download PsExec.exe to your desktop

Go Start and in "Start search" type in: cmd. Hold CTRL and SHIFT keys, press Enter. Command prompt window will open.

Copy and paste following command:
"%userprofile%desktoppsexec" -i -d -s c:windowsregedit.exe

Using such the empowered version of regedit, you need

Take the ownership of ../NET folder (right click, "Permissions...", Advanced, Owner tab, check on "Replace owner on subcontainers and objects")

Add Full Control to OWNER RIGHTS

Remove all the children folders of ../NET
Maybe you'll need to play around with the permission further, machine restarts might help.

Goal: ../NET should be clean of VirtualBox driver folders, and have the Full Control permissions for administrators and OWNER RIGHTS as well.

Related question:
How to uninstall Virtualbox on windows10?

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

My situation: I wanted to update from VirtualBox 5.1.22 to 5.1.28. The installer of newer version hanged near the end, so I needed to properly uninstall 5.1.22 first to get it work:

Download psexec.exe and CCleaner. Then unplug network cable, turn off wifi. Kill google drive, dropbox, and other system-invasive tools (and do this again if you restart during the procedure).

Uninstall using the VirtualBox uninstaller from Control Panel (for some reason I didn't have one on my machine).

Remove the folders C:/Program Files/Oracle/VirtualBox and %userprofile%.VirtualBox

Remove virtual box drivers (files starting with VBox..) from C:Windowssystem32drivers

Clean up windows registry: start regedit.exe as an administrator, search for VirtualBox everywhere and thoughtfully but carefully (don't break other stuff) delete the corresponding folders, keys and values.

Download PsExec.exe to your desktop

Go Start and in "Start search" type in: cmd. Hold CTRL and SHIFT keys, press Enter. Command prompt window will open.

Copy and paste following command:
"%userprofile%desktoppsexec" -i -d -s c:windowsregedit.exe

Using such the empowered version of regedit, you need

Take the ownership of ../NET folder (right click, "Permissions...", Advanced, Owner tab, check on "Replace owner on subcontainers and objects")

Add Full Control to OWNER RIGHTS

Remove all the children folders of ../NET
Maybe you'll need to play around with the permission further, machine restarts might help.

Goal: ../NET should be clean of VirtualBox driver folders, and have the Full Control permissions for administrators and OWNER RIGHTS as well.

Related question:
How to uninstall Virtualbox on windows10?

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

edited Sep 24 '18 at 11:55

answered Oct 12 '17 at 12:18

Hope

14914

answered Oct 12 '17 at 12:18

Hope

14914

answered Oct 12 '17 at 12:18

Hope

14914

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

add a comment |

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

Nice findings for all the places where it leaves its traces. However, this creates much more panic than needed ("this procedure is dangerous") ...as usually with system tweak guids - come on people its just an OS. Usually, user data is left untouched and can be recovered easily by hooking up the harddrive to another computer.

– masterxilo
Sep 24 '18 at 11:56

It depends on the recover tools you dispose. This disclaimer was suggested by Ramhound.

– Hope
Sep 27 '18 at 16:20

add a comment |

It seems you need the original VB installer that matches the version that you Trashed. The VB installer has an uninstaller that systematically vacuums up all the VB install items. Run that.

On my macOS, I tried to remove extra VB files using the following suggestion:

Open Terminal

Type cd /Users//Library

Type ls an see if VirtualBox directory is there (should be)

rm -rf VirtualBox

Hope it may help someway.

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

add a comment |

It seems you need the original VB installer that matches the version that you Trashed. The VB installer has an uninstaller that systematically vacuums up all the VB install items. Run that.

On my macOS, I tried to remove extra VB files using the following suggestion:

Open Terminal

Type cd /Users//Library

Type ls an see if VirtualBox directory is there (should be)

rm -rf VirtualBox

Hope it may help someway.

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

add a comment |

It seems you need the original VB installer that matches the version that you Trashed. The VB installer has an uninstaller that systematically vacuums up all the VB install items. Run that.

On my macOS, I tried to remove extra VB files using the following suggestion:

Open Terminal

Type cd /Users//Library

Type ls an see if VirtualBox directory is there (should be)

rm -rf VirtualBox

Hope it may help someway.

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

It seems you need the original VB installer that matches the version that you Trashed. The VB installer has an uninstaller that systematically vacuums up all the VB install items. Run that.

On my macOS, I tried to remove extra VB files using the following suggestion:

Open Terminal

Type cd /Users//Library

Type ls an see if VirtualBox directory is there (should be)

rm -rf VirtualBox

Hope it may help someway.

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

edited Sep 27 '18 at 6:54

Scott

16.1k113990

edited Sep 27 '18 at 6:54

Scott

16.1k113990

edited Sep 27 '18 at 6:54

Scott

16.1k113990

answered Sep 27 '18 at 6:21

AskFeeds

answered Sep 27 '18 at 6:21

AskFeeds

answered Sep 27 '18 at 6:21

AskFeeds

add a comment |

The only thing that worked for me was to extract the original installer to the path.

This is what I did:

Download the installer

Open Command Prompt

Change to dir containing the installer

Run the installer with the --extract parameter. eg: VirtualBox-5.1.22-115126-Win.exe --extract

Uninstall VirtualBox in the usual way (using "Add or Remove Programs" / "Apps & Features"), or you should be able to run the installer for your new version of VirtualBox.

answered 15 mins ago

David Gallagher

1313

add a comment |

The only thing that worked for me was to extract the original installer to the path.

This is what I did:

Download the installer

Open Command Prompt

Change to dir containing the installer

Run the installer with the --extract parameter. eg: VirtualBox-5.1.22-115126-Win.exe --extract

Uninstall VirtualBox in the usual way (using "Add or Remove Programs" / "Apps & Features"), or you should be able to run the installer for your new version of VirtualBox.

answered 15 mins ago

David Gallagher

1313

add a comment |

The only thing that worked for me was to extract the original installer to the path.

This is what I did:

Download the installer

Open Command Prompt

Change to dir containing the installer

Run the installer with the --extract parameter. eg: VirtualBox-5.1.22-115126-Win.exe --extract

Uninstall VirtualBox in the usual way (using "Add or Remove Programs" / "Apps & Features"), or you should be able to run the installer for your new version of VirtualBox.

answered 15 mins ago

David Gallagher

1313

The only thing that worked for me was to extract the original installer to the path.

This is what I did:

Download the installer

Open Command Prompt

Change to dir containing the installer

Run the installer with the --extract parameter. eg: VirtualBox-5.1.22-115126-Win.exe --extract

Uninstall VirtualBox in the usual way (using "Add or Remove Programs" / "Apps & Features"), or you should be able to run the installer for your new version of VirtualBox.

answered 15 mins ago

David Gallagher

1313

answered 15 mins ago

David Gallagher

1313

answered 15 mins ago

David Gallagher

1313

answered 15 mins ago

David Gallagher

1313

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Tjyylli