The new 7Zip version incorrectly blocks operations. My system is a virtual machine with dynamic memory. When idle, the system memory drops as low as 2GB - but the host has 8TB of RAM and the VM can use all of it.
7Zip incorrectly detects the RAM before compression starts and wrongly assumes there is not enough.
How do I bypass this check? My system can use all 8TB RAM.
Gonna have to agree with this post.
Needs a "Try Anyway" button or an option in settings to ignore completely.
When I compress (with the old version that lets you), I usually start at the bottom, then work my way up as it fails.
I want the OPTION to continue to do so.
As a test on my old system I set it to max 1536, it compressed fine, latest version wont let me go over 384
Last edit: Hammerfest 2021-09-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For anyone else who has been having this problem too like @Hammerfest - here is how to bypass this dialog permanently:
Open the 7zG.exe in any hex editor and search for this string of bytes (there is only 1 occurance):
CF E8 56 F0 FF FF 48 8B F0 41 3A DE 0F 84 B6
And replace the last 3 bytes to look like this:
CF E8 56 F0 FF FF 48 8B F0 41 3A DE E9 B7 00
You will never see that dialog again. Since there is no authenticode signature or anything else, this will not break anything. Obviously, this is specfic to the 21.03 beta version only.
Last edit: Supercilious Dude 2021-09-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For reference, on same system with the limitation, compressed file is 390MB, without it, 370MB.
Ergo, ABSOLUTE blocking should NOT be a thing, a simple
"Hey it LOOKS like you wont have enough RAM and the compression job will fail, we recommend setting the dictionary size lower!
Continue if you wish to possibly waste your time if there's truly not enough memory to complete!"
Less wordy if you want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"large memory pages" option can provide better speed.
But it doesn't allow to use settings with big memory usage that are larger than available RAM size.
"large memory pages" option just sets fast mode for existing memory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
The new 7Zip version incorrectly blocks operations. My system is a virtual machine with dynamic memory. When idle, the system memory drops as low as 2GB - but the host has 8TB of RAM and the VM can use all of it.
7Zip incorrectly detects the RAM before compression starts and wrongly assumes there is not enough.
How do I bypass this check? My system can use all 8TB RAM.
Please show the info about system and dynamic memory.
What hardware is 8 TB RAM?
Hi Igor,
It is a hyper-v virtual machine with dynamic memory enabled. Running Server 2019 on the host and Windows 10 v1809 (Build 10.0.17763) on the VM.
You can read more about dynamic memory here:
https://www.fastvue.co/tmgreporter/blog/understanding-hyper-v-dynamic-memory-dynamic-ram/
Essentially, the virtual machine does not "see" the memory until it actually allocates it.
An HPE ProLiant DL385 Gen10 Plus server with a pair of EPYC 7513 CPUs.
I was using 7Zip to backup old virtual machines before migrating from hyper-v to VMware. I downgraded to the old version due to this problem for now.
Gonna have to agree with this post.
Needs a "Try Anyway" button or an option in settings to ignore completely.
When I compress (with the old version that lets you), I usually start at the bottom, then work my way up as it fails.
I want the OPTION to continue to do so.
As a test on my old system I set it to max 1536, it compressed fine, latest version wont let me go over 384
Last edit: Hammerfest 2021-09-15
For anyone else who has been having this problem too like @Hammerfest - here is how to bypass this dialog permanently:
Open the 7zG.exe in any hex editor and search for this string of bytes (there is only 1 occurance):
CF E8 56 F0 FF FF 48 8B F0 41 3A DE 0F 84 B6
And replace the last 3 bytes to look like this:
CF E8 56 F0 FF FF 48 8B F0 41 3A DE E9 B7 00
You will never see that dialog again. Since there is no authenticode signature or anything else, this will not break anything. Obviously, this is specfic to the 21.03 beta version only.
Last edit: Supercilious Dude 2021-09-18
Much appreciated.
For reference, on same system with the limitation, compressed file is 390MB, without it, 370MB.
Ergo, ABSOLUTE blocking should NOT be a thing, a simple
"Hey it LOOKS like you wont have enough RAM and the compression job will fail, we recommend setting the dictionary size lower!
Continue if you wish to possibly waste your time if there's truly not enough memory to complete!"
Less wordy if you want.
I have this error, as well on Win64, 32GB RAM.
Please fix it?
I am trying an older version.
Last edit: BrendaEM 2022-05-22
Change options to default values or change "Memory usage" option.
The previous W64 release is not broken: 7z2106-x64.exe
Guys,
still in 7zip v23.0.1 (x64)
Change the options to default.
Big memory usage can hang your system.
To enable big memory, go to Options -> Settings tab.
Check "Use large memory pages" (aka Enable large memory pages in English UK made myself).
If there is problem, disable it.
Last edit: PopuriO2 2023-10-21
"large memory pages" option can provide better speed.
But it doesn't allow to use settings with big memory usage that are larger than available RAM size.
"large memory pages" option just sets fast mode for existing memory.
the option "large memory pages" would be grayed out if the RAM size is running low (e.g: 256 MB or 512 MB).
2 or 4 GB would works fine, but I don't think for larger RAM size (depending how much according on the Windows system information).