Windows Prefetch RAM: What It Is, How to Enable or Disable It, and How to Free Up More RAM
Windows Prefetch RAM is used to preload frequently used application data so apps launch faster. It stores trace files in C:\Windows\Prefetch and loads that data into standby memory — RAM that Windows releases immediately when active programs need it. On HDD systems, leave Prefetch enabled. On SSD systems with limited RAM, disable SysMain through services.msc can reduce background disk activity. On modern SSDs, both features are largely harmless.
Most users who search for Windows Prefetch RAM fall into one of two camps. The first group sees high RAM usage in Task Manager, blames Prefetch, and wants to turn it off. The second group has read that clearing the Prefetch folder speeds up Windows and wants to know if that is true.

Both groups are working from incomplete information. This Axeetech Windows Prefetch RAM Usage guide explains what Prefetch actually does to your RAM, why the high usage you see in Task Manager is often not a problem, when disabling Prefetch or SysMain genuinely helps, and 10 confirmed methods to free up more RAM that go well beyond the standard SysMain tip.
Also Read: Windows Secure Folder
What is Windows Prefetch RAM and How Does It Use RAM?
Windows Prefetch is a memory management technology introduced in Windows XP. It monitors which applications and system files you launch during startup and regular use. Windows records those patterns in small trace files called .PF files, stored inside the C:\Windows\Prefetch folder. The next time you open one of those applications, Windows reads the matching *.PF file and pre-loads the relevant data from your storage drive into RAM before you even click the icon.
Prefetch operates at two separate levels simultaneously. Application prefetching tracks and preloads frequently launched applications. Boot prefetching tracks the files Windows needs during system startup and pre-stages them to reduce boot time.
How Prefetch uses your RAM:
Prefetch loads data into RAM as standby memory. Standby memory is occupied but not permanently reserved. Windows releases standby memory immediately and automatically whenever any running application requests more RAM. The data is simply evicted from standby and the RAM becomes available. This is why Task Manager can show high memory usage on a healthy system with Prefetch active — the RAM is not wasted, it is cached and instantly reclaimable.
Where to see Windows Prefetch RAM usage in Task Manager:
- Press Ctrl+Shift+Esc to open Task Manager.
- Click Performance in the left panel.
- Click Memory.
- Scroll to the bottom of the Memory section.
- Look at the memory composition bar at the very bottom.
- The “Standby” segment in that bar (shown in light blue) represents the RAM currently occupied by Prefetch and SysMain cached data.
Tip: The Standby number in the Task Manager memory composition bar is the single most useful indicator of Prefetch RAM activity. A large Standby value does not mean your PC has a memory problem. It means Windows has efficiently used otherwise idle RAM to cache app data. The moment any active program requests that memory, Standby drops and the program gets the RAM it needs instantly.
About the Prefetch folder and .PF files:
The C:\Windows\Prefetch folder contains one .PF trace file for each monitored application. Windows also stores a special file named NTOSBOOT-B00DFAAD.pf for the Windows boot prefetch sequence. In Windows 10 and Windows 11, the Prefetch folder can hold up to 1,024 .PF files. Windows manages the folder size automatically and removes old or unused traces without any user action required.
Prefetch vs SuperFetch vs SysMain: What Is the Difference?
Prefetch and SysMain are two separate mechanisms that both use RAM as a cache. Most guides treat them as the same thing. They are not. Disabling one does not disable the other.
| Feature | Original Name | Current Name in Windows 10/11 | How It Works | Where to Control |
|---|---|---|---|---|
| Prefetch | Prefetch | Prefetch (unchanged) | Reads .PF trace files; preloads specific boot and app files from storage into RAM | Registry: EnablePrefetcher DWORD value |
| SuperFetch | SuperFetch | SysMain | Active Windows service; uses behavioral analysis and pattern learning to preload frequently used apps into available RAM proactively | services.msc: SysMain service |

Key distinctions between the two:
Prefetch is passive and file-based. It reads.PF trace files that record a specific sequence of files loaded during past application launches. It does what the trace file says, nothing more. SysMain (formerly SuperFetch) is an active Windows service. It continuously monitors usage patterns, learns which apps you open most often, and proactively moves those apps into available RAM even before you open them. SysMain was renamed from SuperFetch in Windows 10 when Microsoft reorganized the Services list. The function remained identical.
Both features use the same PrefetchParameters registry key for their respective DWORD values. Both contribute to the Standby memory value visible in Task Manager.
Should You Disable Prefetch? (SSD vs HDD Decision)
The correct answer depends entirely on your hardware. Windows 10 and 11 automatically detect SSD storage and adjust Prefetch behavior, but they do not fully disable Prefetch on SSDs.
| Your Setup | EnablePrefetcher Setting | SysMain | Reason |
|---|---|---|---|
| HDD, any RAM amount | 3 (keep default) | Enabled | Prefetch reduces HDD read latency from 200-400ms to near-instant; significant real-world benefit |
| SSD, 8 GB or more RAM | 3 (default is fine) | Enabled or test disabled | SSD reads are already under 0.1ms; Prefetch benefit is minimal but harmless |
| SSD, 4 GB or less RAM | 0 or 1 | Disabled | SysMain competes for RAM that active processes need on constrained systems |
| Any drive, SysMain shows sustained high disk/CPU in Task Manager | Any | Disable SysMain first | SysMain is an active service causing the activity; test disabling before touching Prefetch |
| Windows Server or multi-user systems | 0 or 2 | Disabled | Unpredictable usage patterns make behavioral preloading ineffective; RAM is better reserved for active processes |
| Gaming PC with 16 GB+ RAM and SSD | 3 (default) | Can disable if noticeable | Games manage their own memory; SysMain preloading is redundant; disable only if startup disk activity bothers you |
Warning: Disabling Prefetch and SysMain is NOT a guaranteed performance improvement. On a healthy Windows 11 PC with an SSD and 8 GB or more RAM, both features run quietly with no negative impact. Disabling them purely to “free up RAM” when the system is not under actual memory pressure often makes app launches slightly slower with no measurable benefit anywhere else.
What Does EnablePrefetcher Mean? (Values 0, 1, 2, 3 Explained)
EnablePrefetcher is a DWORD registry value that controls how Prefetch operates. It lives inside the PrefetchParameters registry key alongside EnableSuperfetch.
Registry path (copy this exactly):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters
EnablePrefetcher values:
| Value | Behavior | Best For |
|---|---|---|
| 0 | Prefetch completely disabled | Very low RAM systems (4 GB or less); SSD with write-reduction goal; specific 100% disk usage troubleshooting |
| 1 | Application prefetching only (boot prefetch disabled) | Users who want app-level optimization but not boot-level preloading |
| 2 | Boot prefetching only (app prefetch disabled) | Users where startup speed matters more than per-app launch caching |
| 3 | Both boot and application prefetching (DEFAULT) | All HDD systems; recommended default; this is what every fresh Windows install uses |

The same PrefetchParameters key contains a second DWORD: EnableSuperfetch. This controls SysMain via the registry. It accepts the same values (0 = disabled, 3 = fully enabled). In some Windows builds, this DWORD may be named EnableSysMain instead.
Naming note: In some older Windows versions, the DWORD may appear as EnablePrefetch (without the final “r”). If you do not see EnablePrefetcher in the right pane, look for EnablePrefetch. The function is identical.
For most PCs, leaving EnablePrefetcher at 3 is the correct choice. Change it to 0 only if you are troubleshooting a specific 100% disk usage problem, running an SSD with genuinely limited RAM, or testing performance on a Windows Server environment.
How to Disable Prefetch in Windows 11 (Registry Method)
Changing EnablePrefetcher requires Registry Editor access. Back up the registry before editing: open regedit, go to File > Export, and save a backup file.
- Press Win+R, type regedit, and press Enter.
- Navigate to this exact path in the left panel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters
- In the right pane, find the DWORD value named EnablePrefetcher.
- Double-click EnablePrefetcher to open the edit dialog.
- Change the Value data to 0 to disable Prefetch completely.
- Click OK to save the change.
- Close Registry Editor.
- Restart Windows for the change to take effect.
To re-enable Prefetch, follow the same steps and set the Value data back to 3.
To verify the current EnablePrefetcher value from the Command Prompt:
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters" /v EnablePrefetcher
The output shows the current DWORD value in hexadecimal. 0x3 = value 3 (enabled). 0x0 = value 0 (disabled).
If Windows Update processes are contributing to high disk usage alongside Prefetch activity, the AxeeTech guide on how to fix Windows Update issues easily covers every repair path for update-related disk and performance problems.
How to Disable SysMain (SuperFetch) in Windows 11
SysMain is the active Windows service version of SuperFetch. Disabling it through services.msc is the recommended method because it gives you both immediate control and persistent startup behavior control.
Method 1: Services Manager (Recommended)
- Press Win+R, type services.msc, and press Enter.
- Scroll down the services list to find SysMain.
- Double-click SysMain to open its properties.
- In the Startup type dropdown, select Disabled to prevent SysMain from starting at next boot.
- Click Stop to halt the service immediately.
- Click OK to save the changes.

Method 2: Command Prompt (Administrator)
Stop the service immediately:
sc stop SysMain
Disable the service from starting at boot:
sc config SysMain start= disabled
Note the space after the equals sign in the second command. That spacing is required for the command to execute correctly.
Method 3: Computer Management
Right-click Start > Computer Management > expand Services and Applications in the left panel > click Services > scroll to SysMain > right-click > Properties > change Startup type to Disabled.
To re-enable SysMain:
- Open services.msc.
- Double-click SysMain.
- Set Startup type to Automatic.
- Click Start to run it immediately.
- Click OK.
To verify the current SysMain service state:
sc query SysMain
The output shows STATE: 4 RUNNING (active) or STATE: 1 STOPPED (disabled/stopped).
Warning: Before disabling SysMain, confirm it is actually causing your high RAM or disk usage. Open Task Manager > Performance > Disk. If “Service Host: SysMain” is not among the top disk activity processes, disabling SysMain will not resolve the issue. High disk usage in Windows 11 can equally be caused by Windows Update downloading in the background, Windows Defender scanning, Windows Search rebuilding its index, a failing storage drive, or insufficient free space on the system drive. Run a Windows troubleshooter to identify the actual source before making any changes.
How to Open the Prefetch Folder (And Why Clearing It Usually Helps Nothing)
The Prefetch folder is accessible to any user with administrator permissions.
Method 1: Press Win+R, type prefetch, and press Enter. Windows will ask for administrator permission to open the folder. Click Continue.
Method 2: Open File Explorer and navigate manually to:
C:\Windows\Prefetch
Inside the folder you will see .PF files named after each monitored application. The file NTOSBOOT-B00DFAAD.pf is the Windows boot prefetch trace that records which system files load during startup.
Why you should not regularly clear this folder:
Clearing C:\Windows\Prefetch removes all .PF trace files. Windows regenerates them automatically starting from the next launch of each application, but the first several launches of every application on your system will be noticeably slower until the traces are fully rebuilt. Windows manages the Prefetch folder size automatically with a limit of 1,024 files in Windows 10 and 11. The folder does not grow without bound. It does not need periodic manual clearing.
The advice to clear the Prefetch folder for speed dates from the Windows XP era, where the folder had no automatic size management and could theoretically accumulate excessive files on systems with many applications. That limitation was removed in Windows Vista and has not been a concern on any modern Windows version. Applying that tip to Windows 10 or 11 serves no ongoing maintenance purpose and causes temporary performance regressions every time you do it.
Warning: Clearing the C:\Windows\Prefetch folder is not a maintenance task in Windows 10 or Windows 11. Windows manages the folder automatically and caps it at 1,024 files. Clearing it removes all trace data built up over days or weeks of normal use. Every application on your system will launch more slowly for the next several sessions while Windows rebuilds those traces from scratch. The only valid reason to clear the folder is to troubleshoot a specific startup issue after a major software change.
10 Ways to Free Up More RAM in Windows 11
These 10 methods go well beyond the standard SysMain tip that most guides stop at. Work through them in order: the earlier methods are faster and less disruptive than the later ones.
Method 1: Disable or Stop the SysMain Service
Open services.msc > find SysMain > set Startup type to Disabled > click Stop. This removes the proactive preloading layer immediately. Standby memory in Task Manager will drop on the next restart.
Method 2: Empty Standby RAM with RAMMap (No Reboot Required)
RAMMap is a free tool from Microsoft Sysinternals. Download it at live.sysinternals.com/RAMMap.exe. Open RAMMap, click the Empty menu at the top, and select Empty Standby List. The Standby value in Task Manager drops immediately. This is the fastest way to recover RAM occupied by Prefetch caching without restarting or changing any settings.

Tip: RAMMap from Microsoft Sysinternals lets you clear standby RAM immediately without rebooting. After running Empty Standby List, the Standby number in Task Manager drops within seconds, and that memory is available to any active process. This is useful before launching a RAM-intensive application like a game or video editor when the system shows high Standby usage.
Method 3: Disable Startup Programs
- Press Ctrl+Shift+Esc to open Task Manager.
- Click the Startup apps tab.
- Review every entry listed.
- Right-click any program you do not need running at startup and select Disable.
Each disabled startup program reduces RAM consumption from the first second after login.
Method 4: Adjust Windows Visual Effects for Performance
- Press Win+R, type sysdm.cpl, and press Enter.
- Click the Advanced tab.
- Under Performance, click Settings.
- Select Adjust for best performance.
- Click Apply and OK.
This disables animations, transparency, and visual effects that consume small but consistent amounts of RAM and CPU.
Method 5: Increase Virtual Memory (Page File)
- Open the same Performance Options dialog from Method 4.
- Click the Advanced tab.
- Under Virtual memory, click Change.
- Uncheck Automatically manage paging file size.
- Select Custom size.
- Set Initial size to 1.5 times your physical RAM in megabytes.
- Set Maximum size to 3 times your physical RAM.
- Click Set, then OK, and restart.
Increasing the page file gives Windows more overflow space and reduces the frequency of memory pressure on constrained systems.
Method 6: Disable Windows Search Indexing (If You Rarely Use Search)
Open services.msc > find Windows Search > set Startup type to Disabled > click Stop. Windows Search indexing runs as a background process that consumes both RAM and disk writes. If you primarily use the Start menu to open apps rather than typing searches, disabling this service frees consistent background resources.
Method 7: Run Windows Memory Diagnostic
- Press Win+R, type mdsched.exe, and press Enter.
- Click Restart now and check for problems.
- Windows restarts, runs a memory hardware test, and shows results on the next login.
Before assuming Prefetch or SysMain is causing your high RAM usage, hardware RAM faults can cause apparent memory pressure that software changes will not fix. Windows Memory Diagnostic rules this out without any third-party software.
Method 8: Identify RAM Leaks with Resource Monitor
- Press Win+R, type resmon.exe, and press Enter.
- Click the Memory tab.
- Sort by Commit (KB) column by clicking the column header.
- Watch for any process whose Commit value keeps rising continuously while the system is idle.
A process whose committed memory grows without stopping while you are not actively using it is leaking RAM. Restarting that specific process or application often recovers the lost memory without rebooting the entire system.
Method 9: Close Background Applications in Settings
Go to Settings > Apps in Windows 11. Review installed apps. Select any app you do not use and click Advanced options to restrict its background activity. Some apps continue consuming RAM while running in the background even when you are not using them.
Method 10: Upgrade Physical RAM
For systems with 4 GB or less RAM, every software optimization above provides only marginal relief. Adding more physical RAM is the most effective single action available. SysMain becomes a net performance benefit rather than a drain on systems with 8 GB or more. Most modern motherboards support 16 GB at minimum, and RAM prices in 2026 make a 4 GB to 16 GB upgrade economically accessible for most desktop users.
If your system enters a self-repair cycle during or after applying any of these changes, the AxeeTech guide on what to do when your system is repairing itself explains each phase of the Windows repair process safely.
Diagnostic Commands: Check Prefetch and SysMain Status
Use these commands to verify the current state of Prefetch and SysMain before and after making any changes.
Check SysMain service status:
sc query SysMain
Output STATE: 4 RUNNING = SysMain is active. STATE: 1 STOPPED = SysMain is stopped or disabled.
Check EnablePrefetcher current value:
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters" /v EnablePrefetcher
Check if TRIM is enabled on your SSD:
fsutil behavior query DisableDeleteNotify
Output 0 = TRIM is enabled on your SSD (correct). Output 1 = TRIM is disabled. TRIM ensures the SSD receives notification of deleted blocks so it can optimize write performance. Prefetch write activity on SSDs is less of a concern when TRIM is active.
Important: BIOS Hardware Prefetch is completely separate from Windows Prefetch. Your BIOS or UEFI firmware may include an option labeled Hardware Prefetch or CPU Prefetch in the Advanced CPU settings. That feature controls CPU cache-level prefetching inside the processor itself. It has nothing to do with the C:\Windows\Prefetch folder, .PF trace files, or the SysMain service. Changing BIOS hardware prefetch settings will not affect any of the Windows behaviors described in this guide.
After confirming your Prefetch configuration, if you notice that default Windows apps or file type associations are also behaving unexpectedly after a system optimization pass, the AxeeTech guide on how to change default apps for file types in Windows covers every method for restoring correct Windows app associations.
Frequently Asked Questions
What is Windows Prefetch and what does it do to RAM?
Windows Prefetch monitors which applications and system files you launch regularly and stores trace data as .PF files in C:\Windows\Prefetch. When you open a monitored application, Windows pre-loads the files that application needs from storage into RAM before you click anything. This RAM usage appears as Standby memory in the Task Manager memory composition bar. Standby memory is not permanently committed — Windows releases it immediately when any active process requests more RAM.
Should I disable Prefetch in Windows 11 if I have an SSD?
For most users with an SSD and 8 GB or more RAM, leaving Prefetch at its default value of 3 is the correct choice. The background activity is minimal on modern hardware. If you have an SSD with 4 GB or less RAM and observe sustained high disk or CPU usage tied specifically to SysMain in Task Manager, disabling SysMain through services.msc is worth testing. Changing EnablePrefetcher to 0 via the registry is only necessary if you want to eliminate SSD write operations or troubleshoot a specific 100% disk usage problem.
What is the difference between Prefetch and SysMain?
Prefetch is a passive file-based system that reads .PF trace files and preloads specific data into RAM when you open an application. SysMain (formerly SuperFetch) is an active Windows service that uses behavioral analysis to proactively move frequently used applications into available RAM even before you launch them. Prefetch is controlled through the EnablePrefetcher registry DWORD. SysMain is controlled through services.msc or the sc command. They are separate mechanisms; disabling one does not affect the other.
What does EnablePrefetcher 0 vs 3 mean?
EnablePrefetcher is a DWORD registry value at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters. Value 3 (the default) enables both application and boot prefetching. Value 0 disables Prefetch entirely. Value 1 enables application prefetching only, and value 2 enables boot prefetching only. For HDD systems, keep it at 3. For SSD systems where you want to reduce background write activity, changing it to 0 is safe but provides minimal real-world benefit on modern hardware.
Why is my RAM usage so high in Windows 11?
High RAM usage in Task Manager includes Standby memory from Prefetch and SysMain. Standby memory is not wasted — it is cached data Windows releases instantly for active processes. To see the breakdown, open Task Manager > Performance > Memory and look at the memory composition bar at the bottom. If the Standby segment is large but In Use is moderate, the system is healthy. If In Use is consistently near your total RAM even when idle, use resmon.exe (Resource Monitor) to identify which processes are consuming the most committed memory and whether any are growing without stopping.
How do I disable SysMain in Windows 11?
Open services.msc (Win+R > services.msc > Enter), scroll to SysMain, double-click it, set Startup type to Disabled, click Stop, then click OK. From Command Prompt as administrator, the equivalent commands are sc stop SysMain to stop it immediately and sc config SysMain start= disabled to prevent it starting at boot. To re-enable SysMain, return to services.msc, set Startup type to Automatic, and click Start.
Is it safe to clear the Prefetch folder in Windows 11?
Clearing C:\Windows\Prefetch is safe in that it will not corrupt Windows. However, it provides no ongoing benefit. Windows automatically manages the folder and caps it at 1,024 files. After clearing the folder, every application on your system will launch noticeably more slowly for several sessions while Windows rebuilds all the .PF trace files from scratch. The advice to clear Prefetch for performance dates from Windows XP and does not apply to Windows 10 or 11.
How do I free up RAM in Windows 11 without restarting?
Download RAMMap from live.sysinternals.com/RAMMap.exe, open it, click the Empty menu, and select Empty Standby List. This immediately releases all standby RAM held by Prefetch and SysMain caching without rebooting. The Standby value in Task Manager drops within seconds. You can also stop the SysMain service immediately with the command sc stop SysMain in an elevated Command Prompt, which halts new preloading activity without a restart.
Does Prefetch cause 100% disk usage in Windows?
Prefetch itself rarely causes sustained 100% disk usage. SysMain (the active service component) can cause high disk activity on older HDD systems or systems under memory pressure immediately after startup. If Task Manager > Performance > Disk shows Service Host: SysMain as the top disk consumer for more than 10 to 15 minutes after boot, disabling SysMain is a valid troubleshooting step. However, 100% disk usage in Windows 11 is more commonly caused by Windows Update downloading in the background, Windows Defender performing a scheduled scan, or a storage drive approaching failure.
How do I enable Prefetch if I accidentally disabled it?
Open Registry Editor (Win+R > regedit > Enter), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters, double-click EnablePrefetcher, and set the value to 3. Click OK and restart Windows. For SysMain, open services.msc, find SysMain, double-click it, set Startup type to Automatic, click Start, and click OK. Both changes take full effect after a restart.
What is RAMMap and how does it help with Prefetch?
RAMMap is a free memory analysis tool from Microsoft Sysinternals, available at live.sysinternals.com. It provides a detailed breakdown of Windows RAM usage including the Standby list that Prefetch and SysMain populate. The Empty Standby List function under RAMMap’s Empty menu clears all standby cached data immediately without rebooting. This is the most direct tool for releasing Prefetch-held RAM on demand, and it is not mentioned in any of the major competing guides for this topic.
Is a freelance tech writer based in the East Continent, is quite fascinated by modern-day gadgets, smartphones, and all the hype and buzz about modern technology on the Internet. Besides this a part-time photographer and love to travel and explore. Follow me on. Twitter, Facebook Or Simply Contact Here. Or Email: info@axeetech.com
