Application: VirtualBox
Category: Utilities
Description:
Oracle VM VirtualBox
Features: VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 3. See "About VirtualBox" for an introduction.
Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD.
VirtualBox is being actively developed with frequent releases and has an ever growing list of features, supported guest operating systems and platforms it runs on. VirtualBox is a community effort backed by a dedicated company: everyone is encouraged to contribute while Oracle ensures the product always meets professional quality criteria.
v7.0.14
Download VirtualBox Portable 7.0.14 Dev Test 2 [97.4MB download / 212MB installed]
(MD5: 73a4a22b2a51a76b00d7b3356d766dc7)
(SHA256: d7108ccc89a6912579b9f2fd413133a16efb85428b3c112bd31a2808a6fb2e00)
(SHA512: 1f214d64e91fb846eeb06dde91df37a1876cbb2c3616bbaf3e90c7fcbaf446a9e25428603f8e0191d361a72f84fd4e0f6c9eff971fb9a235c6865c13d9c23212)
v6.1.50
Download VirtualBox Portable 6.1.50 Dev Test 2 [96.3MB download / 223MB installed]
(MD5: c69f3aa9f6da1dae519caf9500e18d11)
(SHA256: 66fb655310513b0dfd07b02263ae0b676da22b41f68c4cfc01d5921ba8e66505)
(SHA512: 99a1a3d0e77fa002ada61e54020da0a29daab5c759f1879481cf52c5f5e5062e97502eac05e6699f84e2edc70055e066abe535183d1d36729b2f7efc277b579e)
v6.0.24
Download VirtualBox Portable 6.0.24 Dev Test 2 [89.3MB download / 256MB installed]
(MD5: 0298f203331be4f30a3ae28233f5adcf)
(SHA256: 47bf15a402275c9af67a6bb5c79ea5ff5924ed1bbe1eab5d1600e119e6568ea4)
(SHA512: cf3d92d2bc47568d1c5f04451c74fd2d7173ad2f6d0e9cebf205f2709453c699d3fab53a1dc59ebbd3ab974aa91ead7de939be7be92d03407b8b6d73a6733f34)
v5.2.44
Download VirtualBox Portable 5.2.44 Dev Test 2 [31.9MB download / 107MB installed]
(MD5: c6bbaf6dd57961d6db2d1f7bd5dab126)
(SHA256: b911354b5630b7d0ba0b5e3cef54ae71da26dd9647f7e8ad715d081e4f251b17)
(SHA512: 2335681cadd68056c462ec23f005d46fe40c8ddcc40a551faf3b3fa69e77cda92ddaff0f4a4f603467e97bc3d2cdf7c8ea0143cf9229c7fe0f8b185a7efda42e)
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Reserving the name "vboxPortable" in case of issues like with ccleaner, etc.
v5 leaves a VBoxSVC.log file behind in
%USERPROFILE%/.VirtualBoxv6 leaves the same and also a VBoxSDS.log file behind in
%PROGRAMDATA%/VirtualBoxI've tried all of the stuff I know... time to learn some new tricks. If anybody feels like pitching in, it would be greatly appreciated.
For the
settings\.VirtualBox=%USERPROFILE%\.VirtualBoxyou can useFor the
ProgramDatathe default is%ALLUSERSPROFILE%and/or%ALLUSERSAPPDATA%, but this does not work with VirtualBox :( See: https://portableapps.com/manuals/PortableApps.comLauncher/ref/envsub.html#allusersprofile and https://portableapps.com/manuals/PortableApps.comLauncher/ref/envsub.html#allusersappdata. Also there is a serviceVBoxSDS(VirtualBox system service) which is not removed when the VBox exit...Where would one gain a knowledge of how to suss out those [Environment] keys, if one were so inclined..?
I need to learn more about how these work.
It seems there are a few ways to do the same thing in many cases. Good to know we're not out of options... but yeah the service file is the one i'm more concerned about absorbing.
Well, it depend of the app. If you search for the `VBOX_USER_HOME` you will find many results. Just search for `AppName environment` and if you are lucky you will find results
About the service you will need a custom code again with content:
${SegmentFile} ${SegmentPostPrimary} nsExec::Exec '$AppDirectory\x64\VBoxSDS.exe /unregservice' !macroendAbout the ProgramData logs you will need to add
WaitForEXE1=VBoxSDS.exeat the[Launch]section. I think the launcher exit before the vboxsds.exe and this is the case that the%ALLUSERSAPPDATA%\VirtualBoxdoes not work. Also if you don't care about the logs you can use:Also you may think about the virtual machines store. By default the Vbox place it in the %userprofile%
Thanks for the heads up on the App Environment... however, the [DirectoriesCleanupForce] did not work... this is why I'm asking if anybody knows any other tricks.
This is my version of the files:
\VirtualBox7.0Portable\App\AppInfo\Launcher\VirtualBox7.0Portable.ini
```
[Launch]
ProgramExecutable=x64\VirtualBox.exe
WaitForEXE1=VBoxSDS.exe
DirectoryMoveOK=yes
SupportsUNC=yes
RunAsAdmin=try
[Activate]
Java=find
XML=true
[DirectoriesCleanupForce]
1=%ALLUSERSPROFILE%\VirtualBox
[Environment]
VBOX_USER_HOME=%PAL:DataDir%\VirtualBox
[FileWrite1]
Type=Replace
File=%PAL:DataDir%\VirtualBox\VirtualBox.xml
Find=$DEFAULTMACHINEFOLDER$
Replace=%PAL:DataDir%\VirtualBoxVMs
[FileWrite2]
Type=Replace
File=%PAL:DataDir%\VirtualBox\VirtualBox.xml
Find=%PAL:LastDrive%%PAL:LastPackagePartialDir%\
Replace=%PAL:Drive%%PAL:PackagePartialDir%\
[FileWrite3]
Type=Replace
File=%PAL:DataDir%\VirtualBox\VirtualBox.xml
Find=%PAL:LastDrive%%PAL:LastPortableAppsBaseDir%\
Replace=%PAL:Drive%%PAL:PortableAppsBaseDir%\
[FileWrite4]
Type=Replace
File=%PAL:DataDir%\VirtualBox\VirtualBox.xml
Find=%PAL:LastDrive%\
Replace=%PAL:Drive%\
```
\VirtualBox7.0Portable\App\AppInfo\Launcher\Custom.nsh
```
${SegmentFile}
${SegmentPostPrimary}
nsExec::Exec '$AppDirectory\x64\VBoxSDS.exe /unregservice'
!macroend
```
\VirtualBox7.0Portable\App\DefaultData\VirtualBox\VirtualBox.xml
I can not use <pre> tags or markdown for XML
```
<?xml version="1.0"?>
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.12-windows">
<Global>
<SystemProperties defaultMachineFolder="$DEFAULTMACHINEFOLDER$"/>
</Global>
</VirtualBox>
```
Because of the Custom.nsh you must rebuild the launcher. And because of the DefaultData folder you must delete the current Data folder.
Thank you.
Implemented changes discussed about removing VBoxSDS.log. Changes proved successful.
VirtualBox Portable: 7.0.14 Dev Test 2
When I start a VM, I got this error:
NtCreateFile(\Device\VBoxDrvStub) failed:0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)
Make sure the kernel module has been loaded successfully.
where: supR3HardenedWinReSpawn what: 3 VERR_OPEN_FAILED (-101) - File/Device/ open failed. Driver is probably stuck stopping/starting.
Try 'sc.exe query vboxsup' to get more
Probably "VirtualBox system service" (/App/x64/drivers/vboxsup/VBoxSup) isn't running.
Same error
NtCreateFile(\Device\VBoxDrvStub) failed:0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND
for me too
(Win11)
I am aware of the issue, and am working on a way to install the necessary VboxSup.sys file during the install process... it used to be a VboxSys.inf file... or similar. It has been changed since version 5... seems like a trivial change honestly. There might a way to script it. I'm just not super familiar with NSIS etc. Been here 8 years, and I learn something every day.
as subject, I succesfully installed in portable apps platform, but found still needs admin right to open, I am not authorised the admin right
maybe you can run it without admin rights this way:
https://superuser.com/questions/171917/force-a-program-to-run-without-ad...
i help where i can! maybe you can help (me) too! see in my account under 'track' for my conservations/threads. be nice!
if you don't want to help, don't post crap!
Some programs, even though portable, still require administrator rights to run.
See: https://portableapps.com/manuals/PortableApps.comLauncher/ref/launcher.i...
As I understand it, many people use portableapps to circumvent security measures implemented by their school or work. As a libre software enthusiast, I'm all for it... but from a security standpoint, it's a huge no-no. I'm not sure of your specific use-case, but please make sure you have permission to run the programs you are running on the machines you are running them on. Virtualbox, or any other hypervisor program would allow you all types of access to things that may not be allowed on your network... and if setup improperly, can be a backdoor for shady actors.
Stay frosty, homie.