A promo playlist stopping after a Windows update does not, by itself, show that the update caused it. First establish whether OBS stopped playing media while the broadcast continued, or whether YouTube ended the broadcast; those are different faults with different checks.
For an OBS playlist, check the source type, its loop and visibility settings, and whether VLC is still installed if the source is a VLC Video playlist. Then review Windows restart behaviour and test the whole chain before the next public broadcast. These checks can reduce avoidable interruptions, but no setting can prevent every interruption.
First establish what stopped
Look at the symptom before changing settings. If the YouTube watch page or Studio preview remains live but the promo image freezes, goes black, or changes to another scene, the broadcast may still be running while OBS playback or scene content has changed. If Studio reports that the stream ended, or the live page is no longer receiving a broadcast, investigate the broadcast path as well as the playlist.
When possible, observe both OBS and YouTube Studio during a test. In OBS, note whether the source is still present in the Sources list, whether its preview is moving, and whether the intended scene is selected. In Studio, check whether the event is live and whether its preview continues. A single frozen frame can be a display issue; compare what the viewer sees with OBS's preview and Studio status before concluding that playback has stopped.
Write down the time and what you observed: update installation or restart, OBS still open or relaunched, scene visible, source preview moving, and Studio live status. This modest record is more useful than assuming the update is responsible. The evidence reviewed for this specific symptom documents OBS source controls and YouTube event controls, but does not establish that Windows updates cause promo playlists to stop.
If the event itself ended, check the scheduled broadcast's settings in YouTube Studio. YouTube's live control room guidance describes event controls including auto-start and auto-stop. Those settings affect broadcast behaviour; they do not make an OBS media source repeat. Keep the two layers separate during diagnosis.
For broader Windows restart planning, see how Windows Update can interrupt a 24/7 YouTube stream. That is a related but separate concern: avoiding an unexpected PC restart does not fix an incorrectly configured playlist loop.
Identify the OBS source you are using
OBS has different source types for a single file and a multi-item playlist. A Media Source is appropriate for one local video or audio file and has its own Loop option. For a list of multiple files, OBS documents the VLC Video source, which relies on VLC being installed. The OBS media sources guide explains these source types and their controls.
In OBS, select the scene used for the broadcast and inspect the Sources list. Right-click the promo source and open Properties. The dialog title and available controls help identify whether you are looking at a Media Source or VLC Video source. Do not infer the type only from the name shown in the Sources list: operators can name a source “Store promos” regardless of its underlying type.
| What you need to play | Likely OBS source | Control to check | Main trade-off |
|---|---|---|---|
| One promo file repeatedly | Media Source | Loop |
Simple setup, but it plays only that file |
| Several promo files in sequence | VLC Video | Loop Playlist |
Supports a list, but requires VLC and correct playlist paths |
| Several promos with a particular order | VLC Video | Playlist order and Shuffle Playlist |
Shuffle changes sequence, so leave it off when order matters |
Use the source that matches the job rather than adding controls to the wrong source. If a single video ends and stays ended, check the Media Source's Loop option. If several promos play once and stop at the end of the list, check VLC Video's Loop Playlist option. OBS's source guide is useful when the current scene contains unfamiliar or duplicated sources.
Changing source type mid-broadcast can create a new problem, particularly if the scene has filters, transforms, audio routing, or overlays attached to the existing source. Duplicate the scene or save a copy of the profile before a structural change. Then verify the replacement in preview before putting it on air.
Check the file and playlist repetition controls
For a Media Source, open Properties and confirm that the intended local file is selected and Loop is enabled if it should repeat indefinitely. A source can appear in the scene even when its file path points to a file that was moved, renamed, or stored on a drive that is unavailable. Browse to the actual file again if the path is missing, and confirm playback in preview.
For VLC Video, inspect the playlist entries and confirm the files still exist at those locations. Then enable Loop Playlist if the list should start again after the last item. OBS documents that this option controls whether the source restarts after it runs out of media files. Shuffle Playlist is independent: it changes item order, not whether the list repeats. If a daily offer, legal notice, or price card must appear in a prescribed order, leave shuffle disabled and test the sequence.
A list that ends normally and a file that fails to load can look similar in a quick glance. Watch the end of a test run: does the last item finish and then the first item begin, does playback go black before restarting, or does an error occur as soon as a particular item is reached? Test the files one at a time if the fault follows a particular entry. This helps distinguish loop configuration from a broken path or unreadable media file.
Also check whether the source is actually visible in the active scene. VLC Video's Visibility Behaviour setting controls what happens when the source becomes hidden, such as when you switch scenes or hide the source. Depending on the selected behaviour, playback can continue, pause, or stop. If your promo scene is sometimes hidden behind a holding scene, choose and test the behaviour that matches the intended transition rather than assuming the playlist has reached its end.
For a single-file loop that ends with a black frame or behaves unexpectedly, the specific OBS media-source loop troubleshooting guide may help you focus on that source. A separate guide covers preventing a YouTube live loop from ending when its source file finishes; use it when the issue involves the broadcast ending rather than only a source ceasing playback.
Verify VLC is present and matches OBS
A VLC Video source depends on VLC; OBS does not replace that dependency. If an update coincided with a VLC removal, repair, or version change, the playlist source may no longer behave as before. That is a possibility to verify, not evidence that Windows Update performed the change. Check whether VLC opens on the PC and whether the playlist source still lists and plays its files.
Architecture matters. OBS's documented guidance is to use 64-bit VLC with 64-bit OBS. If your OBS installation is 64-bit, confirm the VLC installation is also 64-bit. Having VLC appear in the Start menu is not enough to confirm that the expected architecture is available to OBS. If uncertain, check the About information in each application and compare them before reinstalling anything.
Avoid downloading installers from search-result ads or unofficial download sites. Use the official VLC project page for its current installer, and check the OBS documentation if the source still cannot initialise. OBS's media source documentation describes the VLC Video dependency. Reinstalling software is a reasonable repair step only after confirming what is missing or mismatched; otherwise it can add a second variable without resolving the cause.
Once VLC is available, reopen the OBS scene and inspect the VLC Video properties. Confirm the playlist has retained its entries, loop selection, shuffle selection, and visibility behaviour. A source can retain its name and position in a scene even when one of its files or a required application is no longer available.
Review update timing and restart behaviour
An update may be a useful clue because it can be followed by a restart, a sign-in prompt, a change in which applications launch, or a period when OBS was not running. But timing alone does not establish causation. Look for evidence in Windows Update history and Reliability Monitor, and compare the time of a failure with the system restart and OBS launch. If playback stopped while the PC remained on and OBS remained open, a scheduled restart is less likely to explain the immediate symptom than source configuration or file access.
For a computer dedicated to a live channel, review Windows active hours and restart notifications, and schedule maintenance at a time when the channel can tolerate interruption. Keep the machine connected to power and confirm that OBS launches after a planned reboot if your operating routine depends on it. Automatic sign-in and application launch choices have security implications, so weigh unattended recovery against who can physically access the computer and what accounts it can reach.
Check whether the promo files live in a user folder, removable drive, network location, or synchronised directory. A reboot can expose a dependency on a drive letter or a sign-in session even if no file has been deleted. Prefer a stable local path for the media used in a continuous broadcast, and verify that the account running OBS can read it after a restart. This is a diagnostic recommendation, not a claim that Windows moved or removed the files.
Do not disable updates as a blanket fix. Security updates still matter, and suppressing them indefinitely can leave a broadcast computer exposed. Instead, plan restarts, apply updates during a controlled window, then run the post-update checks below. If Windows reports a restart pending, treat that as an operational warning and decide whether the stream can be interrupted before accepting it.
Test playback and monitor the broadcast
After a system update, restart, VLC repair, or OBS change, test the same scene and source that will be used publicly. First preview locally: start playback, confirm the image and audio, and watch long enough to reach the end of a playlist cycle when practicable. Confirm that the first item returns if repetition is expected and that the correct visibility behaviour applies when switching scenes.
Then use a private or unlisted YouTube test event where suitable, following YouTube's current options for the channel and event. Confirm that Studio receives the stream, the viewer-side picture and sound are present, and OBS playback continues independently. If you need to validate a scheduled event's auto-start or auto-stop behaviour, inspect the event settings in Studio rather than trying to infer them from OBS's loop controls.
Make one change at a time and write down the result. If the issue disappears after restoring a missing VLC installation, that supports a dependency explanation; if the source preview continues but Studio says the event ended, investigate broadcast settings or connection state instead. A single successful test does not prove that an interruption can never recur, but it can catch common configuration problems before a long unattended run.
During a live run, keep a way to notice loss of signal or a frozen source. Periodically compare the OBS preview with the public or private viewer and Studio status, especially after a planned restart. For a small shop displaying the same offers overnight, the practical question is not merely whether the loop checkbox is ticked, but whether the media, active scene, broadcast event, and PC all continue to do their separate jobs.
If repeated overnight checks are difficult because the PC must remain powered and logged in, StreamNeo removes that specific dependence on a local computer: you upload the video, provide the YouTube stream key, and the broadcast runs with the computer switched off, with monitoring and automatic restart if it drops. It is YouTube-only, so it is not a solution if you need this OBS setup for other platforms or a complex live production.
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
Does a Windows update cause an OBS promo playlist to stop?
The timing can make an update worth checking, but the available official documentation does not establish it as the cause of this exact problem. Determine whether OBS playback stopped, the PC restarted, a file path became unavailable, or YouTube ended the broadcast before attributing the fault.
Which setting makes an OBS playlist repeat?
For one file in a Media Source, check Loop. For multiple files in a VLC Video source, check Loop Playlist. These are separate source types and controls; YouTube's auto-stop setting does not make either source repeat.
Why does my VLC playlist stop when I change scenes?
Check VLC Video's Visibility Behaviour setting and whether the source becomes hidden when the scene changes. OBS provides options governing whether playback continues, pauses, or stops when the source is not visible, so test the selected behaviour with your actual scene transitions.
Does OBS need VLC installed for a multi-file playlist?
Yes. OBS documents VLC Video as requiring VLC to be installed, and 64-bit OBS should use 64-bit VLC. Confirm the application and architecture, then reopen the source properties and verify that the playlist paths still work.