PotPlayer Not Remembering Playback Position? The Settings Fix That Usually Solves It

PotPlayer is popular because it is fast, configurable, and feature-rich, but one annoyance can ruin the experience: you close a video mid-way, reopen it later, and it starts from the beginning. If PotPlayer is not remembering playback position, the cause is usually a setting (or a combination of history settings, playlist behavior, and Windows write-permission issues). This guide walks you through the most reliable fixes, explains why each one matters, and includes a short checklist to confirm PotPlayer is actually saving resume data.

1. Confirm The Core Resume Setting Is Enabled.

PotPlayer can resume playback, but it will only do so if its resume and history features are allowed to store playback state. The first thing to do is confirm that PotPlayer is permitted to remember file history and that resume behavior is enabled.

1.1 Enable “Remember Playback Position” (And Related History Options)

Open PotPlayer Preferences and look for options related to playback position and history. The exact wording can vary slightly by version, but you are typically looking for features that:

• Remember playback position (resume)
• Store recently played files (history)
• Use last played position when reopening files

If the player is configured to clear history on exit (or never store it), it often cannot resume reliably because it has nothing to reference. Make sure any “clear history” or “don’t save history” option is disabled.

After changing settings, completely exit PotPlayer (not just close the window if it stays in the tray), then reopen it and test with a local file.

1.2 Check That “Start From Beginning” Is Not Overriding Resume

Some users unknowingly enable behavior that always starts files from the beginning. If you see an option that forces files to start at 0:00, it can override resume. Disable that behavior and retest.

1.3 Test With A Simple Local File First

Before troubleshooting edge cases, verify that resume works on a straightforward scenario:

1. Pick a local MP4 file stored in a normal user folder (like Videos).
2. Play it for 20 to 60 seconds.
3. Close PotPlayer fully.
4. Reopen the same file via “Open File” inside PotPlayer (not via a playlist yet).

If this works, your issue may be playlist-related, network-path related, or tied to file association launching. If it does not work, continue to the next sections.

2. Make Sure PotPlayer Is Allowed To Save Its Settings And History.

A very common reason PotPlayer does not remember playback position is that it cannot write its configuration or history files (or the Windows registry entries it uses). This can happen due to permissions, “portable” mode configuration, Controlled Folder Access, or installing/running PotPlayer in locations where it cannot persist data.

2.1 Run PotPlayer Normally (Not In A Restricted Folder)

If PotPlayer is installed in a standard location and run as a normal user, it typically can store its settings. Problems are more likely if you:

• Run a “portable” copy from a protected directory
• Store it under Program Files but try to write configuration next to the executable
• Use a locked-down corporate machine with policy restrictions

If you are using a portable build, confirm where it saves configuration (often alongside the executable or in a dedicated config folder). If that folder is read-only, or is synced/virtualized in a way that discards changes, resume will fail.

2.2 Check Windows “Controlled Folder Access” And Security Software

Windows security features can block apps from writing to protected folders. If PotPlayer’s history is stored in a location that Windows Defender treats as protected (or your third-party security suite blocks), PotPlayer may appear to “forget” playback position every time.

If you suspect this:

• Verify whether Controlled Folder Access is enabled.
• If enabled, allow PotPlayer as an app that can access protected folders (or move PotPlayer’s configuration to an unprotected location, depending on your setup).

Be cautious and only allow apps you trust. PotPlayer is widely used, but you should still download it from a reputable source and verify you are running an official build.

2.3 Confirm Settings Actually Persist After Restart

A quick way to detect write-blocking is to change an obvious setting, restart PotPlayer, and see whether the setting “sticks.” For example:

1. Change a visible preference (like the skin or on-screen display behavior).
2. Exit PotPlayer completely.
3. Reopen PotPlayer and check whether the preference stayed changed.

If settings revert, you have a persistence problem. Resume cannot work reliably until PotPlayer can save its config and history.

3. Fix Playlist And “Open Next File” Behaviors That Can Break Resume.

PotPlayer’s playback position memory often interacts with how you open files: from a file browser, from “Recent,” from a playlist, or from the file association in Windows Explorer. In some configurations, PotPlayer may treat a file as a “new” item each time (especially if it is opened through a playlist entry that changes), so it never matches the old playback state.

3.1 Retest By Opening The Same File The Same Way

Resume matching often relies on the file path. If you open the same content through different paths or aliases (for example, a network path vs. a mapped drive letter), PotPlayer may store two different “identities” for what you consider the same file.

Examples that can confuse resume tracking:

• Opening as Z:\Movies\Film.mkv sometimes, and as \\NAS\Movies\Film.mkv other times
• Opening a file via a shortcut that points to a different resolved path
• Opening a stream URL whose address changes slightly each time

Standardize how you open the file and test again.

3.2 Watch For “Always Add To Playlist” Versus “Play Immediately”

If PotPlayer is configured to automatically add items to a playlist and you repeatedly open the same file, you can end up with multiple playlist entries that look identical. Depending on how PotPlayer tracks state, you might resume the “wrong” entry (or the newest one, which has no saved position yet).

Try this troubleshooting step:

1. Disable any option that automatically appends every opened file to the playlist (temporarily).
2. Open one file, play part of it, close PotPlayer, and reopen that same file directly.
3. If resume now works, adjust playlist settings so you do not create duplicate entries for the same path.

3.3 Be Careful With “Auto Play Next” When Testing

Auto-playing the next file in a folder is great for TV episodes, but it can complicate testing resume because you may close PotPlayer while it has advanced to the next item or has updated playlist state. When diagnosing resume issues, test with one file and disable any automation that jumps between items until you confirm resume is stable.

4. Understand Which Media Types Resume Well (And Which Sometimes Do Not).

Not all playback sources behave the same. PotPlayer can usually resume local files well, but some sources do not have stable “positions” to return to, or they require the player to remap time to content in ways that do not persist cleanly.

4.1 Local Files Usually Work Best

For MP4, MKV, AVI, and similar local files, resume is typically straightforward: the player stores a timestamp and returns to it. If local files fail to resume, the problem is more likely a settings persistence issue (Section 2) than a file type limitation.

4.2 Network Shares Can Be Tricky

If your video is on a NAS or shared folder, consider these factors:

• Paths can differ (mapped drive vs. UNC path), producing separate resume entries.
• Availability and authentication can vary between sessions.
• Latency can cause delayed seeking, making it seem like resume did not happen.

Use one consistent path format, and ensure the share is available before opening the file.

4.3 Streams And Some Playlists May Not Resume Reliably

For live streams (and even some on-demand streams), a “resume point” might not be meaningful. If a URL is time-shifted, tokenized, or expires, PotPlayer may not be able to return to the exact timestamp. In those cases, a local download or a stable file source is the most reliable way to get consistent resume behavior.

5. Fix “It Resumes Sometimes” Issues: A Practical Checklist.

If PotPlayer resumes inconsistently, you want to narrow down which condition breaks it. Use this checklist to identify patterns.

5.1 Quick Diagnostic Checklist

• Confirm PotPlayer settings persist after restart (change a visible setting and check it stays).
• Enable playback history and ensure it is not cleared automatically on exit.
• Test one local file in a user folder using “Open File” inside PotPlayer.
• Open the file using one consistent path (avoid mixing UNC and mapped drives).
• Temporarily disable playlist auto-append or remove duplicates from the playlist.
• Temporarily disable auto-play next behavior when testing.

5.2 Confirm You Are Fully Exiting PotPlayer

Some configurations keep PotPlayer running in the system tray. If you close the window but the process stays alive, your next “open” might not be a clean session restart, and your testing may produce confusing results. For accurate testing, fully exit the application each time.

5.3 Check For Multiple PotPlayer Installations Or Mixed Builds

If you have installed PotPlayer more than once (for example, a normal install plus a portable copy), you may be launching a different build than the one you configured. This can look like “PotPlayer forgot my settings” when you are actually opening another instance with different configuration storage.

To reduce confusion:

• Uninstall unused builds.
• Confirm the shortcut you use points to the intended executable.
• Configure file associations to point to the same installation you actually use.

6. When Resume Still Fails: Advanced Fixes That Often Work.

If you have enabled resume settings and confirmed PotPlayer can persist preferences, but playback position still does not return, these deeper fixes often resolve stubborn cases.

6.1 Reset PotPlayer Preferences (Then Re-Enable Resume)

Configuration drift can cause unexpected behavior, especially if you have imported settings or changed many options over time. A clean reset can eliminate a hidden conflict.

Recommended approach:

1. Back up your PotPlayer settings if you have a complex setup.
2. Reset preferences to defaults.
3. Re-enable only the key history and resume options.
4. Test resume on a local file before restoring other tweaks.

This helps you verify whether resume works in a clean configuration.

6.2 Change Where PotPlayer Stores Its Configuration (If Supported In Your Setup)

Depending on version and distribution, PotPlayer may store settings in different places (for example, user profile locations, program folder, or the Windows registry). If you are in a locked-down environment, moving configuration storage to a user-writable folder can restore persistence. The correct method depends on the build you are using, so consult the official documentation or readme for your version.

6.3 Check Whether Windows Is Cleaning Temporary Data On Restart

If you use system-cleaning utilities or enterprise policies that wipe application data, PotPlayer’s history may be deleted between sessions. If you notice that “Recent files” or other history disappears regularly, resume will usually fail for the same reason.

If you rely on cleanup tools:

• Exclude PotPlayer’s configuration/history locations from automatic cleanup.
• Disable “clear recent documents” style policies that remove app history you want to keep.

7. FAQ: Common Questions About PotPlayer Resume Behavior.

7.1 Why Does PotPlayer Remember Some Videos But Not Others?

This is usually caused by differences in how the file is opened (path mismatch), where the file is stored (network share versus local), playlist duplication, or whether the file’s location or name changes. It can also happen when settings are not being saved due to permissions.

7.2 Does PotPlayer Resume After A Crash Or Power Loss?

Resume after a crash can be less reliable than a normal exit because the player may not have a chance to write the latest position to disk. If you see failures only after forced shutdowns, test after a normal close. If that works, the fix is usually about stability and ensuring configuration writes are not blocked.

7.3 Can I Force PotPlayer To Always Ask “Resume Or Start Over?”

Some media players offer a prompt each time. PotPlayer’s behavior depends on its preferences and may vary by version. If you want a consistent prompt, look in playback or history settings for resume prompts or confirmation dialogs. If your build does not include a prompt option, consider using bookmarks for critical content you frequently revisit.

7.4 Is This Problem Caused By The Video File Itself?

Sometimes. Corrupt containers, unusual timestamps, or certain stream formats can make seeking to a precise time harder. However, most “PotPlayer not remembering position” complaints come down to history being disabled/cleared, configuration not being saved, or path differences (especially on NAS and network shares).

8. A Simple “Known-Good” Setup For Reliable Resume.

If you want the fastest route to success, aim for a setup that removes the most common failure points.

8.1 Recommended Baseline Configuration

• Enable playback history and ensure history is not cleared on exit.
• Enable playback position memory (resume) and disable “always start from beginning.”
• Store videos locally or use a consistent network path format (choose UNC or mapped drive, not both).
• Avoid duplicating the same file multiple times in playlists during testing.
• Ensure PotPlayer can write to its settings location (confirm by changing a visible setting and restarting).

Once resume works under these conditions, you can reintroduce playlists, auto-advance, network playback, and other conveniences one by one to discover what breaks it in your environment.

Citations

• PotPlayer (official product page). (Daum PotPlayer)
• Protect important folders with controlled folder access. (Microsoft Learn)
• Enable controlled folder access. (Microsoft Learn)
• App permissions and protected locations in Windows (general guidance). (Microsoft Learn)