Is it OK to run Windows Update on my local SnapStream Systems?
Yes. Periodically installing Windows Critical Security Updates are encouraged. However, please keep our best practices in mind when installing Windows Updates.
- We suggest that each SnapStream System NOT be set to install windows updates automatically. Doing so can cause the SnapStream systems to automatically reboot on occasion, and cause unexpected interruptions in your recording schedule. This is why Windows auto-update is disabled by default.
- Schedule time to install critical security updates. We just suggest that you make plans to implement them so that these Windows Update installations don't cause unexpected interruptions in your recording schedule.
- It is best to shut down the SnapStream Software before running Windows update. This can be done by following the instructions below.
- Stop the, "SnapStream Broker Service". This can be done by going to Start > Run: Services.msc.
- Go to the Properties of the SnapStream Broker service, and set Startup Type to Manual.
- Run all of your Windows Updates normally.
- When done, make sure to go back to Services.msc, Start the SnapStream Broker Service, and set the Startup Type back to Automatic.
- Avoid installing optional driver updates. Changing the drivers on your system can create unforseen issues, and we would prefer that the SnapStream Environment be running a known and tested configuration.
- Always test SnapStream functionality when Updates are complete.
Windows 10 version updates can cause the Web Interface to stop working. This can be fixed by following the instructions in Unable to connect to the SnapStream WebUI after running Windows 10 Version Update.
SnapStream encoders (RF tuning and component/HDMI) shipped after April 2018 run Windows 10 IoT. This version of Windows 10 does NOT receive Windows version updates, as described above, via Windows Update. Version updates for Windows 10 IoT should NOT be installed manually on SnapStream encoders. Security updates can be installed as normal according to best practices described above.
To avoid unneccesary SnapStream Warnings, you may want to take our Best Practices for Shutting Down Local SnapStream Systems in to account.