Last updated on November 17th, 2026 at 03:00 pm
Windows 10 has no single activity log. It keeps separate records: sign-in and power events in Event Viewer, opened files in Recent items, websites in each browser’s history, and app installs and crashes in Reliability Monitor. To learn whether the PC was used while you were away, check Event Viewer first: it timestamps starts, shutdowns, sleep and sign-ins.
Only check your own PC, or one you have permission to check. Doing otherwise can break workplace rules or the law.
Pick the record that answers your question
Each tool answers a different question. Start with the row that matches what you want to know, then use the sections below for the exact steps.
| Your question | Where to look | Admin needed? |
|---|---|---|
| Was the PC turned on, woken or shut down? | Event Viewer, System log | No |
| Who signed in, and was a password guessed wrong? | Event Viewer, Security log | Yes |
| Which files or folders were opened? | Recent items (shell:recent), Quick access | No (your account only) |
| Which websites were visited? | Browser history in each browser and profile | No |
| Which apps were installed, removed or crashed? | Reliability Monitor, Apps & features | No |
| What did Windows itself track for my account? | Activity history and Timeline | No |

One point to keep in mind: most of these records belong to a single user account. Recent items and browser history only show what happened in the account you’re signed in to, so if someone used a different account, you need to sign in to that account (or use the Security log) to see it.
See when the PC was on, asleep or shut down
The System log in Event Viewer records power events for every account, and you don’t need administrator rights to read it.
- Right-click the Start button and select Event Viewer. (You can also press Windows key + R, type
eventvwr.mscand press Enter.) - In the left pane, expand Windows Logs and select System. The middle pane fills with thousands of entries, newest first.
- In the Actions pane on the right, select Filter Current Log.
- In the box that reads <All Event IDs>, type
6005,6006,6008,42,1and select OK. - Read the Date and Time column. Select any entry to see its full text in the lower pane.
What those IDs usually mean:
- 6005: the Event Log service started, which happens when Windows starts.
- 6006: the Event Log service stopped, which happens during a normal shutdown or restart.
- 6008: the previous shutdown was unexpected, such as a power cut or a forced power-off.
- 42 (source Kernel-Power) and 1 (source Power-Troubleshooter): on most PCs these mark the system going to sleep and waking up. Other sources also use ID 1, so check the Source column and read the event text before relying on it.
To avoid typing the IDs every time, select Create Custom View in the Actions pane instead, choose the System log, enter the same IDs, and give the view a name such as “Power on and off.” It appears under Custom Views in the left pane.
Two command-line extras help here. In Command Prompt, powercfg /lastwake reports what woke the system from its last sleep, which is useful if the PC seems to wake on its own (a network adapter or scheduled task, for example). systeminfo lists a System Boot Time line on most systems, showing when Windows last started.
Worked example: was the laptop used overnight?
Priya shut the lid on her laptop at 10:40 p.m. and found it awake the next morning. In the filtered System log she sees a Kernel-Power 42 entry at 10:41 p.m., then a Power-Troubleshooter 1 entry at 2:13 a.m. She opens the wake event, and its text names the wake source. Then she runs powercfg /lastwake, which points to the same device. Combined with the Security log (next section), which shows no sign-in at 2:13 a.m., she can tell the laptop woke by itself rather than being opened by someone. Event Viewer shows times in the PC’s local time zone, so allow for that if the clock or time zone was changed.
See who signed in with the Security log
Sign-in records live in the Security log, which only an administrator can open. Microsoft documents three events that matter most:
- 4624: an account successfully logged on. It’s generated by the Audit Logon policy.
- 4625: an account failed to log on, also from Audit Logon.
- 4634: an account was logged off. This one needs the separate Audit Logoff policy. Event 4647 means the user started the sign-out themselves.
- Open Event Viewer from an administrator account.
- Expand Windows Logs and select Security.
- Select Filter Current Log, type
4624,4625in the event ID box and select OK. - Open an event. In the General tab, find Logon Type and, under New Logon, the Account Name.
The log is noisy, because Windows services sign in constantly. Ignore entries for SYSTEM and other built-in service accounts and focus on real user names. The Logon Type number tells you how the sign-in happened:
| Logon Type | Short name | What it usually means |
|---|---|---|
| 2 | Interactive | Someone signed in at the keyboard and screen |
| 3 | Network | Another device accessed a shared folder or printer on this PC |
| 5 | Service | A Windows service started (normal background noise) |
| 7 | Unlock | Someone signed back in at the lock screen |
| 10 | RemoteInteractive | A Remote Desktop session |
| 11 | CachedInteractive | A sign-in with saved domain credentials without the domain controller being contacted |
For a failed sign-in (4625), the Status or Sub Status code explains why. Microsoft lists 0xC000006A as a wrong password, 0xC0000064 as a user name that doesn’t exist, 0xC0000234 as a locked-out account, 0xC0000072 as a disabled account and 0xC0000193 as an expired account. A run of 0xC000006A entries close together means someone kept trying passwords.
To pair a sign-in with its sign-out, match the Logon ID in the 4624 event with the same ID in a later 4634 event. Logon IDs are only unique until the next restart, so compare events from the same boot.
If you prefer PowerShell, this command lists the 50 most recent failed sign-ins (run PowerShell as administrator): Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625} -MaxEvents 50. Change 4625 to 4624 for successful ones. For one local account’s most recent sign-in, net user Alex in Command Prompt shows a Last logon line (replace Alex with the local account name, which can differ from the display name of a Microsoft account).
Check whether sign-in auditing is on
If the Security log shows no 4624 events at all, don’t assume nobody signed in. Check the audit policy first. Open Command Prompt as administrator and run auditpol /get /category:"Logon/Logoff" (keep the quotes, because the name contains a slash). Look at the Logon and Logoff lines: Success or Success and Failure means events are being recorded, while No Auditing means they aren’t. This command works on Windows 10 Home too.
On Pro, Enterprise and Education, you can change the setting in secpol.msc under Advanced Audit Policy Configuration > System Audit Policies > Logon/Logoff > Audit Logon (and Audit Logoff for 4634). A change only affects future sign-ins; it can’t recover events that were never written. On a work PC, this policy may be managed by your organization.
Find files and folders that were opened
- Press Windows key + R, type
shell:recentand press Enter. The Recent Items folder opens. - Select View > Details.
- Select the Date modified column heading to sort newest first. Each shortcut stands for a file or folder that was opened, and its date is roughly when it was last opened.
Other places that show recent files for the signed-in account:
- Quick access in File Explorer lists recent files under Recent files.
- Jump Lists: right-click an app on the taskbar, such as Word or Notepad, to see the documents it opened.
- Changed files: open Documents, Desktop or Downloads, switch to Details view and sort by Date modified to see what was saved or downloaded.
- Deleted files: open the Recycle Bin and sort by Date Deleted.
If these lists are empty, the feature may be switched off rather than the PC being unused. Check Settings > Personalization > Start for the toggle that shows recently opened items in Jump Lists and Quick access, and in File Explorer check View > Options > General > Privacy for the recently used files option.
Check websites and downloads in each browser
- History: press Ctrl + H in Edge, Chrome or Firefox to open history grouped by date. Use the search box to look for a site.
- Downloads: press Ctrl + J to see files downloaded and when.
- Profiles: history is stored per browser and per browser profile, so check each browser installed and each profile in it.
Private windows (InPrivate in Edge, Incognito in Chrome, Private Browsing in Firefox) don’t save history after they close. Browser history can also sync between devices when someone is signed in to the browser, so an entry may come from a phone or another PC on the same account. For the private-browsing side, see how to find traces of Incognito browsing on Windows 10.
Activity history and Timeline on Windows 10 today
Activity history is Windows’ own record of apps, files and websites you used. On Windows 10 you can still browse it in Timeline, but it changed in two important ways: it is now local only, and Windows 11 dropped Timeline entirely. According to Microsoft’s list of deprecated Windows 10 features, syncing activity across devices ended for Microsoft accounts in 2021 and for work accounts in January 2024, but the Timeline view and local activity history remain on Windows 10.
- Open Settings > Privacy > Activity history.
- Check that Store my activity history on this device is ticked. If it’s off, Windows hasn’t been saving activity and Timeline will be empty or short.
- Press Windows key + Tab and scroll down below the open windows to see earlier activities grouped by day.
Timeline isn’t a complete record of everything you did. Microsoft’s activity history privacy page also notes that InPrivate browsing isn’t saved. Activity collected before the sync change may still appear in your Microsoft account’s privacy dashboard until it’s deleted, which Microsoft says happens within 30 days of the last sync. On a Windows 11 PC the steps are different: here’s how to view activity history on Windows 11.
Review apps, installs, updates and crashes
Reliability Monitor is the most readable day-by-day history Windows offers. Press Windows key + R, type perfmon /rel and press Enter. Select a day’s column to see what happened: apps installed or removed, Windows updates, and app or Windows failures. Switch the view to Weeks to scan a longer period. It shows changes and problems, not normal use, so an app that ran fine won’t appear.
Other places worth checking:
- New programs: Settings > Apps > Apps & features, then set Sort by to Install date.
- Updates: Settings > Update & Security > Windows Update > View update history.
- App usage: in Task Manager (Ctrl + Shift + Esc, then More details), the App history tab shows CPU time and network use for Microsoft Store apps since the date shown at the top. Classic desktop programs generally aren’t listed there. The Startup tab shows what launches at sign-in.
- Network use per app: Settings > Network & Internet > Data usage (on some versions, under Status) lists how much data each app used over a recent period. An app with data use was running, even if no files were opened.
If you’re also curious about what was printed, the print queue doesn’t keep history by default, but you can turn on and check print history in Windows 10 for future jobs.
What Windows does not record
It helps to know the gaps before drawing conclusions:
- No keystrokes, screens or file contents. Windows doesn’t log what was typed or what was on screen. Built-in records show that something was opened or run, not what was done inside it.
- No universal app log. A desktop program that runs without opening files or crashing may leave little trace outside Task Manager’s Startup list and data usage figures.
- Records can be switched off or cleared. Recent items, activity history and browser history can be turned off or wiped by the account owner. An administrator can clear the Security log, but Windows then writes event 1102, “The audit log was cleared,” which names the account that did it.
- Forensic traces exist but aren’t for casual checks. Folders such as Prefetch and registry areas such as UserAssist hold program-run data, but reading them reliably needs specialist tools, and editing the registry can cause problems.
Clear or limit your own history
If your goal is privacy rather than investigation, clear each layer separately, because no single button wipes them all:
- Activity history on the PC: in Settings > Privacy > Activity history, untick Store my activity history on this device to stop new collection, then select Clear under the clear activity history heading.
- Your Microsoft account: on the privacy dashboard, review and clear each category (browsing, search, app and service activity) one at a time.
- Recent files: follow the steps to clear recent files in Windows 10, which also covers Quick access.
- Browsers: press Ctrl + Shift + Delete in each browser and choose a time range.
Before clearing an Event Viewer log, save a copy. Right-click the log (for example, System), choose Save All Events As and save the .evtx file. Clearing can’t be undone, and on a work PC it may break company policy and will be noticed. There’s rarely a good reason to clear the Security log on a home PC.
Keep others off your PC
- Press Windows key + L to lock the PC every time you step away. Each later sign-in then shows up as Logon Type 7.
- Give each person their own Windows account, so records like Recent items and browser history stay separate and the Security log names who signed in.
- Use a PIN or password, and turn off Remote Desktop if you don’t use it.
- Keep the PC patched. Microsoft ended regular Windows 10 support on October 14, 2025, so a PC that has to stay on Windows 10 should enroll in Windows 10 Extended Security Updates to keep receiving security fixes.
What the records can and can’t show
Can I see how long someone spent on the PC?
Roughly. Pair a 4624 sign-in with the 4634 or 4647 sign-out that has the same Logon ID, or compare the start (6005) and shutdown (6006) times. Sleep and lock periods inside that window count as time too, so look for 42 and 1 entries in between.
Do these records show activity from a Windows 10 Home PC?
Yes. Event Viewer, Reliability Monitor, Recent items, Timeline and auditpol all work on Home. Only the Local Security Policy editor (secpol.msc) is missing, so you can read the audit state but not change it through that editor.
Will an entry tell me which person used the PC?
Only which account. If several people share one account and password, Windows can’t tell them apart. Separate accounts are the only way to tie activity to a person.
Why do I see sign-ins at times I wasn’t using the PC?
Most are service or network sign-ins (types 5 and 3) by Windows itself or by another device on your network reaching a shared folder. Check the Logon Type and Account Name before worrying; a type 2, 7 or 10 sign-in by a real user name at an odd hour is the one to look into.
How far back do the logs go?
Event logs have a maximum size and overwrite the oldest entries when full, so a busy Security log may only reach back days or weeks. Right-click a log and choose Properties to see its size limit and what happens when it’s full. Scroll to the bottom of the filtered list to see the oldest entry still kept.
For a quick next step, open Event Viewer now and save the power on and off custom view, so the answer to “was my PC used?” is one click away next time.

Matt Jacobs writes and maintains the guides on Support Your Tech, which he started in 2017. He spent most of his career keeping small-business PCs running and still takes the occasional consulting job, so the steps here come from fixing the same problems on other people’s computers. Each guide follows Microsoft, Apple and Google’s own documentation and is updated when the steps change. Screenshots marked “Recreated” are illustrations of the real screens.