Custom Query (16363 matches)
Results (1417 - 1419 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17650 | worksforme | Random crash VM and Nat Network together | ||
| Description |
Hello! Host Ubuntu Server 17.10 Have here Nat network and 3 VMs: 1) Win2016 2) Win2016 (Exchange) 3) Debian 9 (openvpn) Random crash 1-5 days with VM №2 (Exchange) with blackscreen and Nat network on other VMs has not ping. Poweroff all VMs (Exchange with emergency stop) and restart virtualbox service help for anothe 1-5 day. |
|||
| #17649 | fixed | Drag/Drop files stop working when restarting VM from saved state -> fixed in 5.2.20 | ||
| Description |
I am running virtual Box 5.2.8 r121009 with a windows 10 VM running on a host Ubuntu 16. The problem is that when I start my windows VM the drag/drop files works seamlessly in the beginning. I can drag drop files from my windows VM desktop to the Linux without a problem. But then I choose to shut down my VM and in the "Close Virtual Machine" dialog i choose "Save the machine state". When I power on the machine again and restore it's state, the drag/drop files option stop working. The only way to get the option back is to shut down my VM machine completely instead of saving it's state. But then that means i have to restart windows 10 and wait for the whole boot procedure. Can you please fix this issue as it's a real pain to do it like this... |
|||
| #17647 | duplicate | Host-Only adapter failled to install | ||
| Description |
Hello, [How to reproduce it] From fresh installation, installation was ok,I had no problem to use host-only network and the host-only adapter was present. The problem began when I removed using VirtualBox GUI my host-only adapter, I was then not able to re-create it using either the GUI and the command line. [Similar issues] As you can imagine I've walk through the VirtualBox forum and Bug tracker before posting and I found a similar issue : + https://www.virtualbox.org/ticket/17354 + https://forums.virtualbox.org/viewtopic.php?f=6&t=86179 Here the antivirus was involded and disable it resolved the issue. In my case I've completely uninstall my corporate antivirus + deactivate Windows Defender without success. [Troubleshooting] + Repair VirtualBox + Uninstall VirtualBox + Remove %userprofile%\.virtualbox + Remove drivers in %windir%\System32\drivers + Remove registry keys about VirtualBox + Install 5.2 VirtualBox + Run Installer as Admin right + Run a Ccleaner registry cleaning With a result always the same, failed to create host-only adapter. [logs] VirtualBox Gui logs are showing : Failed to create a host network interface. Querying NetCfgInstanceId failed (0x00000002). Code d'erreur : E_FAIL (0x80004005) Composant : HostNetworkInterfaceWrap Interface : IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9} C:\Windows\INF\setupapi.dev.log
!!! idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37fe176ed22ac0b0'. Error = 0x00000005 <<< Section end 2018/03/27 18:20:45.540 <<< [Exit status: FAILURE(0x00000005)] [other] It's just a supposition but I'm wondering if the issue is trigered also as I respond [NO] once to the UAC pop-up message asking to install host-only driver (after choosing to create host-only adapter from the GUI). Thanks in advance for all your help, this issue is a blocker for me. |
|||

