ROG Ally frequently experiences delays when restarting or shutting down.
ROG Ally frequently experiences delays when restarting or shutting down.
I've noticed the restart and shutdown process is taking a long time lately. When I tried to power off my Ally, it kept looping on the shutdown screen for about two minutes before turning off completely. The screen went dark but the device stayed on. Only after a few minutes did it finally shut down with the animation briefly showing. Restarting it also caused delays—sometimes it stuck on the restart screen for several minutes, then went black for a while before coming back up. I searched for fixes but didn’t find anything useful.
I don’t use an SD card and haven’t used one in a long time. My slot is dead, even though the device is only three weeks old. I’m running a custom fan curve (74% at 65°C) and ASUS requires that setting for both fans. I’m not sure what’s causing the slowdown.
Could anyone suggest a solution? I’d appreciate any advice, though it isn’t urgent—I just want to avoid waiting more than five minutes each time I need to restart.
Check the task manager for any unusual activity or excessive processes that might delay shutdown. Consider turning on verbose messages in Windows to understand why it takes longer to close. Search online for instructions on enabling verbose logging. If possible, try booting in safe mode to test if the issue persists.
It seems there was minimal activity since lowering the power profile to 30W and keeping fans low. The device stayed cool most of the time. I hadn’t turned it off or restarted it for three days before attempting shutdown yesterday. After exiting a game, Armoury Crate SE User Session Helper sometimes loads a core fully until the session ends. My idle CPU usage is usually around 5% or less.
Your device staying cool doesn't guarantee everything is working perfectly. There might be background processes or services running slowly, which can cause delays when shutting down. This usually occurs during updates or maintenance. From what you said, you checked Task Manager—consider turning on verbose logging to get more details.
Sure, I'm ready to provide detailed updates. Please let me know what you'd like to focus on.
The group policy editor isn't accessible on Windows Home, the version Ally is using. I can access it on my PC with Windows 11 Pro, though not on Ally. I attempted using Microsoft's registry editor, but I'm unsure if that resolved the issue and it also closed after a short period. Some discussions on Reddit suggest it often occurs during their initial shutdown or restart after a few days.
You're asking about the meaning of "not worked" in the context of shutdowns, specifically mentioning features like "Stopping Services." It seems you want clarification on additional details during shutdown and whether enabling verbose messages via tweaker would help. You also wonder if registry settings made it easier for you.
I used the instructions on Microsoft's website to turn it on through the registry, then I powered it off to check if it might have taken a long time because I hadn't turned it off for three days. I set up a DWORD named verbosemessages and made it equal to 1. When I shut it down, nothing appeared new and it ended normally.
I'll handle that. I tested it on my laptop since I'm not with Ally, and now I can get the old context menu again instead of the new one. At first I wasn't too bothered, but over time I've grown frustrated because simple actions like refreshing the page now need an extra click to reach the old menu. Using coding projects in an IDE meant I had to switch back every time, which is going to be a big hassle.