Opened 9 years ago
Last modified 9 years ago
#15007 new defect
installing virtualbox on windows 10 version 1511 throws VERR_SHARING_VIOLATION
Reported by: | mmd123 | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 5.0.12 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
so yea, just downloaded the latest version of virtualbox, and tried installing it, got the installer to run correctly only to try restarting the installer process from process explorer (due to installer not doing anything at all possibly due to windows issue yet to be discovered or pinpointed) and now upon the thing restarting, it throws that error, and no matter how many times I redownload the installer, it throws this error every time....even if I delete the file from all existance and redownload it, it still throws said error.
Attachments (1)
Change History (3)
by , 9 years ago
Attachment: | virtualbox issue.PNG added |
---|
comment:1 by , 9 years ago
Replying to mmd123:
so yea, just downloaded the latest version of virtualbox, and tried installing it, got the installer to run correctly only to try restarting the installer process from process explorer (due to installer not doing anything at all possibly due to windows issue yet to be discovered or pinpointed) and now upon the thing restarting, it throws that error, and no matter how many times I redownload the installer, it throws this error every time....even if I delete the file from all existance and redownload it, it still throws said error.
uhm........ok, what the crap...sooooo....after the program threw that error, freaking 5 minutes later from time of initial attempted installation, windows prompted me to install the network driver, at which point the installer popped open to ask if I wanted to repair or uninstall, and upon clicking repair, it fixed itself and installed properly, at which point it opened the installed program.... I'm officially confused as heck, but that might be something you guys want to look into maybe?? it apparently worked, just after significant delays on my system...not sure if my issue, or installer/windows issue.
comment:2 by , 9 years ago
priority: | blocker → major |
---|
Definitely something worth to investigate once we are able to reproduce it.
error screenshot