Open d4k0 opened 4 years ago
..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
VirtualBox-<version>-<revision>-Win.exe -extract
this extracts the msi from the exe to "c:\Temp\VirtualBox\VirtualBox-6.1.0-r135406.msi" (or where temp is located)
+
lessmsi to extract the msi (for me the administrative installation did not work "msiexec /a"):
..are you able to use the portable with network bridged..??
I'm not sure ... Is this the default setting? My guest systems use the network/internet connection of the host system.
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?
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
Run (@ScriptDir & "\virtualbox.exe --extract --path temp", @ScriptDir, @SW_HIDE)
Line 1581
Run ($SourceFile & " --extract --path temp", @ScriptDir, @SW_HIDE)
Line 1598
RunWait ("cmd /c ren ""%CD%\temp\*.msi"" x86.msi", @ScriptDir, @SW_HIDE)
Line 1608
RunWait ("cmd /c ren ""%CD%\temp\*.msi"" amd64.msi", @ScriptDir, @SW_HIDE)
@yannismc Can you submit a pull request?
@yannismc Can you submit a pull request?
Maybe we need to create a fork, since runarbu doesn't seem to be around anymore since 5 years.
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.. thanks so much for yr witness cheers
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 : echo extract msi C:\Users\ADMINI~1\Desktop\VBOX\VIRTUA~1.EXE --extract -path C:\Users\ADMINI~1\Desktop\VBOX\extract echo install Administrative msiexec /a "C:\Users\ADMINI~1\Desktop\VBOX\extract\VIRTUA~1.MSI" /qb TARGETDIR="C:\Users\ADMINI~1\Desktop\VBOX\temp" pause Le reste est un jeu d'enfants
..in english pls...the matter is already difficult...so pls help us understand what you write.. thxs ;)
Voilà le fichier bat : D'abord créer un dossier de travail "VBOX" ou autre Pour l'extraction echo extract msi C: 'Users’ADMINI1'Desktop’VBOX’VIRTUA1.EXE -extract -path C:'Users’ADMINI1'Desktop’VBOX Et pour l'installation administrative msiexec /a "C:'Users’ADMINI1'Desktop’VBOX’extract’VIRTUA1.MSI" /qb TARGETDIR'"C:'Users’ADMINI1'Desktop’VBOX’temp"
..in english pls...the matter is already difficult...so pls help us understand what you write.. thxs ;)
@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).
@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 VirtualBox 6.0.x still works, the problem started with VirtualBox 6.1.x.
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
..fine... are you able to use network -bridged-..? ..having win 10 as s.o host..?
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
..fine... are you able to use network -bridged-..? ..having win 10 as s.o host..?
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.. what a real pity.. :(
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 Pour extraire le msi (chemin où est virtualbox.exe) --extract -path (chemin où vous voulez l'extraire) exemple : %USERPROFILE%\Desktop\Appz\Virtualbox.exe --extract -path %USERPROFILE%\Desktop\Extract Pour son installation administrative msiexec /a (chemin où virtualbox.msi" /qb TARGETDIR=chemin du dossier qui contiendra l'installation)" exemple : msiexec /a "%USERPROFILE%\Desktop\Extract\Virtualbox.msi" /qb TARGETDIR="%USERPROFILE%\Desktop\install" Bonne journée
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.