[FIXED] Delivery optimization is eating up memory on Windows 11

Question

Delivery optimization is eating up memory to the point when everything crashes. HELP!

SYSTEM

Edition Windows 11 Home

Version 22H2

Installed on ‎21/‎09/‎2022

OS build 22621.1413

Experience Windows Feature Experience Pack 1000.22639.1000.0

HARDWARE

Processor Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz

Installed RAM 16.0 GB (15.9 GB usable)

Device ID 751751EA-B282-4799-8914-724BAC381FE5

Product ID 00325-81438-56865-AAOEM

System type 64-bit operating system, x64-based processor

ISSUE DESCRIPTION

The issue is with the process

Service Host: Network Service -> Delivery Optimization

I have noticed an issue with unstable browsers - Chrome and Edge.

After a few hours of work, both become unstable. Constant crashes, etc.

I was not sure what is going on until one tab displayed the following:

I started digging and it turned out the Delivery Optimization process is constantly running (using bandwidth) and taking up more and more RAM, up to a point where nothing works.

I have turned off Delivery Optimization in the system settings:

I have performed a Disk clean up twice (including System files)

I have killed the process in Task Manager (many times), restarted the system (many times)...

Nothing works :-(

The process comes back to life on its own and is doing exactly the same thing.

As you can imagine, in only a few hours the 16GB of RAM will be full and the apps will start to crash.

This is impossible to live with.

Answer 1

To fully stop Delivery Optiization, here are the steps:

Click your Start Button, type regedit and hit Enter to open the Registry Editor.

Click View and make sure 'Address Bar' is turned on.

Paste this into the Address Bar at the top and hit Enter.

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DoSvc

Double click 'Start' in the right hand pane, then set its Value Data to 4 and click OK

Close the Registry editor and restart (not shut down) your PC

Answer 2

Group Policy is only included in Pro edition.

Try taking ownership of the Registry key to see if it will settle down:

https://www.maketecheasier.com/full-ownership-w...

I think it's prudent to consider possible infection, especially since it is force enabling a communication channel an invader could use. I would do this thorough disinfection procedure that finds and removes any virus wherever it hides, then repairs any damaged system files: https://answers.microsoft.com/en-us/windows/for...

Let me know if you have any questions or I can help performing any of the above steps. If you'll post back detailed results on each step in each tutorial, it will help me determine what else needs to be tried.

____________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 3

Sounds good. Hopefully it goes away and you never see it again.

MVP's spotted this as trouble when it first showed up in Win10 beta. A torrent for Windows update - what could go wrong?! We had an ally in the long-time head of MS Support who helped keep it off by default, but he retired several years ago so I'd watch it's default.

Answer 4

Hi Greg,

Thank you so much for taking the time to reply.

One additional question - if one of the above works, what outcome should is see?

Delivery Optimization is completely off and not visible in the Task Manager Processes or it will be there, just not working so "aggressively"?

So far I have gone through link one - Fix- Modify the registry.

For the moment I thought it worked.

The process was visible, but not eating memory so fast as previously, however after a few minutes everything went back to as it was.

I can see that the registry value went back from 4 that I set to 3, which was there before :-(.

However, again after a few minutes, it seems it can manage itself properly.

After reaching up to about 250mb it seems to be gone now...

I'll keep monitoring Task Manager if that had indeed fixed the issue.