Page 1 of 1
Installation issue 6.1.4
Posted: 4. Apr 2020, 13:03
by gkhar2
Hey, i just wanted to install 6.1.4 into a new directory, besides my old 6.0 directory, as i am afraid, sth goes wrong and i need to go back.
So actually of course again something went wrong.
After starting the install, the installation program ask me to provide the path to a 5.2.20 version of virtualbox. This was way old and is already uninstalled long ago.
see pics.
Can anybody help, what to do?
As i said, because almost every installation of vbox gives me issues, i do not want to install into the same directory as my 6.0 installation.
thanks and regards
Re: Installation issue 6.1.4
Posted: 5. Apr 2020, 09:45
by gkhar2
guys, could solve it.
So the issue is, that the installer seems to check if older installations are still somehow on the system.
To delete these rests of old installations, it needs the respective .msi files from the old installations.
These are located in the c:/users/xxx/ApPData/local/temp/
They were missing in my temp.
So what to do:
load all old versions the intaller needs from:
.....I am not allowed to post the link... check for old builds and virtualbox in google
open powershell with admin and type for each needed version:
e.g. VirtualBox-5.2.20-125813-Win.exe -extract
The installer will then extract the needed .msi into the temp folder.
This happened for me 3 or 4 times with different versions needed.
I do not know, why the installer needs these old versions, but when you put it there it works.
After doing all this it finished and i came to next issue.
Hardening errors:
2e84.167c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
2e84.167c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe62 and 0x9fe6c in #1 (.text), first: 8b != b8
So i got really annoyed and checked again in the doc, but found out that lots of people have these issues, and there are lots of possible rootcauses.
I did one simple thing that helped in my case: Shutdown (reboot did not help) 2 times.
After that all worked fine.
oh one more thing: my old Virtualbox 6.0.12 installation does not work any longer. So it seems, only one version of vbox can actually work on my system.
Hope i could help a bit and stay safe.
regards
gkhar2