Custom Query (16363 matches)
Results (2083 - 2085 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11259 | duplicate | VirtualBox Host-Only does not report itself as a virtual adapter on Windows 7 | ||
| Description |
I installed VirtualBox and had the Juniper Pulse client configured with a profile that suppresses wireless connections on Windows 7 when a wired connection is detected. Microsoft reported the VirtualBox host-only network adapter as a wired connection and caused suppression of wireless networks causing loss of connectivity when not wired in. This is a blocker for non-advanced users who cannot modify profiles or kill applications that suppress wireless connections when wired connections are detected. |
|||
| #14326 | fixed | 5.0 NDIS6 Bridged Driver kills host network | ||
| Description |
After installing Vbox 5.0 on Windows 7 x64, the host LAN stops functioning. Tried both 5.0.0-101573 and 5.0.1-101778. If I unbind the bridged adapter in the LAN network adapter properties, the LAN immediately begins to work again. Without it bound, Vbox guests can't use bridged networking. See https://forums.virtualbox.org/viewtopic.php?f=6&t=68980 |
|||
| #13355 | duplicate | Problem in verify process integrity | ||
| Description |
Starting from version 4.3.14, running on Windows 7 SP1 with Symantec Endpoint Protection version 12.1.4112.4156, VirtualBox fails to startup. Following the instruction displayed by the program, I've contacted the antivirus manager that disabled the ADC component of the antivirus but the problem persist. The Virtual Box manager starts correctly but trying to starts any of the VM present fails. I've tried to reinstall version 4.3.14 with ADC component disabled but nothing worked. When I've downgraded to versione 4.3.12 everything worked correctly. I don't know if it's an antivirus problem related, since prior to versione 4.3.14 everything worked fine. Regards. |
|||

