"Scan Error: Thread 0: Please fill something in 100" (often accompanied by code 100) typically occurs when Cheat Engine
is unable to correctly initialize or write its temporary scan files to your storage drive Primary Causes and Solutions Insufficient Disk Space
: This is a leading cause, especially when performing "Unknown Initial Value" or "All" type scans on modern games.
: Ensure the drive holding your scan results (usually your system drive's temporary folder) has at least 20GB to 80GB of free space. Change Scan Location Settings > Scan Settings
and set a custom location for scan results on a drive with more space. Permissions and Administrative Rights
: Cheat Engine may lack the necessary authority to read the game's memory or write its own temporary data. : Always run Cheat Engine as an Administrator Check Folder Permissions
: Ensure the Cheat Engine installation folder has full read/write permissions for your user account. Antivirus Interference
: Security software like Comodo or Windows Defender can block Cheat Engine from accessing other processes or creating temporary files.
: Temporarily disable your antivirus or add an exception for the Cheat Engine executable and its temporary file folder. Incorrect Scan Settings
: In some cases, specific scan options can trigger thread errors depending on the game engine or system architecture. Settings > Scan Settings , try toggling the MEM_MAPPED checkbox. Some users also report success by disabling 32-bit vs. 64-bit Incompatibility "Scan Error: Thread 0: Please fill something in
: Using the 32-bit version of Cheat Engine on a 64-bit process (or vice-versa) can cause memory access violations. : Use the 64-bit executable ( cheatengine-x86_64.exe ) for modern 64-bit games. custom path for your scan files to avoid future disk space errors? View topic - Scan error - Cheat Engine
It looks like you're encountering a specific Cheat Engine error:
Thread 0: Please fill something in (100)
This usually appears when you try to run a scan but haven't entered a value to search for.
The most frequent cause of this error is extremely simple: You did not type a number into the "Value" box before clicking "First Scan."
Cheat Engine requires a reference point to know what to look for in the computer's memory.
Please Fill Something In.100, 5000, 0) and then click "First Scan."Ctrl+F for First Scan without focusing the Value field can cause this.99,999 with a comma will fail. Use 99999.Sometimes, an old or corrupt cheatengine-i386.exe configuration file causes the value input field to not register keystrokes properly. You type a number, but internally CE sees an empty string.
| Action | Why it helps | |--------|---------------| | Always double-check the Value field before clicking First Scan or Next Scan. | Prevents the blank input error. | | Use Unknown Initial Value correctly – only for first scan, with blank Value. | Avoids misusing the feature. | | Clear Value field when doing "Increased/Decreased" scans – but only after an Unknown initial scan. | Prevents confusion. | | Watch the status bar – Cheat Engine often shows a yellow hint before you click. | Early warning. |
100 if you know the health is 100).If the error persists, disable any antivirus temporarily (false positive), or try Cheat Engine 7.4/7.5 (latest stable).
Final note: The exact phrase "Please fill something in 100" is not a standard Cheat Engine error string — it may be from an older translation, a modified version, or even a joke/meme. But the underlying issue almost always points to an empty or invalid scan input or a thread initialization failure. The Error Logic: You clicked "Scan," but the
If you’re seeing this in a custom script or table, make sure the script’s aobScan or value parameters are correctly filled with a placeholder like 100 where required.
The glow of the monitor was the only thing keeping Elias awake in the basement. On the screen, Age of Ruin—a notoriously difficult RPG—was mocking him. He’d been stuck on the final boss for three days.
Desperation led him to a dusty corner of the internet. He downloaded a legacy build of Cheat Engine, one that looked like it hadn't been updated since the dial-up era. He opened the process, targeted the game, and prepared to give himself infinite health. He typed "999" into the value box and hit First Scan.
The progress bar didn’t move. Instead, a window popped up with an error Elias had never seen in years of tinkering:
"Cheat Engine Scan Error: Thread 0. Please Fill Something In. 100." "Fill something in?" Elias muttered. "I did."
He tried again. Same error. He tried hex codes, floating points, even a simple search for his gold count. Each time, the box reappeared, the "100" at the end blinking like a countdown.
Suddenly, the game audio cut out. The boss on the screen—a towering, faceless knight—stopped its idle animation. It turned its head, not toward Elias’s character, but toward the "camera." The error box changed.
"Cheat Engine Scan Error: Thread 0. Please Fill Something In. 99."
The number was dropping. Elias reached for the power button, but his hand froze. He realized the "Value" box in the scan settings was no longer empty. It was scrolling text in real-time, pulling data from somewhere it shouldn't have access to. Heart Rate: 105 BPMRoom Temperature: 68°FOxygen Level: 21% The "100" wasn't a countdown of time. It was a percentage. a modified version
"Cheat Engine Scan Error: Thread 0. Please Fill Something In. 85."
The air in the basement grew thin. Elias felt a phantom pressure on his chest, like a vacuum was starting to pull the breath from his lungs. The game world began to bleed; the textures of the basement walls started to pixelate and tear, revealing a void of green code beneath the drywall.
The software wasn't scanning the game's memory. It was scanning his. Thread 0 wasn't a processor instruction; it was the biological "Main Thread"—him.
"Cheat Engine Scan Error: Thread 0. Please Fill Something In. 50."
Elias couldn't move. His vision started to strobe in 8-bit colors. He realized what the error meant. The scan had found a "null value" in his own reality, a hole where his physical existence used to be. To complete the scan, it needed data to fill the void. It was consuming his surroundings to balance the equation.
With a shaking hand, Elias grabbed a half-empty soda can from his desk and smashed it against the keyboard. The keys jammed. He didn't type a number. He typed a plea. STOP.
The screen flickered violently. The boss in the game screamed—a sound of grinding metal and distorted static. "Scan Complete: 1 Value Found."
The basement snapped back into focus. The oxygen rushed back into Elias's lungs so hard he fell off his chair. The monitor was black.
He never played Age of Ruin again. He deleted the software and threw the hard drive into the trash. But sometimes, when he’s lying in bed and the room is perfectly quiet, he feels a slight lag in his own pulse. And in the corner of his vision, a small, white box appears for a split second: "New Scan? (Y/N)"
| Cause | Explanation | |-------|-------------| | Invalid data type mismatch | You selected "String" as scan type but typed a number like 100, or vice versa. | | Scan type "Unknown initial value" but no follow-up | This error rarely appears with "Unknown" scans, but can if you then click "Next Scan" without entering a changed/exact value. | | Corrupted Cheat Engine settings | In rare cases, the CE settings file (userdefined.txt) or the registry entry can cause false validation errors. | | Access violation deep in memory | Very rare – the error would mention "Access Violation" not (100). |