Windows Do Not Disturb is the main control for stopping ordinary desktop notifications from appearing on a children’s 24/7 livestream. Turn it on, remove unnecessary exceptions, and use an automatic rule that matches the hours when your stream is running.
It does not block every possible banner. Alarms, reminders, and apps you have allowed can still appear, so you should inspect the actual programme output before leaving the stream unattended.
Open Windows notification settings
On Windows 11, open Start > Settings > System > Notifications. This is where you control Do Not Disturb, priority notifications, automatic rules, and notification behaviour for individual applications.
The quickest route to the manual switch is Notification Center. Select the notification area on the taskbar, then select the bell icon marked with “zZ” to turn Do Not Disturb on or off. The Settings page is still the better place for a 24/7 channel because it exposes the exceptions and automatic conditions that the quick control does not show at a glance.
Before changing anything, note which applications are open on the streaming computer. A children's channel might use OBS Studio, a media player, a browser for channel monitoring, an audio application, cloud storage, or a remote-support tool. Each may have its own notification setting, and some may show an overlay independently of the normal Windows notification panel.
Do not assume that a clean desktop proves the stream is safe. A banner may appear only when a message arrives, a licence expires, a cloud folder changes, an update completes, or a reminder becomes due. The useful test is the programme output being sent to YouTube, not the operator's view of the control screen.
If you are still deciding how the content should run, compare the responsibilities of different methods in this guide to OBS versus FFmpeg for a nonstop YouTube event replay stream. The capture method affects how much of the desktop is exposed, while Do Not Disturb controls what Windows tries to display.
Turn on Do Not Disturb
In Settings > System > Notifications, turn on Do not disturb. Windows will normally send most notifications directly to Notification Center instead of displaying them as banners while the feature is active. Microsoft describes the current behaviour in its guidance on Notifications and Do Not Disturb in Windows.
This is a system setting, not an OBS filter. It is useful when the stream computer is also used for browsing, administration, or monitoring, because it reduces the chance that a message or application alert will appear over the desktop. It remains necessary to inspect the allowed notifications, since Do Not Disturb does not mean that every notification is suppressed.
After enabling it, leave the Settings page open long enough to confirm the state. If you use the taskbar control instead, check that the bell icon shows the active state rather than assuming a previous click worked. A restart, update, or change made by another operator can alter what you find when you return to the machine.
For a channel showing a devotional loop, nursery animation, educational slides, or a quiet background scene, even a small banner can be distracting. It can also expose an account name, message preview, email subject, calendar entry, or other private information. That is why the review of exceptions matters as much as the main switch.
Do Not Disturb is most useful when paired with a narrow OBS scene. If the content is a single application, OBS's Window Capture approach may show less of the desktop than Display Capture. That link is about switching prerecorded videos, but the same distinction matters here: the fewer unrelated surfaces you capture, the fewer places a notification can appear.
Review apps, calls, and reminders allowed through
On the Notifications page, open Set priority notifications. Review every item that Windows may still allow through while Do Not Disturb is enabled.
Microsoft's documented behaviour allows banners for alarms, reminders, and apps of your choice. Remove anything that does not have a clear operational reason to interrupt the stream. A chat application, shopping application, email client, calendar, game launcher, or browser may be convenient on the computer but unnecessary in the programme output.
Calls and reminders need particular care. An operator may want a reminder that the stream needs checking, but allowing it through on the same desktop that OBS captures can put the reminder in front of viewers. If the reminder is important, use a separate device or a monitoring method that is not part of the captured scene.
If you deliberately allow an operational application, consider what it can reveal. A banner from a remote-support tool or account-management application may contain a name, ticket subject, email address, or message preview. The question is not only whether the app is trusted. It is whether the information would be suitable for a public children's channel if the banner appeared at the wrong moment.
You should also inspect notification settings for individual apps. Windows lets you disable notifications for an app entirely or turn off its notification banners while retaining entries in Notification Center. That gives you a second layer of control. For example, you might keep a browser's notification history available for the operator while stopping its banners from appearing over the desktop.
Work through the list rather than clearing it without thought. Some applications may be part of your recovery process. If a streaming or connectivity warning is useful, decide whether it can be viewed on a separate monitor or device instead. A warning that helps the operator can still be unsuitable for the audience when it appears on a captured display.
For channels that move between several prerecorded files, document the exact scene and source used for each one. The guide on making OBS switch between prerecorded videos on YouTube Live is relevant because a scene containing a media source is usually easier to control than one that exposes the whole working desktop.
| Setting or source | What it controls | What it does not prove |
|---|---|---|
| Do Not Disturb | Sends most Windows notifications to Notification Center | That alarms, reminders, and permitted apps cannot show banners |
| Priority notifications | Chooses calls, reminders, and apps that may interrupt | That an allowed app will never display private information |
| Per-app notification settings | Disables an app's notifications or its banners | That the app has no separate overlay or alert system |
| Window Capture | Captures one selected application window | That the window itself cannot display an alert |
| Display Capture | Captures the selected display more broadly | That the desktop is free of unrelated content |
Set an automatic rule for the stream schedule
Expand Turn on do not disturb automatically. Windows provides conditions including a time of day, display duplication, gaming, and full-screen app use. Choose the condition that matches how your stream actually runs, then confirm the resulting schedule rather than assuming the setting will remain active indefinitely.
For a channel that runs from a fixed evening start through the following morning, a time-of-day rule is the clearest starting point. Set the start and end times to cover the real operating window, including the period when you prepare the scene and connect the broadcast. If the channel runs continuously, the schedule still needs to be considered carefully because a daily time rule has a beginning and an end.
A time rule is not the same thing as “this computer is streaming”. Windows does not infer from the existence of a YouTube broadcast that a 24-hour protection period should begin. A stream can continue when a rule ends, and a rule can be active when OBS is not streaming. Check the state during the handover between one day and the next.
Full-screen use can be useful when the programme is deliberately run in a full-screen application, but it is not a universal solution. A media player may leave full-screen mode after an update or when a file changes. Window sizes can also change after a restart. Treat this condition as an additional convenience, not proof that banners cannot appear.
Display duplication and gaming are also activity-based conditions. They may suit a particular production setup, but they do not describe every kind of prerecorded or educational stream. Select only the rules that correspond to the way your machine is operated. More conditions do not automatically create a stronger result if the wrong condition is being relied upon.
Focus sessions deserve separate caution. Microsoft's Focus guidance explains that starting a focus session turns Do Not Disturb on automatically. A focus session is timed, however, and the session ending is not an appropriate basis for assuming that an all-day stream remains protected. Use the notification settings and automatic rule directly, then verify the state.
Write the schedule down in the channel's operating notes. Include the intended start and end, the selected conditions, and who is responsible for checking them. This is especially useful when one person prepares the content and another person checks the overnight broadcast from a different location.
Understand alarms and other exceptions
Alarms are the clearest reason not to describe Do Not Disturb as a complete block. An alarm or reminder may still appear as a banner, depending on the configuration. An app you have allowed may also interrupt the desktop. These are documented exceptions, not evidence that the main setting failed.
If the channel uses a full-screen animation, an alarm may be less visible to the operator but still be part of the captured image if OBS is capturing the display. A notification can also appear at a boundary between scenes, during a source change, or when the intended application loses focus.
Check the exceptions with the same audience in mind as the main stream. A reminder reading “renew account” or a call banner containing a contact name is not appropriate simply because it is useful to the operator. Remove it, route it to another device, or keep it outside the captured display.
There can also be visual interruptions that are not ordinary Windows notification banners. A browser page may show its own message, an application may display an update prompt, and an overlay may be drawn by software outside the standard notification system. Do Not Disturb is not a promise to hide those surfaces.
If your scene must show the whole desktop, reduce the number of applications open on that desktop. Close personal email, messaging, shopping, banking, and social applications before starting the unattended period. This is not a substitute for Do Not Disturb, but it reduces the number of possible sources of private or distracting content.
Limit what OBS captures
Windows-level suppression and OBS capture selection solve different parts of the problem. Do Not Disturb changes which notifications Windows presents. OBS determines how much of that presentation can enter the broadcast.
When the show comes from one supported application, Window Capture can be more controlled than Display Capture because it targets a single window. OBS also documents Game Capture for supported Windows games. These sources are not interchangeable in every production, so confirm that the chosen application behaves correctly with the selected source.
Display Capture has a wider scope because it captures the selected display. Use it when the programme genuinely needs the whole desktop, but understand the trade-off. A banner on that display is within the area OBS is being asked to capture.
OBS also provides Settings > General > Hide OBS windows from screen capture. This hides OBS windows from screen capture. It does not disable Windows notifications, and it does not prevent another application from showing a banner on the captured display.
A secondary display can keep OBS's control interface away from the main captured display. That may make the scene easier to manage, but it does not suppress notification banners on the display that is being captured. Treat it as a separation of controls, not a notification filter.
Before starting a children's channel, send a private or unlisted test and inspect the actual output. Trigger the parts of the workflow that might generate messages, such as opening the browser, changing a media file, or starting the scheduled task. The purpose is not to claim that one test proves every future event is safe. It is to catch an obvious exposure before viewers see it.
Recheck after updates, restarts, and handovers
Add a notification check to every restart and update procedure. Open Settings > System > Notifications, confirm Do Not Disturb is active when it should be, and review the automatic rule. Then open Notification Center and verify the visible state rather than relying on memory.
Check the OBS scene as well. Confirm that the intended source is still selected, the capture is aimed at the correct display or window, and the scene has not reverted to Display Capture after a change. If the computer has more than one monitor, confirm which display is being captured.
A Windows update can change menu wording or introduce a different arrangement of settings. The available controls and their labels can vary by installed build. If you maintain instructions for a Windows 10 machine, label them separately from Windows 11 instructions. Microsoft says Windows 10 support ended on 14 October 2025, so a current production computer should be assessed for a supported operating system rather than treated as permanently suitable.
Restart the machine before an unattended handover when your normal process allows it. After it comes back, wait for the required applications to open, confirm the schedule, and inspect the programme output. A machine that restarted cleanly is not necessarily a machine with the intended notification state.
Keep a short checklist near the streaming computer:
- Do Not Disturb is active or the automatic rule is due to activate.
- Priority calls, reminders, and apps have been reviewed.
- Personal and unnecessary notification sources are closed or disabled.
- OBS is using the intended source and display.
- The private preview shows only the programme.
- The next operator knows when to repeat the check.
If the stream depends on a local computer remaining powered and connected, notification control is only one part of the operating risk. For another common failure point, see how to keep a podcast YouTube Live stream running during power cuts in India. For a simpler workflow, StreamNeo removes the need to leave the streaming computer running: upload the video, provide the YouTube stream key, and verify the broadcast from the output rather than relying on a desktop that can display unrelated alerts.
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 Do Not Disturb block every notification on Windows?
No. Most notifications are sent to Notification Center, but alarms, reminders, and apps you have allowed can still show banners. Review priority notifications and test the actual OBS output before leaving the stream unattended.
Will a 24-hour YouTube stream automatically turn on Do Not Disturb?
No. Windows does not automatically activate Do Not Disturb merely because a YouTube broadcast is running. Set an appropriate automatic rule and verify its state after starting, restarting, or updating the streaming computer.
Is Window Capture safer than Display Capture for OBS?
Window Capture can limit OBS to one application window, while Display Capture covers the selected display more broadly. It is not a universal guarantee, because the captured application can still show its own prompts or overlays and the correct choice depends on the programme.
Can hiding OBS windows hide desktop notifications?
No. OBS's “Hide OBS windows from screen capture” setting hides OBS windows from capture. It is not a system-wide notification filter, so Windows Do Not Disturb and the review of allowed apps are still needed.