virtualbox.org

Hi, I think i am doing something wrong, but taking some time to read here and search a lot, I did not find a solution.

Everytime when I update Virtualbox this involves uninstall of the previuos version. Well, this is quite funny as it reminds me on computer usage around 1996, very nice historic joke. I believe, there is a secret update trick, that I can not find?

Also on updates, what really was very, very good joke, the Virtual Host Interfaces on Windows all disappeared - so each and every virtual machine has to be reconfigured with a new-to-create virtual host interface - wow, I believe, I am a total idiot beause i did not find anything about how to avoid this illness???

Also the uninstall-install update procedure kills windows network bridges configured with Virtual Host Interfaces that have been installed before - what is really annoying is the fact, that windows does not seem to be able to handle the situation that the configured interface for the bridge disappeared - so it is not possible to delete the bridge. Of course it is not possible to do anything with the bridge - it´s now a "death" windows item lying around in my windows network. Wow, that is really bad.

Will this happen on every update?

I learned from the first update I made so I removed the bridge before uninstall / install. Very cool. Of course the Virtual Hostinterfaces still vanished and all VMs had to be reconfigured - there must be some way to preserve the interfaces - could you please tell me, how to do this and PLEASE publish this information on the homepage of the website so people know BEFORE? THANKS!!!

There is a HUGE warning when you start the installer that all the virtual interfaces will be REMOVED when continuing the installation. What more of a warning do you need? If you're too eager to hit next, next, install, OK, then it's your own fault that you miss that info. If they could go around this issue, it would have been done sooner, but it seems that it's a windows issue, possibly because of the drivers for the devices. VB uses it's own driver for the virtual interfaces.

For the 'broken' bridge, you can call it's properties and tick the interfaces you want to be a part of the bridge, or right click an interface and select 'add to bridge', so it isn't as 'dead' as you claim it to be.

About the warning: I did not see the warning. I believe, there was no warning, however, if there was one, it should be made BIG, FAT and RED

Of course the warning is still just a warning. If you look at other software that needs its own interfaces, it is possible to update the whole thing without loosing all the interfaces. A distinct installer would be a good solution. There must be done some work on this, as this is totally annoying. I was testing vbox for use in a bigger scenario - but this misconception is a showstopper and will not let vbox into our environment, as long it is not resolved - if you are involved in development please print out this sentence and put it on a BIG poster on the wall:

BREAKING ANYTHING ON UPDATE IS A BIG SIN AND I WILL GO TO HELL IF I IMPLEMENT BROKEN UPDATE WITH MY SOFTWARE!


About the bridge: it is NOT possible to add anything to the bridge. That is the problem! Otherwise I would not complain, right? The bridge is a "dead item" in terms of that it is not possible to delete the bridge, to add anything to the broken bridge or to do anything with it! Windows just keeps on searching for the vanished interface and it is only possible to restore the whole system. Of course this is a typical Mickysoft-illnes and not really your fault - but you should consider this problem as yours, as it leaves no other way than restoring the system after vbox uninstall, what leads to "vbox broke my whole system"-perception.

BTW don´t be so sensitive and humor-resistent - I am writing here, because I think vbox is a good piece of software, otherwise I would not spend my time showing you the problems to resolve and dive into the mud of public discussions.

There is a warning, and yes, it's very annoying.

That's why we have rewritten the host interface networking on Windows completely. All this nonsense will be a thing of the past with the next major release.

sandervl wrote:All this nonsense will be a thing of the past with the next major release.

TORA, TORA, TORA!!! Great!

Again some good programmers lost for Mr. Devil

sandervl wrote:That's why we have rewritten the host interface networking on Windows completely. All this nonsense will be a thing of the past with the next major release.

Really?? You mean no more host interface required at all? That would be wonderful. And I know this is on Terry's list, so I'm sure he'd be in favour too..