blocks|key|4477100|text|我的Windows10机器今天自动更新了。看起来像是“Windows10周年纪念更新”，当我用桥接适配器重启Virtualbox时，服务器显示与OP相同。我尝试重新运行VirtualBox安装程序(它进行了修复)-但没有解决问题。我尝试以Admin身份再次运行安装程序(它进行了修复)-但没有修复。我运行了安装程序并选择了UnInstall，然后再次运行它进行安装。并且网络适配器设置看起来很好。服务器像往常一样启动并连接到我的网络。呼。希望这对某些人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477101|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My Windows 10 machine was automagically updated today. Looks like the "Windows 10 Anniversary update" When I restarted Virtualbox my server with a bridged adapter showed same as OP. I tried rerunning the VirtualBox installer (it did a Repair) - that did not fix the issue. I tried running the installer again as Admin (it did a Repair) - that did not fix. I ran the installer and selected UnInstall, then ran it again to Install. And the Network adapter settings looked good. Server started and connected to my network as usual. Whew.
Hope this helps someone.

blocks|key|4478044|text|转到您的网卡。转到属性，然后选择Install+->+Service，是哪一个？这:+VirtualBox+NDIS6桥接网络驱动程序|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4478045|重新打开虚拟盒子|4478046|entityMap^0|G|7|R|7|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Go to your net card. Go to properties and then <code>Install</code> -&gt; <code>Service</code>, which? This: VirtualBox NDIS6 Bridged Networking Driver
Reopen Virtual Box

blocks|key|4477002|text|安装最新的Virtual+box+5.x，此问题将得到解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477003|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Install the latest Virtual box 5.x and this issue will be resolved.

blocks|key|4476972|text|这就是我解决这个问题的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4476973|为VirtualBox可执行文件启用“Windows8”兼容性:右键单击VirtualBox+shortcut>Properties:在属性对话框中:切换到“兼容性”选项卡，在“兼容模式”部分下，选中“在兼容模式下运行此程序”旁边的复选框，确保在组合框中选中“Windows8”。单击Ok，再次运行VirtualBox！(不需要以管理员身份运行)|4476974|附言:+VirtualBox似乎还没有完全支持Windows10，所以一些功能可能在一些电脑上不能正常工作|4476975|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This is how I mananged to fix this problem:

Enable "Windows 8" compatibility for VirtualBox executable:
right-click on VirtualBox shortcut>Properties: in Properties dialog box: switch to "Compatibility" tab, under "Compatibility mode" section, select the check box next to: "Run this program in compatibility mode", make sure "Windows 8" is selected in combo box. click Ok, run VirtualBox again!
(it's not needed to run as Administrator)

p.s.: It seems that VirtualBox doesn't yet fully support Windows 10, so some features might not work properly on some computers

blocks|key|4477937|text|卸载，然后再次运行安装程序，但这次是以管理员身份运行。确保在安装过程中选择了VB桥驱动程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477938|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Uninstall then run the setup program again but this time as Administrator. Make sure the VB bridge driver is selected during installation.

blocks|key|4477135|text|从%25userprofile%25\\.virtualbox\安装"vbox-ssl-cacertificate.crt“证书，然后重启。如果你没有.virtualbox文件夹--启动"Oracle“一次，这个文件夹就会出现。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4477136|我不仅在我的机器上有这个问题，而且在许多主机上也有这个问题，这个证书解决了这个问题。我是偶然发现的，因为没人说过这个证书--|4477137|entityMap^0|1|R|1Z|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Install "vbox-ssl-cacertificate.crt" certificate from <code>%userprofile%\\.virtualbox\</code> and then reboot. If you don't have <code>.virtualbox</code> folder - launch "Oracle VM VirtualBox" once and this folder will appear. 

I had this issue not only on my machine but on many hosts, and this certificate fixed the issue. I figured it out by chance, because nowhere said about this certificate -_-

blocks|key|4477191|text|我用类似@Khalil的方法解决了这个问题，但我附加了“桥接适配器”而不是“仅主机适配器”。Here是更详细的屏幕截图。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4477192|entityMap|0|LINK|mutability|MUTABLE|url|https://gblue1223.wordpress.com/2017/08/16/virtualbox5-1-26s-bridge-mode-on-windows-10/^0|1A|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I solved it with similar way to @Khalil's but I attched to 'Bridged Adapter' instead of 'Host-only Adapter'. <a href="https://gblue1223.wordpress.com/2017/08/16/virtualbox5-1-26s-bridge-mode-on-windows-10/" rel="nofollow noreferrer">Here</a> is more detail with screenshots.

blocks|key|4478192|text|当使用桥接连接时，您正在将来宾(VM)的虚拟网络桥接到主机(Windows+10)的物理网络设备。然后，主机物理设备分配IP地址并管理客户OS+(VM)的网络连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4478193|​|4478194|📷|atomic|offset|length|4478195|4478196|你需要检查的东西。在Windows10(主机)上，转到控制面板/网络和互联网/网络连接，在来宾操作系统(VM)上右击要桥接的物理设备，并确保启用了"VirtualBox+NDIS6桥接网络驱动程序“和"Brdige驱动程序”。|4478197|4478198|4478199|4478200|注:访客(VM)+VirtualBox设置中的网桥连接选择与物理设备名称相同...此外，您可能会发现主机上的非活动/禁用的网络设备不会显示在主机(windows+10)中，直到您将它们连接到它们，即以太网电缆连接到LAN端口。|4478201|这应该可以帮助您解决桥接连接问题。|4478202|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c4a9f07bb184fe0a9429a0d525b6a6cb.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/51994c5c963ae7e7d338d52650c02a11.png^0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@$G|16|H|17|1|18]]|A|$]]|$1|I|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|E|5|F|7|1C|8|@]|9|@$G|1D|H|1E|1|1F]]|A|$]]|$1|N|3|C|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]|11|$5|V|W|X|A|$Y|12|10|-4]]]]

When using a bridged connection you are bridging the virtual network of the guest (VM) to the physical network device of the host (Windows 10). The host physical device then assigns the IP address and manages the network connection of the guest OS (VM).
<a href="https://i.stack.imgur.com/xwTjT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xwTjT.png" alt="enter image description here" /></a>
What you need to check. On Windows 10 (host), go to Control Panel/Network and Internet/Network Connections, right click the physical device that you are trying to bridge to on your guest OS (VM) and make sure that &quot;VirtualBox NDIS6 Bridged Networking Driver&quot; and &quot;Brdige Driver&quot; are enabled.
<a href="https://i.stack.imgur.com/v9nRd.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/v9nRd.png" alt="enter image description here" /></a>
Note:
The bridge connection choice in the guest (VM) VirtualBox settings and the phsyical device name are the same...
Also, you may find that inactive / disabled network devices on the host will not show in the host (windows 10) until you connect to them i.e. ethernet cable to a LAN port.
That should help you solve the bridged connection issue.

blocks|key|4477248|text|在更新了Virtual+Box之后，我今天遇到了同样的问题。通过卸载Virtual+Box并移回旧版本V5.2.8解决了问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477249|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I faced the same problem today after updating the Virtual Box.
Got resolved by uninstalling Virtual Box and moving back to old version V5.2.8

blocks|key|4477277|text|到目前为止(5.2.20)错误已经修复。唯一需要的操作是下载最新版本，桥接模块应该可以正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477278|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As of now (5.2.20) bug is fixed. The only action required is to download the latest version and bridge mod should function normally.

blocks|key|4477315|text|以防有人在看，上面的方法都不能解决您的问题：https://forums.virtualbox.org/viewtopic.php?f=6&t=90650&p=434965#p434965|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4477316|将WIFI作为第一适配器MTDesktop、AllowALL，将局域网有线MTServer、AllowAll作为第二适配器。在来宾计算机上，我在适配器设置中禁用了第一个适配器。然后我可以ping内部的，外部的任何东西。|4477317|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.virtualbox.org/viewtopic.php?f=6&t=90650&p=434965#p434965^0|M|20|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

In Case some one is looking and none of the above resolves your issue :
<a href="https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=90650&amp;p=434965#p434965" rel="nofollow noreferrer">https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=90650&amp;p=434965#p434965</a>

placing the WIFI as the first adapter [MTDesktop, AllowALL] and the LAN WIRED [MTServer,AllowAll] as the second adapter.
In the Guest machine I disable the First Adapter in Adapter Settings. I can then ping internal, external whatever.

blocks|key|4477331|text|我也有同样的问题。我更新到新版本的VirtualBox+5.2.26，并检查以确保在安装过程中启用了网桥适配器，现在可以工作了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4477332|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

i had same problem.
i updated to new version of VirtualBox 5.2.26
and checked to make sure Bridge Adapter was enabled in the installation process 
now is working

blocks|key|4478134|text|两行答案:对于有线连接，它将顺利工作；对于无线，如果您的无线适配器不支持promiscious模式，请打开“promiscious模式”，以下是要解决的link。也可以访问offical+oracle+virtualbox文档，查看有关通过wifi使用桥接连接的更多细节here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4478135|entityMap|0|LINK|mutability|MUTABLE|url|https://www.revolutionweb.com.au/computer-security/use-wireless-adapter-virtualbox-bridge-mode/|1|https://www.virtualbox.org/manual/UserManual.html#network_bridged^0|24|4|0|3R|4|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

Two line answer: For wired connections it will work smoothly, for wireless turn on 'Promiscious mode' if your wireless adapter does not support promiscious mode, here is the <a href="https://www.revolutionweb.com.au/computer-security/use-wireless-adapter-virtualbox-bridge-mode/" rel="nofollow noreferrer">link</a> to workaround. Also visit offical oracle virtualbox documentation to see more details <a href="https://www.virtualbox.org/manual/UserManual.html#network_bridged" rel="nofollow noreferrer">here</a> on using bridged connection over wifi.

I just upgraded my laptop from Windows 7 to Windows 10 and found that I am unable to start Virtualbox VMs configured with a bridged adapter.

See the configuration below:

<a href="https://i.stack.imgur.com/AckzK.png"><img src="https://i.stack.imgur.com/AckzK.png" alt="Virtualbox preferences 1"></a>

<a href="https://i.stack.imgur.com/UpVTc.png"><img src="https://i.stack.imgur.com/UpVTc.png" alt="Virtualbox preferences 2"></a>

Bridged networking not working in Virtualbox under Windows 10

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我刚刚将我的笔记本电脑从Windows 7升级到Windows 10，发现我无法启动配置了桥接适配器的Virtualbox虚拟机。请参见以下配置：​​​​

问桥接网络在Windows 10下的Virtualbox中不起作用
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问桥接网络在Windows 10下的Virtualbox中不起作用EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问桥接网络在Windows 10下的Virtualbox中不起作用
EN