Closed strictlymike closed 6 years ago
This ticket was logged for documentation purposes and will be closed.
If you're also trying to run fakenet on windows 10 v1607+ and have secure boot enabled, you'll also have difficulties loading the driver due to requirement changes.
When you start FakeNet-NG, you see the following error:
This is an issue relating to WinDivert (as opposed to FakeNet-NG), but as it impedes using FakeNet-NG, I am documenting it here.
It appears that new Windows driver signing practices are at issue here. See this comment from the WinDivert Driver Signing discussion. For me, it was sufficient to bring my VM out of isolation, run Windows Update, and then retry. The updated VM ran FakeNet-NG without any Windows driver signing error.
Thanks to @garsim for noticing this as well, and @tankbusta for noting the relevant conversation about the issue including the work-around.