Auto Optimize doesn't work

[finegorko]

Checklist

• I have used the search function to see if someone else has submitted the same bug report.
• I will describe the problem in as much detail as possible.

App version

Latest

Windows version

W11 23H2

Steps To Reproduce

I have setting Auto Optimize ON

Current Behavior

Auto Optimize doesn't work properly, it's doesn't trigger when need

Expected Behavior

No response

Anything else?

No response

[IgorMundstein]

Let's test it.

1. Set this config

2. Let's check the logs
3. After 5 minutes, you should have a log entry like this

4. After 1 hour, you should have a second log entry like this

Can you please provide more details?

[finegorko]

virt memory is 8% free and autooptimize doesnt work

[finegorko]

and how to add app to startup? i add shortcut to shell:startup but doesn't work

[IgorMundstein]

Ah, I see the confusion. The auto-free memory is applicable to physical memory only. I will update the text to be clearer.

Check the setting "Run on startup." It will create a Windows task. Any other methods, like shortcuts or the Windows registry, don't work as expected because the app needs administrator privileges to run. That's the only known way so far.

[nnyeh]

and how to add app to startup? i add shortcut to shell:startup but doesn't work

I personally struggled with trying to get it to launch on startup as well even with "Run on startup" enabled, but a solution that worked for me was to create a .bat file inside the startup folder with the following code:

@echo off
start "" "[location of the file]\WinMemoryCleaner.exe"
exit

I wanted the app to start minimized with the icon visible in the taskbar and that did the trick.

[IgorMundstein]

@nnyeh @finegorko

Can you please open the Windows Task Scheduler and see if the task is created when you flag "run on startup"? If yes, can you close the app if it's open, run the task, and see if the app opens? If it doesn't, the Task Scheduler will show an error message. Reply with a screenshot of the error. That will help identify what's going on.

[nnyeh]

Can you please open the Windows Task Scheduler and see if the task is created when you flag "run on startup"? If yes, can you close the app if it's open, run the task, and see if the app opens? If it doesn't, the Task Scheduler will show an error message. Reply with a screenshot of the error. That will help identify what's going on.

The task is not created when clicking it nor do I get an error message. I have tried creating one manually, but that didn't really work either. If I recall correctly, it might have launched it but it was hidden away in processes and needed to be closed from the task manager to be able to open it. The way I did it was the only one that worked for me for some reason.

[IgorMundstein]

Can you please open the Windows Task Scheduler and see if the task is created when you flag "run on startup"? If yes, can you close the app if it's open, run the task, and see if the app opens? If it doesn't, the Task Scheduler will show an error message. Reply with a screenshot of the error. That will help identify what's going on.

The task is not created when clicking it nor do I get an error message. I have tried creating one manually, but that didn't really work either. If I recall correctly, it might have launched it but it was hidden away in processes and needed to be closed from the task manager to be able to open it. The way I did it was the only one that worked for me for some reason.

Okay. Let's see if there is a log with an error when the task is trying to be created.

Can you check the logs in Windows Event Viewer?

https://github.com/IgorMundstein/WinMemoryCleaner?tab=readme-ov-file#-logs

It might have a message like "An unexpected error occurred while managing the startup task for ..."

[nnyeh]

Okay. Let's see if there is a log with an error when the task is trying to be created.

Can you check the logs in Windows Event Viewer?

https://github.com/IgorMundstein/WinMemoryCleaner?tab=readme-ov-file#-logs

It might have a message like "An unexpected error occurred while managing the startup task for ..."

Nah I have only the normal "Memory optimized" ones. To be clear, I have everything working like I want it to, but I suppose you want to try and understand why it wasn't working for me in the first place.

[IgorMundstein]

@nnyeh

Please download and test this beta version: WinMemoryCleaner-beta.zip

It should fix the run on startup issue.

After enabling this setting

You should see a scheduled task created as follows:

You can close the app and start the task by right-clicking on it and selecting "Run". If the app opens, it's a good sign. It should open automatically the next time you restart and log in to the system.

Please, let me know the results.

[finegorko]

igor can u describe what is low priority or give me "optimized setings" pls, i use ur app because im run 10+ .exe of world of warcraft and wow has memory leak and ur app very useful

[IgorMundstein]

igor can u describe what is low priority or give me "optimized setings" pls, i use ur app because im run 10+ .exe of world of warcraft and wow has memory leak and ur app very useful

Sure. It's more related to the CPU usage and processing power.

Here is a simple way to think about what the "Run on low priority" setting does.

Imagine your computer's attention (its processing power) is like a cashier at a busy store.

• Normally, all your open applications are in the same line, waiting for the cashier's attention. The cashier tries to serve everyone fairly, switching between them quickly so no one waits too long.

• When you check "Run on low priority", you're telling WinMemoryCleaner to be extra polite. It steps out of the main line and says, "You go first!" to all your other applications.

What This Means for You

• Your computer stays fast and smooth: While the memory cleanup is happening, your main tasks—like browsing the web, playing a game, or writing a document—will always get the computer's full attention first. You're less likely to notice any stuttering or slowdowns.

• The cleanup might take a little longer: Because WinMemoryCleaner is politely waiting its turn, the optimization process itself might take a few extra seconds to complete.

In short, enabling "Run on low priority" is a great way to ensure that the app does its job quietly in the background without interrupting your work, making for a much smoother experience.

Recommended Settings for Your WoW

Given that WoW has memory leaks the goal is to create a stable, automated setup that regularly cleans up the memory without crashing your game clients.

Here are the "optimized settings" I recommend for you:

1. Protect World of Warcraft First (Most Important Step!)

   • In the "Processes excluded from optimization" section, find Wow.exe (or whatever the game's process is named) in the dropdown list and click the + button to add it to the exclusion list.
   • This is the most critical step. It tells the cleaner never to touch your active game clients, which will prevent them from crashing.

2. Set Up a Safe, Automated Cleanup

   • Memory Areas:
     • UNCHECK Working set. This is the aggressive option that can cause active programs to crash. By excluding WoW in step 1 and disabling this for automated cleanups, you are double-protecting your games.
     • Leave all other memory areas checked. These are very safe to clean.
   • Auto Optimization:
     • To combat the memory leaks, set it to run on a schedule. Every 1h or Every 2h is a good starting point. This will regularly clear out the standby memory and other caches without touching the game itself.
   • General Settings:
     • Check Run on low priority. As we discussed, this is perfect for your use case.
     • I also suggest checking Run on startup, Start minimized, and Close to the notification area so the app just runs quietly in the background without you having to think about it.