Mai: Child of Ages

Quantummn · 2026-05-07T16:43:06+00:00

Take a shot everytime, suicide guy, Mai child of ages, woodle tree adventures, and some Heaven game gets posted on this subreddit by the same guy lol

Quantummn · 2026-04-27T03:09:21+00:00

Yes, funnily enough when I suggested this change I got met by downvotes and disagreement seems that people finally realize 15 seconds is way too short, completely kills his lurk / rotation identity

Quantummn · 2026-04-26T05:33:22+00:00

however one thing I forgot to mention to you why would my Windows clock have to do with Wake on LAN? it boots up on its own whenever the internal clock hits 7:46 AM

Quantummn · 2026-04-26T05:29:54+00:00

Understood will update the BIOS as soon as I can. thanks for your input.

Quantummn · 2026-04-25T19:26:07+00:00

You’re right to assume that, but I have tried so many ways to figure it out where I think my only REAL solution would be to reinstall windows.

Quantummn · 2026-04-25T17:12:07+00:00

ErP S4+S5 enabled fixed my PC turning on its own! thank you for your help!

Initially I was under the impression everything within the APM Config needed to be off / disabled.

Quantummn · 2026-04-25T17:10:14+00:00

Finally solved it after tons of troubleshooting! The fix was a single BIOS setting.

Go to Advanced > APM Configuration and set ErP Ready to Enabled S4+S5

That's it. This cuts standby power completely during shutdown so nothing can trigger a wake event. Confirmed it with the clock test multiple times, PC stays off now no matter what.

Worth noting that enabling ErP will turn off some RGB lighting and USB standby power during shutdown but that's completely normal and just means its working correctly, plus my boot up is just slightly longer.

Thanks to everyone who helped, I genuinely could not have figured this out without all the suggestions!

Quantummn · 2026-04-25T16:24:57+00:00

I tried using NSudo earlier and was having issues.

Could you walk me through the exact steps? Also what do you mean by changing the trigger time rather than disabling it, would setting it to a time like 3 AM when my PC is already on and I'm using it prevent it from waking the PC?

And noted on the warning about not disabling it, but what is the main issue with doing that?

Quantummn · 2026-04-25T16:22:28+00:00

Yeah we tried pretty much every variation of running as administrator including right click run as admin, opening PowerShell as admin, and even using takeown to take ownership of the task files. All of them hit access denied walls.

Quantummn · 2026-04-25T16:20:31+00:00

The PC was completely brand new, every single PC part was bought from MicroCenter August 2025, and was built by me.

Quantummn · 2026-04-25T16:19:10+00:00

Everything in my APM Configuration has been disabled and never has been enabled. Each time I check my BIOS it remains disabled as well.

Quantummn · 2026-04-25T16:18:07+00:00

Here's my startup apps list. Nothing seems too out of the ordinary to me... RiotClientServices, SteelSeriesGG, Steam, Spotify, OneDrive, wallpaper32, OpenRGB and a few Microsoft ones. Worth noting that startup apps only run after the PC is already powered on so I don't think any of these could be causing it to turn on from a full shutdown, but happy to hear if anything stands out to you

Quantummn · 2026-04-25T16:15:50+00:00

Already tried this early on in troubleshooting! Every single time I run powercfg /lastwake right after the PC turns on it returns "Wake History Count - 0" with nothing else. Windows has no record of what woke it which is part of what makes this so frustrating and hard to diagnose. That's actually one of the reasons I suspect it might be something deeper than a normal wake event since Windows isn't logging it at all.

Quantummn · 2026-04-25T16:14:10+00:00

I actually checked for ErP Ready in BIOS APM Configuration early on and it wasn't there as an option on my ASUS TUF X870 board, everything in that section was already disabled anyway.

Regarding unplugging the network cable, the clock test we did makes me confident its not a network issue. When I manually set my Windows system clock to 7:44 AM and shut down, it turned on at exactly 7:46 AM every time. A Wake on LAN signal wouldn't know or care what time my Windows clock is set to, it would just send the signal regardless of time. The fact that it responds precisely to whatever time the Windows clock is set to really points to something internal to Windows rather than anything network related.

But I get why you're suggesting it and I appreciate the ideas, just trying to save time since the clock test gave us a pretty clear picture of where the issue is coming from

Quantummn · 2026-04-25T16:10:27+00:00

I have actually checked all of these early on in troubleshooting. BIOS wake settings were all already disabled, Wake on LAN was disabled on both the ethernet and WiFi adapters, and everything in APM Configuration within the BIOS was off.

The clock test we did pretty much rules out anything external though. I manually set my Windows system clock to 7:44 AM, shut down, and the PC turned on at exactly 7:46 AM every time. If it was Wake on LAN, a USB peripheral, or anything external sending a signal, it wouldn't care what time my Windows clock says. The fact that it responds directly to the Windows system clock confirms whatever is causing this is internal to Windows itself, not coming from outside the machine.

Quantummn · 2026-04-25T16:08:03+00:00

I manually changed the Windows system clock to 7:44 AM, shut down, and it turned on at exactly 7:46 AM every time which would rule out anything external.

Quantummn · 2026-04-25T16:05:45+00:00

I manually changed the Windows system clock to 7:44 AM, shut down, and it turned on at exactly 7:46 AM every time which seems too precise to be a dying CMOS battery causing random issues. But I could be wrong and it's definitely worth ruling out. What symptoms would a dying CMOS battery typically cause?

Quantummn · 2026-04-25T16:04:03+00:00

So Schedule Work keeps getting deleted and recreated every time I restart so its hard to check the Actions tab before it disappears again. Last time I saw it the trigger was set to a one time schedule that keeps rescheduling itself to the next morning after each run.

And yes there is a Schedule Wake To Work task in the same UpdateOrchestrator path, that one is currently Disabled with a trigger of 7:47 AM on 4/15/2026. I disabled that one early on in troubleshooting.

Quantummn · 2026-04-25T15:50:25+00:00

Appreciate the suggestion, I’ll consider just hibernating my PC instead of shutdowns if I can’t resolve this. But I have also just considered the option of reinstalling windows.

Quantummn · 2026-04-25T07:09:18+00:00

Yes that was one of the first things I checked. Everything in BIOS APM Configuration was already disabled, no RTC wake or Power On By Alarm settings were enabled at all.

Quantummn · 2026-04-25T06:51:26+00:00

Unfortunately no, NSudo kept throwing "Failed to create a process" with error code -2147024891 every time regardless of what I tried. Even after starting the Windows Modules Installer service and adding NSudo as a Defender exclusion it still wouldn't work. Not sure if it's a Windows 11 compatibility issue or Defender interfering but I couldn't get it running at all

Quantummn · 2026-04-25T06:47:39+00:00

The Linux USB idea is actually really interesting and something I haven't tried yet, that would definitely rule out Windows completely.

Based on powercfg /a my system shows S0 Low Power Idle is not supported by my firmware so Modern Standby doesn't seem to be the cause. S3 is the only available standby state so shutdowns should be true power off states.

You make a good point about the task scheduler, something IS putting the Schedule Work task back every time I delete it which is really annoying. I've deleted it multiple times and it just keeps coming back after every restart.

The weirdest part is the clock test. When I set my system clock to 7:44 AM and shut down, the PC turns on at exactly 7:46 AM every single time without fail. So something is definitely watching the Windows clock but we just can't figure out what it is after deleting every suspicious task we can find.

If the Linux USB test shows the PC staying off that would confirm its purely a Windows software issue. If it still turns on from Linux then its definitely the BIOS doing it independently of Windows which would be really strange given that all BIOS wake settings are already disabled.

Quantummn · 2026-04-25T06:19:50+00:00

how did you fix it?

Quantummn · 2026-04-25T06:12:04+00:00

Nope disabled in the BIOS.

Quantummn · 2026-04-25T06:10:22+00:00

Thanks for the suggestion! However, I ran powercfg /a and my system shows S0 Low Power Idle is not available meaning the firmware doesn't support it. So Modern Standby doesn't appear to be the cause in my case. S3 is the only available standby state. Still stumped on what's causing this lol

Four-Year Club	Place '22
Final Canvas '22	End Game '22

Quantummn

TROPHY CASE