-
Notifications
You must be signed in to change notification settings - Fork 241
VBox 5.1.22 can't unpack VirtualBox 6.1.0 properly #73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
..are you able to use the portable with network bridged..?? |
Not even UniExtract ( https://github.com/Bioruebe/UniExtract2/releases ) works for me (only shows "file too big"). How did you manage to extract 6.1.0 or how can I do this on Windows? |
To extract: https://www.virtualbox.org/manual/UserManual.html#installation_windows
this extracts the msi from the exe to "c:\Temp\VirtualBox\VirtualBox-6.1.0-r135406.msi" (or where temp is located)
|
I'm not sure ... Is this the default setting? My guest systems use the network/internet connection of the host system.
VBox creates a temp folder in its directory when it extracts the installer. I copied the msi file from this directory (you have to be fast) and used UniExtract2 afterwards. But cocoon's way is more convenient, that's why I'm using it now. |
Seems VBox is not regularly changing the installation directories. Is it not possible to update VBox Portable once? Does anyone know what exact folders changed, compared to the last working version of VBox Portable? |
Successfully installed VirtualBox 6.1.6 on Windows 10 The problem lies on lines 1573, 1581, 1598 and 1608 of file "Portable-VirtualBox.au3" The new installation file of Virtualbox has different command line switches and doesn't produce two files x86 and amd64. But only one The following modification is proposed Line 1573 Line 1581 Line 1598 Line 1608 |
@yannismc |
https://github.com/vboxme/Portable-VirtualBox/pull/76/files |
Maybe we need to create a fork, since runarbu doesn't seem to be around anymore since 5 years. |
finally some other clever people has realized the incredible ABSENCE of Runar Buvik here.. |
Bonjour à tous. Pour ma part je suis fan des chôses simples et je vous propose un fichier bat qui doit vous régler vos problèmes : |
..in english pls...the matter is already difficult...so pls help us understand what you write.. |
Voilà le fichier bat : |
..in english pls...the matter is already difficult...so pls help us understand what you write.. |
@streetgt thx for the PR. I tried it & compiled it with the 2 changed files, but unfortunately VB is not extracting the new "VirtualBox-6.1.8-137981-Win.exe" (x64 selected). |
It worked for me, anyway I gave up on this software ;) |
how to update VirtualBox 6.1.0 to 6.1.8 for Portable? |
I just downloaded https://download.virtualbox.org/virtualbox/6.0.24/VirtualBox-6.0.24-139119-Win.exe and gave it to Portable-VirtualBox, works like a charm |
@Shuunen |
..fine... |
I have w10 but sadly the bridged connection does not work with this solution. Bridged network seems to rely on the driver packaged into the virtualbox setup we all want to avoid. |
this so frustrating issue is there since the very late 2015.. |
why the download linkhasn't been updated yet? |
Bonjour à tous, pour ceux qui ont des problèmes d'extraction je vous donne la marche à suivre que j'utilise depuis des années |
VirtualBox 6.1.0 was just released and I tried to update the portable version. However, VBox 5.1.22 only creates a temp folder with a VirtualBox msi file inside it. VBox should unpack this msi installer to the app64 folder, but this doesn't happen. Instead, it deletes the temp folder. It seems that something changed inside the msi file.
If I unpack the msi file manually using UniExtract and place the files into the app64 folder, VBox 5.1.22 seems to work properly.
The text was updated successfully, but these errors were encountered: