FAQ
Answers to common questions about SCOS Standard, SCOS Builder, installation, requirements, compatibility, and current beta limitations.
SCOS is independent and not affiliated with Microsoft, Valve, Steam, or any third-party launcher.
General
What is SCOS?
SCOS Standard is a Windows-based Steam console environment. It turns a fresh Windows installation into a controller-first living-room experience built around Steam Big Picture / Steam Gamepad UI.
Is SCOS a new operating system?
SCOS installs as a separate Windows-based console environment created from a Windows ISO. It is not a program that tweaks your existing Windows installation.
Does SCOS include Windows?
No. SCOS does not include, provide, sell, or activate Windows. You must provide your own official Windows ISO, and Windows activation remains separate from SCOS.
What is SCOS Builder?
SCOS Builder is the tool used to create a SCOS installation ISO from your own Windows ISO. It downloads the official SCOS Build Package from GitHub, injects the setup files, and rebuilds the final bootable SCOS ISO.
What’s the goal of SCOS?
The goal is to deliver a console-style living-room gaming experience while keeping the compatibility advantages of Windows for games, launchers, drivers, and anti-cheat systems that expect Windows.
Who is SCOS for?
SCOS is for players who want a Windows-powered Steam console experience on a TV, especially when they want native Windows compatibility instead of relying only on Linux/Proton compatibility.
Download & SCOS Builder
Where do I download SCOS?
Download SCOS Builder from the official GitHub release page. The website Download button opens the GitHub release page so you can read the notes and download the correct release asset.
Which file do I download on GitHub?
On the release page, download the SCOSBuilder_v0.1.3.zip asset, extract it, then run SCOSBuilder.exe.
Can I download the final SCOS ISO directly?
The current public flow uses SCOS Builder. You provide your own Windows ISO, then SCOS Builder creates the final SCOS installation ISO locally.
Why use GitHub instead of a direct ZIP link?
GitHub release pages show release notes, requirements, assets, and future checksums or hotfixes. This is safer and clearer for a public beta.
Requirements
What do I need to run SCOS Builder?
You need Windows 10 or Windows 11, the matching .NET Desktop Runtime, Windows ADK Deployment Tools, an official Windows ISO, and an internet connection.
Which Windows ADK option do I need?
During Windows ADK installation, only Deployment Tools is required. SCOS Builder uses oscdimg.exe from Deployment Tools to rebuild the final ISO.
Do I need Windows 11 TPM / Secure Boot requirements?
For Windows 11-based SCOS builds, the target device should meet the official Windows 11 requirements, including TPM 2.0, Secure Boot-capable UEFI firmware, and at least 4 GB of RAM.
Can I bypass Windows 11 requirements with Rufus?
Officially, no. For SCOS ISOs, leave all USB creation customization options unchecked. SCOS already includes its own setup configuration, and extra modifications may conflict with the SCOS installation flow.
Installation
How do I install SCOS?
Use SCOS Builder to create a SCOS ISO from your own Windows ISO. Then create a bootable USB, boot from it, choose the target disk or partition, and let SCOS setup finish. See the step-by-step guide on the Download page.
Will installation erase my data?
It can. Selecting a target disk or partition may erase or format that drive. Back up your data before you begin.
Does SCOS modify my current Windows install?
SCOS is intended to be installed as a fresh separate environment. It does not modify your existing Windows installation unless you choose to install it over the same disk or partition.
Do I need Ethernet?
Ethernet is required for the current beta setup so SCOS can download required components and complete setup more reliably.
Bootable USB
Which tool should I use to create the USB?
You can use a tool such as Rufus or BalenaEtcher to write the generated SCOS ISO to a USB drive.
Should I enable Rufus customization options?
No. Leave all Windows installation customization options unchecked. This includes bypassing TPM, Secure Boot, RAM requirements, online account changes, local account creation, privacy options, regional options, and BitLocker-related changes.
Why leave customization options unchecked?
SCOS already includes its own unattended setup configuration. Extra USB tool customizations may overwrite or conflict with SCOS setup files and cause the installation to fail or behave incorrectly.
Controllers
USB vs Bluetooth?
USB controllers are recommended for the current beta. Bluetooth controller support is planned for a future version.
Which controllers work?
Xbox, PlayStation, and other XInput-compatible controllers should work over USB. A USB hub is recommended for multiple controllers.
Do I need keyboard and mouse?
Keyboard and mouse are useful for installation and troubleshooting. Daily use is intended to be controller-first once SCOS boots into Steam.
Audio picks the controller — how do I fix it?
- In Steam Big Picture: Menu → Settings → In-Game Voice.
- Under Microphone, choose Select Device to open the Windows sound panel.
- In the Playback tab, set your TV, AVR, speakers, or headset as Default.
- In the Recording tab, set your preferred microphone as Default if needed.
- Apply the change and return to Steam.
Networking
Can I use Wi-Fi?
Direct Wi-Fi configuration inside SCOS Standard is not yet part of the beta experience. Ethernet is strongly recommended.
What if my living-room setup has no Ethernet cable?
A Wi-Fi repeater or bridge with an Ethernet port can be configured in advance, then connected to the SCOS console through Ethernet.
Unified Remote & Launchers
What is Unified Remote for?
Unified Remote Server can help with occasional phone-based input for text fields or external launcher sign-ins when available.
Can I manually install apps later?
SCOS Standard restricts normal Windows desktop access after installation, so manual app installation is not part of the public Standard experience.
Do external launchers work?
SCOS is Windows-based, so it has better compatibility with Windows launchers than Linux-only environments. However, launcher behavior and sign-in flows may still vary during the beta.
SteamOS vs SCOS
SteamOS is a Linux-based Steam-first operating system. It works very well for many games, but some Windows games, launchers, anti-cheat systems, or tools may still depend on Linux/Proton support from the game developer.
SCOS takes a different approach. It keeps the Windows foundation, then turns it into a console-style Steam environment. This gives SCOS a better chance with games, launchers, drivers, and anti-cheat systems that expect Windows.
See Documentation → SteamOS vs SCOS for a detailed comparison.
Troubleshooting
Black screen after exiting Steam
SCOS Standard uses Steam as the final shell. Exiting Steam entirely may leave a blank or limited shell state. Restart the console to return to the intended Steam experience.
GPU driver is outdated
GPU driver update support is planned for a future SCOS release. The goal is to provide a controlled SCOS Driver Setup or Driver Manager path without exposing the full Windows desktop.
The clock or time zone is wrong
Time zone and internet clock sync improvements are planned. A future Builder version may let users select the time zone before creating the SCOS ISO.
No audio on TV/AVR
If the wrong audio device is selected, use the approved Sound settings path described in Audio picks the controller.
Privacy
SCOS aims to keep the environment focused and free of custom analytics by default. The website contact form may use an external provider; data entered into that form is handled by that provider. See Docs → Privacy & Data for details.
Roadmap
- SCOS Builder v0.1.3: Time zone selection and SCOS configuration options
- SCOS v0.3.6.5: Time zone and internet clock sync
- SCOS v0.3.7: Driver setup phase foundation
- SCOS v0.3.8: GPU driver update support
- Future: Optional SCOS Recovery Environment integration through Builder
- Future: Bluetooth and Wi-Fi improvements
- Future: Expanded Builder-based customization
- Future: Windows 11-based SCOS improvements