Share via

Hibernation & Resume: svchost.exe: DNSCache

Anonymous
2025-03-09T10:55:25+00:00

Using custom content in the HOST file, svchost has always populated the DNSCache at every cold boot, takes 15 minutes to complete, which is fine. For some reason, possibly as a result of 24H2, svchost runs this now at every resume after hibernation. Nothing stands out as to the reason why.

Delivery Optimization is now turned off, and Network Discovery also now turned off for public networks if that is a thing. Running a custom Power Plan, nothing in there to indicate a change in resume boot. Windows Resume Application in BCD is configured to what it is always was. Windows Update is working well, KB5052093 was successfully installed four days ago. There are events 7011 & 7046, they are not new however.

Also tried:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

Rebooted, no change.

Any clues, or can this behaviour (if intentional), be changed through Policy settings?

Thanks.

Windows for home | Windows 11 | Sleep and Power on, off

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2025-03-09T12:44:15+00:00

Hi there,

It looks like the behavior you’re experiencing with the DNS Client service (DNSCache) repopulating on resume from hibernation is now occurring after the 24H2 update and isn’t something that can be directly controlled through any Group Policy or registry setting.

In previous builds the DNS cache was refreshed only on a cold boot, and this change appears to be an intentional modification by Microsoft.

One potential workaround would be to set up a scheduled task that stops the DNS Client service upon resume, though this isn’t recommended because disabling DNS caching can negatively affect name resolution and overall system performance.

The best approach at this time is to provide feedback via the Windows Feedback Hub so Microsoft can review whether this change is impacting users significantly and consider a fix in a future update.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful