Failed Windivert installation causes GoodbyeDPI to exit
CAPTCHA
- [x] I understand I could be banned from the repository if I misusing issue section not for posting bugs, but for question or 'broken website' report. / Я понимаю, что меня могут заблокировать в репозитории, если я буду использовать раздел issue не для сообщений об ошибках, а для вопросов или сообщении о «неработающем веб-сайте».
Operating system / операционная система
Windows 8.1 (x64)
Running as service / Запуск программы как сервис
I installed it as a service / Установил как сервис Windows
Describe the bug / Опишите ошибку программы
Hello,
I installed GoodbyeDPI as a service with -9 argument. However, service would fail and stop every 20 seconds. I modified the batch files to log the issue, analyzing which insinuated something wrong with Windivert64.sys so I checked its installation and the output was:
`Checking WinDivert status... [OK] WinDivert.dll found [OK] WinDivert64.sys found [OK] WinDivert driver service exists
SERVICE_NAME: WinDivert TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 2 (0x2) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0
Testing GoodbyeDPI with basic parameters... GoodbyeDPI v0.2.3rc3: Passive DPI blocker and Active DPI circumvention utility https://github.com/ValdikSS/GoodbyeDPI
Block passive: 1 Block QUIC/HTTP3: 0 Fragment HTTP: 2 Fragment persistent HTTP: 2 Fragment HTTPS: 2 Fragment by SNI: 0 Native fragmentation (splitting): 0 Fragments sending in reverse: 0 hoSt: 1 Host no space: 1 Additional space: 0 Mix Host: 0 HTTP AllPorts: 0 HTTP Persistent Nowait: 1 DNS redirect: 0 DNSv6 redirect: 0 Allow missing SNI: 0 Fake requests, TTL: disabled (fixed: 0, auto: 0-0-0, min distance: 0) Fake requests, wrong checksum: 0 Fake requests, wrong SEQ/ACK: 0 Fake requests, custom payloads: 0 Fake requests, resend: 1 Max payload size: 0
Opening filter Error opening filter: 2 The system cannot find the file specified.
The driver files WinDivert32.sys or WinDivert64.sys were not found. Exit code: 1 Press any key to continue . . .`
To get around the issue, I simply copied the Windivert64.sys to System32 directory and the issue resolved. Previous stable version i.e. 0.2.2 did not have this issue. The newest version 0.2.3rc3 has this issue. Please have a look into this if possible.
Thank you for your great work, your help is highly appreciated.
Additional information / Дополнительная информация
No response
Have you solved this problem? The same problem
Have you solved this problem? The same problem
To get around the issue, I simply copied the Windivert64.sys to System32 directory and the issue resolved.