Just grabbed (pVB) Portable-VirtualBox_v5.0.26-Starter_v6.4.10-Win_all.exe and since things didn't appear to go smoothly during the "installation of Portable VirtualBox, I also grabbed (VB) VirtualBox-5.2.0-118431-Win.exe to point PVB extraction to an actual local file. This was done on a brand new PC/desktop with Win 10 Pro 64bit OS on it. It's only a week old and has not had VB on it before. New employer, new system.
Why is it that even though I chose to extract the 64bit files, given that this is a 64bit system, when I use the VB UI to create new VMs, I only have options for 32bit OSes? And the "app" folder inside the PVB folder hierarchy is app64.
Is the intention supposed to be that a user can/should selected both 32 and 64bit files for extraction?
Just grabbed (pVB) Portable-VirtualBox_v5.0.26-Starter_v6.4.10-Win_all.exe and since things didn't appear to go smoothly during the "installation of Portable VirtualBox, I also grabbed (VB) VirtualBox-5.2.0-118431-Win.exe to point PVB extraction to an actual local file. This was done on a brand new PC/desktop with Win 10 Pro 64bit OS on it. It's only a week old and has not had VB on it before. New employer, new system.
Why is it that even though I chose to extract the 64bit files, given that this is a 64bit system, when I use the VB UI to create new VMs, I only have options for 32bit OSes? And the "app" folder inside the PVB folder hierarchy is app64.
Is the intention supposed to be that a user can/should selected both 32 and 64bit files for extraction?