System: Windows Vista HP SP2 with Sun (Oracle) Virtual Box (VB) running Windows XP Pro. During a Windows update coinciding with a VB update, the uninstall/re-install routine for the VB Bridged Network Drivers failed leaving 2 registry entries for the same driver. At each subsequest VB update (some 20+) a new registry entry is created for the driver but without uninstalling the previous entry. Windows cannot resolve the reference so fails to initialise the driver. I have deleted most of the driver entries using {Control Panel}{Device Manager}{Network Adaptors}. 4 drivers cannot be uninstalled from this panel. I have tried manually uninstalling the registry entries in both normal & safe modes but Windows will not allow me to delete. As a consequence, the Bridged Network does not function. Any help to resolve this very tedious problem would be very welcome. Some specifics From the individual Network Adaptor dialog boxes Device status for 1 driver; This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available. Device status for 3 other drivers; Reinstall the drivers for this device. (Code 18) To reinstall the drivers for this device, click Reinstall Driver. Hardware ID: sun_VBoxNetFltmp Driver keys: (1) {4d36e972-e325-11ce-bfc1-08002be10318}\0018 (2) {4d36e972-e325-11ce-bfc1-08002be10318}\0014 (3) {4d36e972-e325-11ce-bfc1-08002be10318}\0021 (4) {4d36e972-e325-11ce-bfc1-08002be10318}\0038 Removal policy/Removal Policy Default = 00000001 The registry continues to hold 17 entries numbered 0000 to 0017 of which 4 have full values attributed. None can be deleted or modified. The 4 with full values correspond to the driver keys above.

System: Windows Vista HP SP2 with Sun (Oracle) Virtual Box (VB) running Windows XP Pro. During a Windows update coinciding with a VB update, the uninstall/re-install routine for the VB Bridged Network Drivers failed leaving 2 registry entries for the same driver. At each subsequest VB update (some 20+) a new registry entry is created for the driver but without uninstalling the previous entry. Windows cannot resolve the reference so fails to initialise the driver. I have deleted most of the driver entries using {Control Panel}{Device Manager}{Network Adaptors}. 4 drivers cannot be uninstalled from this panel. I have tried manually uninstalling the registry entries in both normal & safe modes but Windows will not allow me to delete. As a consequence, the Bridged Network does not function. Any help to resolve this very tedious problem would be very welcome. Some specifics From the individual Network Adaptor dialog boxes Device status for 1 driver; This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available. Device status for 3 other drivers; Reinstall the drivers for this device. (Code 18) To reinstall the drivers for this device, click Reinstall Driver. Hardware ID: sun_VBoxNetFltmp Driver keys: (1) {4d36e972-e325-11ce-bfc1-08002be10318}\0018 (2) {4d36e972-e325-11ce-bfc1-08002be10318}\0014 (3) {4d36e972-e325-11ce-bfc1-08002be10318}\0021 (4) {4d36e972-e325-11ce-bfc1-08002be10318}\0038 Removal policy/Removal Policy Default = 00000001 The registry continues to hold 17 entries numbered 0000 to 0017 of which 4 have full values attributed. None can be deleted or modified. The 4 with full values correspond to the driver keys above. Yours is the kinda of problem I live to solve since the causes are myriad and the fixes can be as brutal as your current mood. For the moment though and as you describe the inability to gracefully or surgically in the registry to remove the entries but being denied, paraphraqsing your description you weren't being allowed to delete the entries in Safe Mode or regular boot. Were you encountering Error 5's / Access Denied even after you took ownership of the keys, then granted perms and still was unable to remove the keys? And or, is it even more insidious and are the keys resurrecting at a reboot or if you turn away long enough and they return again sorta like a bad houseguest or more like a protective write filter such as EWF or the FBWF ( I didn't think Vista shouldered those two anyway). Hey, wanna just get lazy and launch the registry editor as the system account and cleave it up as you feel like without having to take ownership? Are you comfortablerunning simultaneous registry editors for the reasons we can't think for the moment but you'llbe happy you did. Just in case since it isn't widely documented regedit /m Rest assured, even if you haven't seen me in action, there isn't a system yet I've been unable to kneecap and with the precision of Lecter, just not with his culinary appetites. If these drivers are there, soon they'll be as dead as Dillinger. In the meantime, have you been experimenting with Nirsofts RegFromApp.exe ? I rely on in when I'm confronted with a recalcitrant driver that refuses to render it's INF and sys fille even after spitting every MSIEExeC switch and dissecting it with Orca. Sometimes that happens especially more often with video drivers (what did Intel ever make so great with an integrated video card and 50MB driver) and I just wanted the four files that make it go. HP is sitll trying to intravenously install their 10MB+ printer drivers installers through my eyesocket instead of just letting me have the seven files they're keeping safer than Helen Kellers favorite color. RegFromApp removes all that pretention for me.

System: Windows Vista HP SP2 with Sun (Oracle) Virtual Box (VB) running Windows XP Pro. During a Windows update coinciding with a VB update, the uninstall/re-install routine for the VB Bridged Network Drivers failed leaving 2 registry entries for the same driver. At each subsequest VB update (some 20+) a new registry entry is created for the driver but without uninstalling the previous entry. Windows cannot resolve the reference so fails to initialise the driver. I have deleted most of the driver entries using {Control Panel}{Device Manager}{Network Adaptors}. 4 drivers cannot be uninstalled from this panel. I have tried manually uninstalling the registry entries in both normal & safe modes but Windows will not allow me to delete. As a consequence, the Bridged Network does not function. Any help to resolve this very tedious problem would be very welcome. Some specifics From the individual Network Adaptor dialog boxes Device status for 1 driver; This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available. Device status for 3 other drivers; Reinstall the drivers for this device. (Code 18) To reinstall the drivers for this device, click Reinstall Driver. Hardware ID: sun_VBoxNetFltmp Driver keys: (1) {4d36e972-e325-11ce-bfc1-08002be10318}\0018 (2) {4d36e972-e325-11ce-bfc1-08002be10318}\0014 (3) {4d36e972-e325-11ce-bfc1-08002be10318}\0021 (4) {4d36e972-e325-11ce-bfc1-08002be10318}\0038 Removal policy/Removal Policy Default = 00000001 The registry continues to hold 17 entries numbered 0000 to 0017 of which 4 have full values attributed. None can be deleted or modified. The 4 with full values correspond to the driver keys above. Yours is the kinda of problem I live to solve since the causes are myriad and the fixes can be as brutal as your current mood. For the moment though and as you describe the inability to gracefully or surgically in the registry to remove the entries but being denied, paraphraqsing your description you weren't being allowed to delete the entries in Safe Mode or regular boot. Were you encountering Error 5's / Access Denied even after you took ownership of the keys, then granted perms and still was unable to remove the keys? And or, is it even more insidious and are the keys resurrecting at a reboot or if you turn away long enough and they return again sorta like a bad houseguest or more like a protective write filter such as EWF or the FBWF ( I didn't think Vista shouldered those two anyway). Hey, wanna just get lazy and launch the registry editor as the system account and cleave it up as you feel like without having to take ownership? Are you comfortablerunning simultaneous registry editors for the reasons we can't think for the moment but you'llbe happy you did. Just in case since it isn't widely documented regedit /m Rest assured, even if you haven't seen me in action, there isn't a system yet I've been unable to kneecap and with the precision of Lecter, just not with his culinary appetites. If these drivers are there, soon they'll be as dead as Dillinger. In the meantime, have you been experimenting with Nirsofts RegFromApp.exe ? I rely on in when I'm confronted with a recalcitrant driver that refuses to render it's INF and sys fille even after spitting every MSIEExeC switch and dissecting it with Orca. Sometimes that happens especially more often with video drivers (what did Intel ever make so great with an integrated video card and 50MB driver) and I just wanted the four files that make it go. HP is sitll trying to intravenously install their 10MB+ printer drivers installers through my eyesocket instead of just letting me have the seven files they're keeping safer than Helen Kellers favorite color. RegFromApp removes all that pretention for me.