Ticket #10797 (closed defect: obsolete)
Stale WinReg classes cause host-only to screw up.
|Reported by:||markfilipak||Owned by:|
I have attached "ROOT%NET%0002 - before repairing VBox.zip" which has bogus WinReg entries referencing an Unknown Adapter (Dev. Mgr. with !) with the only clue being "Device Instance Id" of "ROOT\NET\0002" (all other properties were blank). I have attached "ROOT%NET%0002 - added by repairing VBox.zip" which has good WinReg entries referencing the same adapter AFTER I had identified it as VBoxNetAdp.sys. The good WinReg entries and the bogus WinReg entries are now BOTH in the WinReg. How did I do this? I tried to update the Unknown Adapter driver. I found that the only thing that Windows would accept was Oracle Corp., Host-only. When I updated the Unknown Adapter driver to the Host-only driver, the Unknown Adapter DISAPPEARED (leaving only my original Host-only Adapter). Curiously, my original Host-only connection now has this as it's IP: 169.254.27.11/16. The original (before the Unknown Adapter disappeared) was 192.168.56.1/24. How did the bugus WinReg entries get made? I had reinstalled ("Repair") VBox three times. There were 3 bogus entries. Coincidence? It seems to me that VBox is not cleaning up the WinReg. Your mileage may vary. This problem prevented me from getting host-only working. I would appreciate a prompt reply regarding whether you'd like me to make any tests or send any additional.