A Windows update is a useful time clue when OBS media disappears, but it does not establish that Windows caused the problem. First check that the file still exists and its drive is reachable; then compare the current path with the one saved in OBS and repair the reference if needed.
OBS Media Sources point to local audio or video files. If a source cannot find its file, the cause may be a disconnected volume, a changed drive letter, a moved folder, or another path change. The reliable approach is to trace those possibilities in order, then keep future media in a location that remains consistent across restarts.
Check whether the media file is missing
Start outside OBS. Open File Explorer and browse to the folder where the affected media should be. Check the exact file rather than assuming that a source is broken because its preview is blank. A file may have been renamed, moved into another folder, or deleted during ordinary housekeeping; those situations can look the same inside a scene.
If you know the file name, search the computer or the relevant drive. When you find it, note its full path: for example, D:\\StreamMedia\\opening.mp4. Do not rely only on the folder name displayed in a shortcut or recent-files view. You need to know which volume and folder OBS is expected to read.
If the file is present and opens in a media player, that is useful evidence that the file itself is readable. It does not yet prove OBS has the right reference, so keep the current path available for comparison. If the file is not found, check other likely folders and any backup or archive location before changing the OBS source.
The update date can help you decide when to investigate, but avoid treating it as a diagnosis. OBS says its updates should leave settings intact and notes that other software can interfere after an update. The available guidance does not establish that Windows updates generally make OBS media go offline. If other OBS functions also stopped working, consult the OBS update troubleshooting guidance; a missing local file still deserves a file-and-path check first.
Confirm the drive is connected
If the media lives on a USB drive, external SSD, secondary internal drive, or network-backed location, make sure that location is available to Windows. Reconnect a removable drive directly, wait for it to appear in File Explorer, then browse to the file. If Windows cannot open the volume, OBS cannot resolve a path on it either.
A drive can be physically connected yet unavailable at the path OBS expects. Check that it appears in File Explorer and that you can open the relevant folder. If the drive is encrypted or requires a sign-in or unlock step, complete that before launching OBS. For a shared location, confirm that the computer is connected to the network and that the account in use can reach the folder.
Avoid moving files or reformatting a drive while troubleshooting. Those actions can create more path changes or affect other applications that use the volume. If Windows reports a disk problem, address that separately and preserve a copy of important media before attempting repairs. The immediate question is simple: can Windows browse to the file right now?
This check also matters for a channel that uses a dedicated streaming PC. A machine may restart overnight, while a removable volume is absent or mounted differently after boot. For a broader checklist on keeping a computer focused on a continuous broadcast, see ways to limit memory use on a 24/7 streaming PC. That is a different failure class, but both checks begin with confirming what the computer can access after a restart.
Check for a changed drive letter or path
Once Windows can see the file, compare its current full path with the location the OBS source used before. A source that referred to E:\\Audio\\bed.wav will not automatically find the same file if the drive now appears as F:. Likewise, a file moved from D:\\StreamMedia to D:\\Archive\\StreamMedia is still present, but its old path no longer resolves.
To inspect a source, open the scene that uses it, select the Media Source, and open its properties. The Local File field shows the file reference. OBS documents Media Sources as a way to add local audio or video files to a scene, with the file set in that source's properties. See the OBS Media Sources documentation for the source controls and supported file types.
Write down or copy the path currently in the source before editing it. Then compare it with File Explorer's current location. If only the drive letter differs, the likely issue is the mounted letter. If the letter matches but a folder differs, the file or folder may have been moved. If the path appears identical but the source remains unavailable, verify spelling, file extension, and whether the selected file is the one that should play.
Do not infer a drive-letter change just because the problem appeared after an update. Windows may assign a different letter when volumes are added, removed, or otherwise enumerated, but the timing alone does not show that this happened here. Confirm the letter in File Explorer or Disk Management and compare it with the saved OBS path.
Restore the path or relink the source in OBS
There are two sensible repair routes. If other software also expects the original location, restore that location where practical. If the file has intentionally moved and OBS is the only thing pointing to its old location, update the source to the new file. Either route can work; choose based on which path is least disruptive to the rest of the setup.
OBS includes a missing-files workflow. Its interface can report that files are missing since OBS was last used, and provides controls such as Search Directory... and Select file... to locate replacements. Search the folder that now contains the media, or select the correct file directly. Check the file name and destination carefully before applying the repair, especially if several versions have similar names.
For a single source, you can also open its properties and use the file selection control next to Local File to browse to the current file. Confirm the chosen path, apply the change, and watch the preview. If a source is part of a scene collection with several missing files, use the missing-files interface to find them as a group where possible rather than opening every source blindly.
If the expected drive letter changed, restoring the previous letter may repair multiple sources at once. Only do this if that letter is available and you understand whether other programs rely on the current assignment. Alternatively, relink sources to the new letter. A bulk change may save time, but it also risks creating another mismatch later if the new assignment is not stable.
For a channel assembled from recorded tracks, keeping the folder and references understandable makes repairs easier. The guide to running a nonstop YouTube radio stream from recorded tracks covers the wider media workflow; here, the important detail is that every file-based source depends on a path Windows can resolve.
Choose a stable media location
The simplest prevention is to keep broadcast media in a deliberate folder on a volume that remains connected and mounted consistently. Avoid scattering source files across Downloads, temporary folders, removable devices that are regularly swapped, and user folders that may be reorganised. A folder such as D:\\StreamMedia is only stable if the D: volume and folder remain available at that same path.
For removable storage used with portable OBS on more than one PC, an OBS Project forum guide recommends assigning the drive the same letter on each PC. That approach keeps references consistent across those machines, but it depends on the chosen letter remaining available. The guide is older community guidance, so check the current Windows controls and your own multi-PC arrangement before changing assignments.
Windows also supports mounting a volume at a folder path rather than relying on a drive letter. Microsoft documents methods through Disk Management, command line, and PowerShell, and specifies that a folder mount point requires a volume formatted as NTFS or ReFS. This can make a path such as C:\\MediaVolume available even though the storage is a separate volume. It adds setup and maintenance, so use it only if you are comfortable managing mount points and checking the result after a restart.
| Path approach | Useful when | Trade-off to check |
|---|---|---|
| Consistent drive letter | Removable media is used across PCs and each can use the same letter | The letter must remain available on every machine |
| Folder mount point | You want a folder-based path for a separate volume | Windows requires NTFS or ReFS for the mounted volume, and setup is less familiar |
| Local folder on a fixed volume | One streaming PC uses a stable, always-present disk | The disk and folder still need to remain at the saved path |
A dedicated external SSD is not automatically a fix. It can be a convenient place to keep media together, but if it is disconnected or assigned a different path, OBS can still lose access. Choose storage for the way you operate, and make its mount location part of the routine you check after a restart.
For a wider view of how a prerecorded channel is assembled and what to prepare before going live, read whether a new YouTube channel can run a 24/7 prerecorded livestream. It does not replace local path checks: any computer-based workflow still depends on the media being where its sources expect it.
Test sources after relinking
After repairing a path, test every affected source in the scene where it is actually used. Select the scene, confirm the media appears in the preview, and start or restart playback as appropriate for the source. For audio, check that the audio meter responds and that the intended sound is audible at a sensible level. A visible image alone does not confirm that an audio source is working.
If a source is set to loop, test that behaviour too. If it is a short transition, check the point in the scene where it should appear. The practical aim is not merely to clear a missing-file warning, but to confirm the source behaves as your broadcast needs it to. A valid path can still point to the wrong version of a file.
Save the repaired scene collection, close and reopen OBS, then revisit the scene. This is a useful check that the reference persists rather than relying on an unsaved change in the current session. If the file is on external storage, test again after a normal restart with the drive connected in the intended way.
Keep a short record of the media folder and any non-default drive assignment. If you have several scenes, note which ones use the same files. That gives you a practical recovery map if a drive is later swapped or a folder is reorganised. When a broadcast is important, test the scenes before the next scheduled run rather than discovering the broken source during it.
When the path is not the only problem
If Windows can open the file and OBS points to the correct path, consider whether the source itself or the file format is the issue. Confirm that you selected the intended file and that it is a type supported by the Media Source. OBS lists common video formats including MP4, TS, MOV, FLV, MKV, AVI, GIF, and WebM, and audio formats including MP3, AAC, OGG, and WAV. Do not convert or replace a file until you have ruled out a wrong selection or a path typo.
If several unrelated OBS features fail after an update, treat that as a broader application problem rather than a media-path diagnosis. OBS's help guidance discusses possible interference from other software, including security software scrutinising an updated application. This does not show that security software changed a media path. Check the official troubleshooting advice and any relevant allow-list settings without assuming that they explain a missing local file.
A local file repair also does not guarantee that a 24/7 broadcast will continue without interruption. You still need to consider playback, OBS operation, the computer, and the YouTube connection. The article on why YouTube may end a 24/7 live stream concerns a different point in the chain: it can help separate a source-file issue from a platform or broadcast interruption.
Keeping a channel running when the computer is the weak point
For an OBS setup, local files must remain reachable by the computer running the scene. That is appropriate when you want direct control over OBS sources, transitions, and other parts of a production. It also means a computer restart, an unavailable drive, or a changed path can require attention before the source plays again.
If your actual difficulty is that the streaming computer must stay on to deliver a file-based channel, StreamNeo removes that specific always-on-computer burden by turning an uploaded video into a YouTube live stream that runs with your computer switched off. That does not repair OBS paths or apply to non-YouTube platforms; it is a separate workflow to consider when the media is ready and the aim is a continuous YouTube broadcast.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why are my OBS media files missing after an update?
The timing tells you when you noticed the problem, not necessarily what caused it. Check that the file still exists, the drive is available, and the current path matches the one in the OBS source before blaming the update.
How do I relink a missing file in OBS?
Use OBS's missing-files workflow to search the directory or select the replacement file, or open the affected Media Source and choose the correct file in its Local File setting. Then test playback in the scene and save the repaired scene collection.
Why did my OBS drive letter change?
A drive letter is a Windows mount location, and the one assigned to a volume may not be the one stored in an OBS source. Compare the letter shown in File Explorer or Disk Management with the path in the source; do not assume an update changed it without checking.
Is a folder mount point better than a drive letter?
It depends on how you use the media. A consistent drive letter is straightforward for removable storage used across PCs, while a folder mount point gives a folder-based path but requires setup and an NTFS- or ReFS-formatted volume. Choose the path you can keep consistent and verify after a restart.