Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 22, 2019 8:58 PM
This logon was not allowed in before but now has been accessing my computer a lot. Also, my event viewer is constantly saying that I am reading some credential vault stuff and I am only reading my event viewer. If this stuff is normal I would like someone to just shoot me a response here.
An account was successfully logged on.
Subject:
Security ID: SYSTEM
Account Name: DESKTOP-59MLST1$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Information:
Logon Type: 5
Restricted Admin Mode: -
Virtual Account: No
Elevated Token: Yes
Impersonation Level: Impersonation
New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x2fc
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 impersonation level field indicates the extent to which a process in the logon session can impersonate.
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.
Special privileges assigned to new logon.
Subject:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Privileges: SeAssignPrimaryTokenPrivilege
SeTcbPrivilege
SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeAuditPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege
SeDelegateSessionUserImpersonatePrivilege
Thanks, MM
All replies (3)
Friday, August 23, 2019 2:09 AM
Hi MM,
According to your event log, there is not something special need to be noticed, normal phenomenon.
Only two account names appears in your event log, they are SYSTEM and DESKTOP-59MLST1$, if this DESKTOP-59MLST1$ is your own account, nothing needs worry.
Account Name: DESKTOP-59MLST1$
Logon Type: 5
Description: Service logon—This is used for services and service accounts that log on to start a service. When a service starts, Windows first creates a logon session for the user account that is specified in the service configuration.
Security ID: SYSTEM
Account Name: SYSTEM
Description: SYSTEM account logging on, it’s normal.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, August 23, 2019 2:16 AM
Open Task mgr,locate the software,R.click on it,open File location,R.click,properties,see what the OS says.Plus check/edit Windows Firewall/Exceptions..Next,download & run,kb890830
http://catalog.update.microsoft.com/v7/site/Search.aspx?q=890830
Friday, August 23, 2019 2:24 AM
What I find that only 2 users accessed system:
Account Name: DESKTOP-59MLST1$
Account Name: SYSTEM
System logon is absolutely normal.
[Used only by the System account
eg.System startup.]
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP