A Windows restart can launch OBS and ask it to start streaming, but it cannot guarantee that YouTube is configured for the right broadcast or that the network is ready. The key is OBS’s --startstreaming launch parameter, paired with a scheduled task whose Start in directory points to the folder containing obs64.exe.
Set up the YouTube stream and encoder settings first, then test the whole sequence on the machine you intend to use. A task that starts OBS is only one step; you still need to check the preview and confirm the broadcast in Live Control Room.
What a Windows restart can and cannot automate
When Windows starts again, it can run a scheduled task or a shortcut after a user signs in. That can open OBS with an instruction to begin streaming. It does not create a YouTube event, choose the correct event in every setup, supply a working network connection, or prove that viewers can see the broadcast.
This distinction matters after a power cut or an operating-system update. Windows may return before the network connection is ready, and OBS may launch while YouTube is unavailable or while the encoder settings do not match the broadcast you intended. The launch instruction is not a recovery guarantee.
There are two common ways to start OBS. A Startup-folder shortcut is a straightforward choice when you only need it to launch after a user signs in. Task Scheduler is more configurable: it lets you choose a trigger and conditions, and makes the Start in working-directory field available. Neither approach, on its own, verifies that a stream has reached YouTube.
| Launch approach | Useful when | Points to check |
|---|---|---|
| Startup-folder shortcut | OBS should launch in the usual signed-in user session | Test the shortcut on the actual account and machine; confirm its working directory if the shortcut provides that field |
| Task Scheduler | You need control over the trigger, delay, or conditions | Set the program, arguments and Start in directory separately; test the chosen sign-in and restart behaviour |
For a channel that must keep running unattended, an OBS-on-Windows task is still dependent on that PC, its power, the signed-in session and its internet connection. If keeping a home computer running is the problem rather than a Windows restart, the guide to running a 24/7 YouTube bhajan livestream without keeping a PC on covers a different operating model.
Configure the YouTube encoder stream first
Before adding an automatic launch, open YouTube Studio and prepare the live stream you expect OBS to feed. In YouTube’s explanation of stream settings and stream keys, the key is the credential that tells an encoder where to send its video. Treat it as private: do not put it in a script, share it in a screenshot, or include it in a public troubleshooting post.
In OBS, select the intended YouTube service and enter the stream key for that stream. Check the selected video source, audio devices, output settings and scenes while you are at the computer. A successful OBS launch cannot correct a wrong key, a missing source or a scene that only shows a blank display.
YouTube also has auto-start and auto-stop choices for a stream. Check the current settings for the event you are using and understand whether the encoder can start the broadcast as soon as it sends a feed, or whether you need to start the event separately. YouTube notes that those selections carry over when stream settings are reused, so do not assume a new event has inherited the behaviour you want.
This is also the point to decide whether you want a persistent stream key or a key associated with a particular event, according to the workflow YouTube currently offers in Studio. Keep the destination unambiguous. If you manage several channels or recurring events, label your own notes by channel and event rather than relying on memory after an overnight restart.
Before automating anything, make a normal manual test: start OBS, connect it to YouTube, inspect the preview and confirm the intended event is receiving video and audio. YouTube’s encoder setup instructions walk through creating a live stream with an encoder. Once this path works manually, the scheduled launch can reproduce the OBS start action; it cannot substitute for this configuration work.
Add --startstreaming to the launch task
OBS documents --startstreaming as a launch parameter that automatically starts streaming. Its launch-parameters page also specifically addresses automated Windows launches and the working directory. Use the documented parameter rather than assuming that opening OBS normally will start the broadcast.
In Task Scheduler, create a task with a trigger that matches your intended recovery. For an ordinary restart, that may be a sign-in trigger for the Windows account that runs OBS. Configure the action to start the OBS executable, put --startstreaming in the arguments field, and set the working directory as described in the next section. The exact choices depend on whether OBS should run only in a signed-in desktop session and on how your PC is used.
Do not confuse a trigger with a successful stream. The trigger means Windows attempted to run the action; it does not tell you that OBS opened the expected profile, connected to YouTube, or started the correct event. If OBS prompts for a profile or a confirmation on launch, resolve that during a manual test. A prompt that blocks the interface can leave the task technically successful while streaming has not begun.
You can instead use a shortcut in the user’s Startup folder if the simpler sign-in flow suits you. Add the same launch parameter to the shortcut’s target after the executable path, preserving the path’s quotation marks. OBS’s documented working-directory guidance remains relevant to automated launches; verify the shortcut’s Start in field rather than relying on the folder Windows happens to choose.
Use one launch mechanism at first. Running both a startup shortcut and a scheduled task can open OBS twice, trigger a second instance warning, or create confusing results. Make one change, restart, observe what happens, and only add extra conditions if the test exposes a need for them.
Set the task working directory
The working directory is easy to miss because Task Scheduler separates it from the executable path and arguments. OBS’s guidance is to set the working directory—the Start in value—to the directory containing obs64.exe for a scheduled or otherwise automated Windows launch. This is not the full path to the executable; it is the folder that contains it.
To find the correct folder, locate the OBS shortcut you normally use, open its properties and inspect the target path, or locate obs64.exe directly. The installation location can vary, so do not copy a path from another computer or assume a particular drive. If the executable is in a folder such as C:\Program Files\obs-studio\bin\64bit, use that folder as Start in only if it is where your own obs64.exe resides.
In Task Scheduler’s action, keep the fields conceptually separate:
- Program/script: the complete path to
obs64.exe. - Add arguments:
--startstreaming. - Start in: the containing folder, with no executable filename at the end.
If the path contains spaces, preserve the quotation marks around the executable path in the appropriate field. Do not put the launch argument inside the Start in value. After saving, inspect the action again: a small field-placement error can mean Windows opens nothing or OBS starts without the intended parameter.
A working directory is not a YouTube setting and cannot fix a bad stream key. It gives the application the launch context OBS documents for automated starts. Once the task is saved, run it manually from Task Scheduler while you are present, then check that OBS opens and the stream attempt behaves as expected before relying on a restart.
Check account and power conditions
A scheduled task runs under an account and conditions that affect what it can do. Use the Windows account that has the working OBS installation and the profiles, scenes and media sources you configured. If you choose a setting that requires the user to be signed in, plan for that: a machine that reboots overnight and waits at a sign-in screen may not run the task as you expect.
Task Scheduler offers conditions related to power and idle state. Read them carefully. A condition that is sensible for a laptop may prevent a desktop stream from starting after a power interruption, while disabling every condition without understanding the effect can produce unwanted launches. The right choice depends on whether the PC is a dedicated streaming machine or a computer used for other work.
Also consider what happens if OBS is already open when the trigger fires. Test the behaviour rather than assuming the task will reuse the existing instance cleanly. Keep the task’s action and trigger simple until you have seen how your installed OBS version and Windows account behave together.
If your broadcast uses local video or audio files, check that their paths remain available to the account running the task. A source that works in your desktop session may be unavailable if it points to a removable drive that is disconnected after reboot. For a file-based channel, the guide to streaming a Telugu podcast archive on YouTube Live nonstop is useful context for planning source files and continuous playback.
Test restart, network return and preview
A real restart test is more useful than simply clicking Run in Task Scheduler. Save your OBS profile, make sure the intended YouTube event is prepared, and note what a healthy manual stream looks like. Then restart Windows at a time when you can watch the recovery and stop the stream if it is wrong.
Observe the stages separately. First, does Windows return to the expected account or desktop? Next, does the task run and open the intended OBS profile? Does OBS show the expected scene and audio meters? Then, does it connect to YouTube and send a preview? Finally, does the broadcast become live in the way your event settings specify? A failure at any one stage needs a different fix from the others.
For a more realistic test, interrupt the network before the restart or delay reconnecting it, if that is safe for your setup. A task may start before Wi-Fi or the router has restored internet access. YouTube’s streaming tips explain that a connectivity disruption can break a stream and recommend upload bandwidth headroom; where you use backup encoder capacity, its guidance calls for primary bitrate plus backup bitrate plus 20%. That is a recommendation, not a promise that a marginal connection will recover.
If the first connection attempt fails, do not infer that --startstreaming will keep retrying until it succeeds. OBS community discussion of startup after a reboot describes initial connection failure as a case where auto-reconnect may not work as hoped. Treat that as a failure mode to test on your particular installation, not as a guarantee about every OBS setup. Check the OBS log and YouTube status, restore the network, and determine whether a manual retry is needed.
Do not test only once immediately after configuration and then assume every update or outage will behave identically. Repeat after a Windows or OBS change that affects startup, and after changes to the account, profile, event or network. Keep a short record of the date, what you restarted, and whether the preview and event recovered. That gives you a practical reference without turning one successful test into an uptime claim.
Verify the broadcast in Live Control Room
OBS showing a streaming state is not the final check. Open YouTube Studio’s Live Control Room for the intended event and confirm that YouTube is receiving the feed. Inspect the preview for the right picture, and listen for audio if you can. YouTube advises checking the preview before streaming and monitoring audio and video quality; its computer live-streaming guidance is a useful checklist for this part of the test.
Confirm the event status and audience access using the settings you chose. If the preview is missing, stale or belongs to a different event, pause before assuming viewers can see the correct broadcast. A stream key routes an encoder feed, but event selection and the live status still need to be checked in YouTube Studio.
For recurring or always-on content, decide how someone will notice a failure when nobody is at the PC. A local OBS window is not a remote alert. If the specific difficulty is checking a stream while away from the streaming computer, the guide to monitoring a cloud-hosted YouTube livestream when your PC is off discusses that separate monitoring problem.
An unattended Windows task can be the right fit when you already use OBS on a dedicated, dependable PC and can test its behaviour. If the requirement is that the channel continue while your own computer is switched off, StreamNeo removes that particular burden by taking an uploaded video and running it as a YouTube live stream without leaving your computer on. It does not change the need to prepare your content and verify the YouTube channel and 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
Will --startstreaming make OBS go live after every Windows restart?
It tells OBS to start streaming when launched with that parameter, provided OBS can start and the configured stream is usable. It does not guarantee that YouTube has the intended event ready, that the network has returned, or that the connection will succeed. Test the complete restart path on your own machine.
Where should I put the OBS working directory?
Use the folder containing obs64.exe as the Task Scheduler Start in value. It is a folder path, not the path to the executable itself. The location varies by installation, so check the target on the PC you are configuring.
Should I use Task Scheduler or the Startup folder?
A Startup-folder shortcut can suit a simple launch after a user signs in. Task Scheduler is more useful when you need control over triggers or conditions. In either case, test the account, launch argument, working directory and YouTube preview rather than assuming the launch itself proves the stream is live.
What should I check if OBS opens but YouTube shows no preview?
Check that OBS has the intended profile, source and stream key, then confirm the selected event and its settings in YouTube Studio. Check whether internet access had returned when OBS made its first connection attempt. If necessary, restore connectivity and retry manually; the launch parameter does not guarantee recovery from a failed initial connection.