KB5022913 some 20hr later DNS just stopped.

[Legacy1]

Not sure if its just a one off but my PC just stopped allowing DNS out ICMP , ARP and DHCP was fine, in the end I rebooted the PC and it all started working again weird.

[#2]

Did you download or install any program before this problem started?
Check Windows Update history and there might be related update (for example related to network driver).

[#3]

Their was a ASIX - Net – 2.20.9.0 (USB to 1Gb) update but thats not the NIC I'm using for internet which is a Marvell AQtion 10Gbit Network Adapter is my main and I have many VLANs by Hyper-V on Intel I225-V with a backup 4G

[#4]

I suggest have a look at log files in the Event Viewer , so you might find some clues there. Sometimes, you will observe this behavior if a service stop responding.

[#5]

Can't find anything in logs before I did a reboot as to what caused it

[#6]

Was there any other device connected that time?
If yes, did you observed the same behavior?

[#7]

If you mean could a access the internet on another device the answer is yes

[#8]

happened again! tried ipconfig /flushdns but still ended up rebooting

[#9]

Check for update for your network driver.
Try open start and search for feedback and open the Feedback Hub app and report this issue.

[#10]

Yes driver is upto date I have reset the Winsock and done my VLANs so I see what happens.

As for the Feedback Hub app and report this issue that never helps.

[#11]

Thinking it some weird driver issue with Marvell on 3.1.7 as I have another system on 3.1.3 without problem so have rolled back

[#12]

Thank you for sharing.
Have you tried performing Clean Boot and see if the problem persists?

[#13]

I did a reboot and I'm just waiting to see if it happens again or I be doing a reinstall

[#14]

Before reinstalling Windows, try Clean Boot and share the result.

[#15]

By Clean Boot you mean a shut down and power up? As said I did a reboot or is that not enough?

[#16]

As if this was not enough MS decided let push Marvell on 3.1.7 out to everyone! Was not a optional driver so now I have to roll back to 3.1.3

[#17]

Does that solve the problem?

[#18]

It can take about a week when it happens so I let you know in 7 days

[#19]

No worry, please observe the behavior and let us know about the result.

[#20]

Been stable for a week so the problem must be Marvell on 3.1.7 causing the problem.