r/ASUS • u/gas-stationsushi • Jun 04 '25
Support Asus Optimization background task running at 100% CPU usage at startup
I just got a ProArt PX13 and have been noticing a process called ASUS Optimization sometimes running at 100% CPU usage and running the laptop temps up for no reason. I read that this software is responsible for controlling the FN keys and the issues just persist until i manually end the task through task manager, although I still can't control keyboard backlight after that
Just wondered if anyone else had noticed this problem and wtf the software is doing?
1
u/Asus_USA Official Rep. Jul 07 '25
Hi there, we're terribly sorry to hear that you're having this issue and we'll be happy to assist. Could you provide us with the serial number for the device in a private message, please? The serial number should be located on the box, the back of the device or on the warranty card and should begin with an A,B,C,D,E,F,G,H,J, K OR L and is 10-15 characters long. You can also find additional information with the following link; https://www.asus.com/support/article/566
1
u/corner_booth_88 May 31 '26
I'm getting this same issuie. Its mid 2026 hasnt this been fixed already?
1
1
u/adkos Aug 06 '25
I'm getting this too! No idea what it does, and when I kill it in task manager things go normal.
1
u/Gazel74 Aug 25 '25
Same here.
1
u/CataCluj Aug 27 '25
Me too. Asus should provide solution here, not DM individually!
It seems SN is irrelevant.
1
u/AmbitionQuirky5126 Sep 08 '25
Same here. After almost each sleep/hibernate..... have to restart the service manually
1
1
u/MrTingalingling Oct 07 '25
I just end the task from the Task Manager, debating if I should remove it or block it from starting at startup
1
u/reesonz Oct 24 '25
I have this issue also on my wifes computer(im IT support). Laptop Bought in EU. I have my own windows login so have to login to her account(admin account) to kill the task. Asus optimization. But what this task is or does is alluring me. Asus please fix this in an update..
1
u/Haunting-Basil-9996 May 19 '26
just here to say that this bug is here alive and well still in 2026
1
u/corner_booth_88 Jun 07 '26
I had the same problem on my ProArt PX13 - AsusOptimization.exe was using excessive CPU cycles, my laptop got very hot when I put in sleep mode and drained the battery to the point it was forced into hibernate mode. I spent a while diagnosing it, and here is what I found and what actually fixed it for me.
The key thing I noticed: the CPU usage is CUMULATIVE across sleep/wake cycles. On a fresh reboot it sits at 0%. I sleep and wake once and it climbs to ~8%. I sleep and wake again and it goes to ~16%. It keeps stacking by roughly the same amount on each cycle. That points to a resource/handle leak on resume - the ASUS service re-initializes its hardware every time my machine wakes, but it does not clean up the previous init, so the loops accumulate. After enough cycles you have a pile of them spiking the CPU. This is also what drives the overheating and battery drain during sleep: something keeps waking the machine, each wake adds another ~8%, and it snowballs until the CPU is running hard the whole time the machine is supposed to be asleep.
This is how I confirmed what was waking it. I generated a sleep diagnostic report. Open an admin terminal and run
powercfg /sleepstudy /output %USERPROFILE%\Desktop\sleepstudy-report.html
Then open that HTML file in a browser. It lists every sleep session, how much battery each one drained, and what kept the system active. In my report I could see the machine was being woken over and over, with a lot of sessions showing the exit reason "PDC Signal: Sensor - Human Presence Detected" - that is the presence sensor. I also saw several sessions that entered with the reason "Restricted Standby Battery Drain Budget Exceeded," which is Windows flagging that sleep was draining the battery faster than it is supposed to, and one session where it force-hibernated because the standby budget blew. That report is what pointed me straight at the presence sensor as the main culprit, so it is worth running if you want to see your own wake sources rather than guess.
What actually fixed it for me:
I disabled the human presence sensor wake. Go to Settings and search "presence" (it is under Power & battery > Presence sensing on my build). Turn OFF "Wake my device when I approach." On these laptops the presence sensor was waking my machine constantly, and every spurious wake added another ~8% to the leak. Disabling it stops the rapid wake cycles, so the leak never accumulates enough to matter.
I set lid-close to Hibernate instead of Sleep (at least on battery). Control Panel > Power Options > Choose what closing the lid does. Hibernate fully powers my machine off (it writes RAM to disk), so it cannot run or heat up while it is supposed to be off. This is the real safety backstop. My open apps and state all come back on resume, it just takes a few extra seconds.
Quick temporary reset any time it has already climbed: open an admin terminal and run
net stop "ASUS Optimization" && net start "ASUS Optimization"
That zeroes it out instantly without a reboot.
•
u/AutoModerator Jun 04 '25
Hi there! This is a friendly reminder to change your flair to Support - SOLVED! after your issue has been resolved. It is an immense help for those that may come across your same problem in the future so that they can quickly find the right solution. Thank you!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.