Somehow it broken Windows native network layer stacks

[skshpr]

Operating system / операционная система

Windows 11 22H2

Running as service / Запуск программы как сервис

I run it as a regular program / Запускаю программу обычным образом

Describe the bug / Опишите ошибку программы

With not often use it broken native windows network layer stack somehow so created earlier VPN connection (win native l2tp) started working very slow and it begin works well when gdpi start to work. Also same scenario thing happens when trying to run any simple tool from actual version of windivert (flowtrack).
Resetting all TCP, network settings - doesn't' help.
Removing VPN settings - doesn't' help.
Removing all network devices with drivers, and it's further reinstalling - doesn't help
Trying to kill \ uninstall windivert via windivertctl.exe - doesn't help.

Don't want to reinstall win. It will be last mile.

Summary:
Ethernet connection works well without VPN and GDPI.
When running VPN, main Ethernet traffic have full speed, but VPN connection is 20 times slower.
When running VPN with windivert, main Ethernet traffic is 80% of full speed, VPN connection run at full speed.
If switching from Ethernet to WiFi adapter so all works well for main traffic and VPN tho.

Will appreciate any suggestion to dig in...

Additional information / Дополнительная информация

No response

[r4sas]

Better to ask on WinDivert: https://github.com/basil00/Divert. GDPI works using it on network layer.

[skshpr]

Will try. TU 73

[ValdikSS]

Are you sure this is not because of automatic network driver updates, or something similar?
Which network card do you have? Try disabling all offloading options in the driver configuration first.

[skshpr]

Hi! I'm only sure that it was caused not by driver updates but it may affected by generic windows update which I also tried to uninstall without any desired result. There are 2 integrated Ethernet adapters (1gbps from Intel and 2,5 gbps from realtek) and 1 wireless. Will try to disable options you've mentioned. Thanks!

[skshpr]

Hey guys, sorry for bothering you but seems it was recent fuc...up update from Microsoft.
Confirming:
Link 1
Link 2
And solution that 100% works well (and @ValdikSS you pointed in right a place)
Link
In my case problematic update couldn't be uninstalled.