Both, the Hard drive and RAM play a major role in performing any operation on a computer. Every task or a process that takes place in a computer requires some RAM storage as well as Hard drive storage to be executed. But at times, when you are copying files from one location to another, you may receive one of the following messages:
- Out of memory or system resources, Close some windows or programs and try again.
- There is not enough memory to complete this operation – copying files.
This error is caused due to the Desktop Heap limitation when there is not enough memory to complete this operation while copying files. Today, we will be checking out the potential fixes to increase this limit and ultimately fix this error on Windows 10.
Well, close all open windows and programs and try to copy again and see if that helps. If it does not then follow our suggestion.
Out of Memory error while copying files
Before you begin, you might want to create a System Restore point first, as it can help you to reverse undesirable or unwanted changes.
We will be using the Registry Editor to fix this issue. Run regedit and hit Enter. Once Registry Editor opens, navigate to the following key-
Double click on the DWORD named Windows to modify it.
In the Value Data field, you need to change the values for SharedSection.
It will be in the format of,
You need to change the value of bbbb and cccc.
- In case that you are using an x86 operating system, set the value for bbbb to 12288 and the value for cccc to 1024.
- In case that you are using an x64 operating system, set the value for bbbb to 20480 and the value for cccc to 1024.
Exit the Registry Editor and reboot your computer for the changes to take effect.
The bbbb value in the SharedSection registry is the size of the desktop heap for each interactive window station, whereas the cccc section of the SharedSection value is the size of the desktop heap for each non-interactive window station. You should also know that setting the value of bbbb to more than 20480 KB is not at all recommended.
Is your issue fixed now?