I used to frequent this site and provide the help I could and learn from others on here. This problem I'm not sure how to approach.  So as the title says my computer has been starting up by itself. I place the computer into sleep mode it will start back up periodically through the day. At first I thought someone scheduled multiple scheduled tasks to start my computer up as a gag, that was not the case, I've scanned multiple times for virus. I used the scanners that CH lists for scanning a system and CAME up clean multiple times.


Oh, I almost forgot, here are my specs.


Help please,


TalonTromper

[recovering disk space, attachment deleted by admin]It's either a scheduled task...or an app updating.
Could also be your e-mail client phoning home.
I don't use any Windows power saving features.If it was a scheduled task wouldn't it be listed inside the schedule tasks inside computer management?


Also I've tried unplugging my network when I would leave, still happens.Check the event log
In answer to your question...Yes...a scheduled Task would be listed.I've noticed that same thing with my laptop. Even though it's SLEEPING at times I hear the fan and the harddrive running.SalmonTrout I looked into the event viewer and the earliest thing that I could find entering an active state was "Window Image Acquisition"





Log Name:      System
Source:        Service Control Manager
Date:          7/27/2014 3:43:03 AM
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      TomC-Comp_Room
Description:
The Windows Image Acquisition (WIA) service entered the running state.
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
 
   
    7036
    0
    4
    0
    0
    0x8080000000000000
   
    119036
   
   
    System
    TomC-Comp_Room
   
 
 
    Windows Image Acquisition (WIA)
    running
    7300740069007300760063002F0034000000
 




Here is the exported version of the event log.






Am I reading this right??? My system was remotely activated? The key field says that for a "3" that it was a network logon to my system, am I reading this wrong?





Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/27/2014 3:42:54 AM
Event ID:      4624
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      TomC-Comp_Room
Description:
An ACCOUNT was successfully logged on.


Subject:
   Security ID:      SYSTEM
   Account Name:      TOMC-COMP_ROOM$
   Account Domain:      WORKGROUP
   Logon ID:      0x3e7


Logon Type:         5


New Logon:
   Security ID:      SYSTEM
   Account Name:      SYSTEM
   Account Domain:      NT AUTHORITY
   Logon ID:      0x3e7
   Logon GUID:      {00000000-0000-0000-0000-000000000000}


Process Information:
   Process ID:      0x2d0
   Process Name:      C:\Windows\System32\services.exe


Network Information:
   Workstation Name:   
   Source Network Address:   -
   Source Port:      -


Detailed Authentication Information:
   Logon Process:      Advapi 
   Authentication Package:   Negotiate
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:      0


This event is generated when a logon session is created. It is generated on the computer that was accessed.


The subject fields indicate the account on the local system which requested the logon. This is most COMMONLY a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.


The logon type field INDICATES the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).


The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.


The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.


The authentication information fields provide detailed information about this specific logon request.
   - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
http://schemas.microsoft.com/win/2004/08/events/event">
 
   
    4624
    0
    0
    12544
    0
    0x8020000000000000
   
    32930
   
   
    Security
    TomC-Comp_Room
   
 
 
    S-1-5-18
    TOMC-COMP_ROOM$
    WORKGROUP
    0x3e7
    S-1-5-18
    SYSTEM
    NT AUTHORITY
    0x3e7
    5
    Advapi 
    Negotiate
   
   
    {00000000-0000-0000-0000-000000000000}
    -
    -
    0
    0x2d0
    C:\Windows\System32\services.exe
    -
    -
 





Sorry for the wall of text.Why would at the same time as a log-on would a policy change be executed to the VSS.exe? Volume Shadow Service policy changes make no sense during a log-on.Just another reason to NOT use Win power saving features...just sayin.
If you want the PC off ...turn it off...if you want it on...leave it on.If it's a remote magic packet wouldn't that start my system regardless of s1-4?


But I will probably start leaving my system in a powered off state and see what happens.


Quote

If it's a remote magic packet wouldn't that start my system regardless of s1-4?