sodcalculator

10 Tech How-To

Check If Someone Else Is Logging Into Your Windows 10 PC

Guide 10-51681 · Updated · Step by step

This guide shows you how to check whether someone else has been logging into your Windows 10 computer, and how to spot signs of unauthorized access. You’ll learn where Windows records successful and failed sign-in events, how to read those logs, and what to do if you find something suspicious.

What You’ll Need

  • Administrator access to the Windows 10 PC (you need this to view security logs).
  • A basic understanding of event log terms like “Event ID” and “Logon Type.”
  • If your PC is part of a work or school domain, you may need permission from your IT admin to view these logs.

Step-by-Step

  1. Open Event Viewer. Press Windows Key + R, type eventvwr.msc, and press Enter. If prompted by User Account Control, click Yes.
  2. Navigate to Windows Logs. In the left pane, expand Windows Logs and click Security. This is where all sign-in events are recorded.
  3. Filter for sign-in events. In the right pane, click Filter Current Log…. In the window that opens, check the boxes for Success (4624) and Failure (4625) under “Event IDs”. You can also add 4634 (logoff) and 4647 (initiated logoff) if you want a fuller picture. Click OK.
  4. Look at the most recent events. The list will now show only sign-in related events. Each entry shows the date/time and the event ID. Double-click any entry to see details.
  5. Identify the user. In the event details, scroll to the Account Name field under “New Logon”. This tells you which user account was used for the sign-in. If you see an account you don’t recognize, or a sign-in at a time you weren’t using the PC, that’s a red flag.
  6. Check the Logon Type. The Logon Type field tells you how the sign-in happened. Type 2 means interactive (someone at the keyboard), 3 means network (e.g., accessing a shared folder), 4 means batch, 5 means service, 7 means unlock, 8 means network with cleartext, 9 means new credentials, and 10 means remote interactive (like Remote Desktop). If you see a Type 2 or Type 10 at a time you weren’t there, investigate further.
  7. Check the source IP address. For remote logons (Type 10), look for the Source Network Address field. This shows the IP address of the remote computer. If it’s not your home or office IP, someone may be connecting remotely.
  8. Look for failed attempts. Event ID 4625 indicates a failed logon. Many failed attempts in a short period can suggest someone guessing passwords. The Logon Type and Source Network Address fields here are equally important.
  9. Check the “Last Logon” timestamp. Open Command Prompt (type cmd in Start, right-click and run as administrator) and run net user <username>. This shows the last logon time for that user. Compare it with your own activity.
  10. Review other security logs. In the same Security log, look for Event ID 4720 (user account created), 4726 (user account deleted), or 4732 (member added to security group). These can indicate someone creating backdoor accounts.

Common Mistakes

  • Misreading Logon Type 3. Many network logons are normal (e.g., connecting to a network drive). Don’t panic over Type 3 unless the source IP is unfamiliar.
  • Ignoring time zones. Event Viewer shows times in your local time zone by default, but if you’ve changed time zones or the PC is set to UTC, the times can look wrong. Check the PC’s time zone settings first.
  • Assuming all 4624 events are human logons. Windows services and scheduled tasks also generate 4624 events. Check the Logon Type and the account name — SYSTEM and SERVICE accounts are normal.
  • Forgetting to check for RDP. If Remote Desktop is enabled, anyone with network access can try to log in. Check whether the RDP port (3389) is open on your router.
  • Only checking the last few events. Someone could have logged in days ago. Use the “Find” button (Ctrl+F) in Event Viewer to search for your username or unknown usernames across a longer period.

Tips

  • Enable logon auditing if needed. By default, Windows 10 logs successful and failed sign-ins, but if you see nothing at all, auditing may be off. Open Local Security Policy (secpol.msc), go to Security Settings → Local Policies → Audit Policy, and enable “Audit logon events” for success and failure.
  • Use “WhoLoggedOn” style tools. Third-party tools like NirSoft’s WinLogOnView can parse the security log into a readable table, but for this guide, Event Viewer is enough.
  • Set up a baseline. Note your own typical logon times and types. Then anything unusual stands out immediately.
  • Check the “Workstation Name” field. For interactive logons, this shows the computer name. If it’s not your PC’s name, that’s suspicious.
  • Look for multiple rapid reboots. If someone is installing software or changing settings, you may see many unexpected shutdown/startup events (Event IDs 1074, 6005, 6006) in the System log.

Troubleshooting

You don’t see any 4624 or 4625 events. This usually means auditing is disabled. Follow the “Enable logon auditing” tip above. If you’re on Windows 10 Home, Local Security Policy may not be available; you can enable auditing via auditpol /set /subcategory:"Logon" /success:enable /failure:enable in an elevated Command Prompt.

The Security log is empty or very small. The log may have been cleared. Right-click Security in Event Viewer and select Properties. Check the “Maximum log size” and whether “Clear log manually” is set. A cleared log with no recent events is itself a red flag.

You find a logon you didn’t make, but you’re not sure. Cross-check with other logs. Look at the System log for events around the same time (e.g., 6005 “Event log service started” indicates a reboot). Also check Applications and Services Logs → Microsoft → Windows → PowerShell/Operational for any script activity.

You can’t open Event Viewer due to permissions. You must be an administrator. If your account is standard, ask an admin to run it for you. On a work PC, your IT department controls this.

You suspect someone is using your PC physically. Check for recently modified files, browser history, or installed programs. Look in C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Recent for recently opened files. Also check the Task Manager (Ctrl+Shift+Esc) for running processes you don’t recognize.

You find evidence of unauthorized access. Immediately change your password, enable two-factor authentication on your Microsoft account, run a full antivirus scan, and consider disconnecting the PC from the network until you’ve cleaned it. If it’s a work device, report it to IT.

Frequently Asked Questions

Q: Can I see when my computer was last logged into?
A: Yes. Run net user <yourusername> in Command Prompt and look at “Last Logon”. This shows the last time that user account was used to sign in.

Q: What is the difference between Event ID 4624 and 4625?
A: 4624 is a successful logon, and 4625 is a failed logon attempt. Both are recorded in the Security log.

Q: Does Windows 10 log all sign-ins by default?
A: Yes, on most installations, both successful and failed logons are audited by default. If you see nothing, auditing may have been disabled.

Q: Can someone delete the security log to hide their tracks?
A: Yes, an administrator can clear the Security log. If you notice the log has no entries or a gap in dates, that itself is suspicious.

Q: Is a “Logon Type 3” always a sign of someone else?
A: No. Type 3 is a network logon, which happens when you access shared folders, printers, or other network resources. Only worry if the source IP is unfamiliar or it happens at odd times.

Q: How do I know if someone is using Remote Desktop to access my PC?
A: Look for Event ID 4624 with Logon Type 10. Also check the “Source Network Address” field — it will show the remote IP. You can also check if Remote Desktop is enabled by going to Settings → System → Remote Desktop.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →