| 2 | | |
| 3 | | I've noticed the following event in the Windows System Event Log when I boot up. It may be related: |
| 4 | | |
| 5 | | {{{ |
| 6 | | - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> |
| 7 | | - <System> |
| 8 | | <Provider Name="VBoxNetLwf" /> |
| 9 | | <EventID Qualifiers="49156">12</EventID> |
| 10 | | <Level>2</Level> |
| 11 | | <Task>0</Task> |
| 12 | | <Keywords>0x80000000000000</Keywords> |
| 13 | | <TimeCreated SystemTime="2019-10-27T11:38:21.734816600Z" /> |
| 14 | | <EventRecordID>5632</EventRecordID> |
| 15 | | <Channel>System</Channel> |
| 16 | | <Computer>tycho</Computer> |
| 17 | | <Security /> |
| 18 | | </System> |
| 19 | | - <EventData> |
| 20 | | <Data>\Device\VBoxNetLwf</Data> |
| 21 | | <Binary>0000000001000000000000000C0004C0080000000000000000000000000000000000000000000000</Binary> |
| 22 | | </EventData> |
| 23 | | </Event> |
| 24 | | }}} |
| 25 | | |
| 26 | | VBoxNetLwf is "the light-weight filter driver for NDIS6". If it fails to load then that may explain the VERR_INTNET_FLT_IF_NOT_FOUND error. |
| 27 | | |
| 28 | | As for what event id 12 is... I've no idea. Event Viewer only gives the following for the description: |
| 29 | | |
| 30 | | > The driver detected an internal driver error on \Device\VBoxNetLwf. |
