Custom Query (16363 matches)
Results (1471 - 1473 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17453 | worksforme | VirtualBox 5.2.4-119785 does not install on Windows 10 | ||
| Description |
Error message: "the feature you are trying to use is on a network resource that is unavailable." It asks you to give it the path to VirtualBox-5.2.2-r119230-MultiArch_amd64.msi, which doesn't exist in C:\Users\admin\AppData\Local\Temp\VirtualBox\ The file that exists is VirtualBox-5.2.4-r119785-MultiArch_amd64.msi Telling the installer to use this file instead of the one it is looking for does not help it move forward. Renaming the existing file to the name the bootstrapper is expecting is impossible, since the msi is being held in use by the bootstrapper itself. Installation is impossible. Clearly a build error in the bootstrapper, almost certanly reproducible in all version of Windows 64 bits. |
|||
| #17452 | invalid | Resume VM Bugs | ||
| Description |
I am currently running Mac OS 10.11.16 (El Capitan) and below as my host OS. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial I just started having issues perhaps with a recent update of Virtual Box that when I pause the Linux VM, upon resuming the VM two things happen. The first is the screen is black and I have to resize the screen for the desktop to appear. The second is that the mouse cursor does not show in Linux. I tried the following without luck to resolve the mouse cursor:
I have not had any issues like this for over a year with this same VM. Also an older back up of the machine that I had not modified from several months ago displays this behavior, which is point me towards thinking it has to do with Virtual Box vs. the guest OS. |
|||
| #17451 | worksforme | Immutable images take an extra minute before starting to boot | ||
| Description |
I have a VirtualBox image that I use for testing things on a new install of a particular OS. I don't want any changes to be saved after the virtual machine is exited because I want it to always return to the state of a new install for future testing, so I made the image immutable. In VirtualBox 5.1, starting an immutable image immediately went to booting the virtual machine. I just switched from VirtualBox 5.1.30 to VirtualBox 5.2.4, and now starting an immutable image brings up a dialog box that says "Disk Image Reset Operation - Immutable Image", which blocks progress for about a minute before the virtual machine starts to boot. This extra wait is a worse situation than with VirtualBox 5.1. |
|||

