SCOS Builder v0.1.3 · Build Package v0.3.7

Documentation

SCOS Standard is a Windows-based Steam console environment for living-room gaming. It is built with SCOS Builder from your own official Windows ISO.

SCOS does not include Windows. Windows activation remains separate from SCOS and is the user's responsibility.

SCOS is independent and not affiliated with Microsoft, Valve, Steam, or any third-party launcher.

Project Overview

SCOS is designed to turn a compatible Windows installation into a living-room Steam console environment. SCOS Standard boots into Steam Big Picture / Steam Gamepad UI and restricts normal Windows desktop access for a more console-like experience.

  • Built with SCOS Builder from a user-provided Windows ISO.
  • Native Windows compatibility for games, launchers, drivers, and anti-cheat systems that expect Windows.
  • Console-like startup with Steam as the final shell in SCOS Standard.
  • Controller-first direction for daily use after installation.
In short: SteamOS is a Linux-based Steam-first operating system. SCOS is a Windows-based console environment designed for Steam gaming while keeping Windows compatibility.

Want the quick answer? Jump to SteamOS vs SCOS.

Current Public Release

  • SCOS Builder: v0.1.3
  • SCOS Build Package: v0.3.7
  • Edition: Standard
  • Channel: stable
  • Status: Public beta

How SCOS Builder Works

SCOS Builder creates the final SCOS installation ISO from your own official Windows ISO.

  1. The user selects an official Windows ISO.
  2. The user selects an output folder.
  3. SCOS Builder downloads the official SCOS Build Package from GitHub.
  4. SCOS Builder validates the build package manifest.
  5. SCOS Builder injects SCOS setup files into the Windows ISO structure.
  6. SCOS Builder replaces the temporary bootstrap password placeholder.
  7. SCOS Builder writes the SCOS Standard edition and lockdown markers.
  8. SCOS Builder rebuilds the final bootable SCOS ISO.
The final ISO is created as SCOS_Standard_yyyyMMdd_HHmmss.iso in the selected output folder.

Requirements

Builder Requirements

  • OS: Windows 10 or Windows 11
  • .NET: .NET Desktop Runtime matching the SCOS Builder release
  • Windows ADK: Deployment Tools component for oscdimg.exe
  • Windows ISO: Official Windows ISO provided by the user
  • Internet: Required to download the SCOS Build Package from GitHub

Target Console Requirements

  • CPU: Modern dual-core minimum; quad-core or better recommended
  • RAM: 8 GB minimum; 16 GB recommended for modern games
  • GPU: DirectX 12 compatible GPU recommended
  • Storage: SSD recommended; size depends on the Windows version and games installed
  • Network: Ethernet required for the current beta setup
  • Input: Keyboard and mouse for installation; controller for daily use
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.

Windows ADK Installation

SCOS Builder uses oscdimg.exe to rebuild the final bootable ISO. This tool is included with Windows ADK Deployment Tools.

During Windows ADK installation, only this component is required:

[x] Deployment Tools

The other ADK components are not required for SCOS Builder v0.1.3.

Alternatively, oscdimg.exe can be placed manually next to SCOS Builder in tools\oscdimg.exe.

Installation

SCOS installs as a separate Windows-based console environment. It does not modify your existing Windows installation unless you choose to install it over the same disk or partition.

⚠️ Important: Installing SCOS to a disk or partition can erase data. Back up everything important before you begin.

  1. Download SCOS Builder from the official GitHub release page.
  2. Extract the SCOS Builder release package and keep all included files together.
  3. Run SCOSBuilder.exe.
  4. Select your official Windows ISO.
  5. Select an output folder.
  6. Click Build SCOS ISO.
  7. Create a bootable USB from the generated SCOS ISO.
  8. Boot the target console from the USB drive.
  9. Select the target disk or partition and install SCOS.
  10. Let SCOS setup finish and reboot into the Steam console environment.

Bootable USB Warning

When creating a bootable USB from a SCOS ISO, do not enable Windows installation customization options.

If your USB creation tool shows options such as bypassing TPM, Secure Boot, RAM requirements, creating a local account, disabling data collection, changing regional settings, or modifying Windows setup behavior, leave all of those options unchecked.

SCOS already includes its own unattended setup configuration. Extra customization options may conflict with SCOS setup files and cause the installation to fail or behave incorrectly.

For SCOS ISOs, write the ISO as-is.

Networking

  • Current beta: Ethernet is strongly recommended during installation.
  • Wi-Fi setup: Direct Wi-Fi configuration inside SCOS Standard is not yet part of the beta experience.
  • Alternative: Use a Wi-Fi repeater or bridge configured in advance, then connect it to the console through Ethernet.
  • Built-in Wi-Fi support is planned for a future version.

Controllers

  • USB controllers are recommended for the current beta.
  • Use a USB hub to connect multiple controllers.
  • Bluetooth controller support is planned for a future version.
  • Keyboard and mouse are mainly useful for installation and troubleshooting.

Installed Software and Setup Components

  • Steam — used as the main shell in SCOS Standard
  • Unified Remote Server — planned/used for occasional phone-based input where available
  • Required setup components — downloaded during SCOS setup when needed

Beta note: Some helper tools and launcher-related behavior may still change between beta releases.

SCOS Standard restricts normal Windows desktop access after installation, so manual app installation after setup is not part of the public Standard experience.

SteamOS vs SCOS

SteamOS is a Linux-based Steam-first operating system. SCOS is a Windows-based console environment designed for Steam gaming while keeping Windows compatibility.

Feature SteamOS SCOS
Base System Linux-based Windows-based
Main Goal Steam-first Linux gaming Living-room console-style gaming with Windows compatibility
Windows Game Support Strong through Proton, but not perfect Native Windows compatibility
External Launchers May require extra setup Better compatibility with Windows launchers
Anti-Cheat / DRM Depends on Linux/Proton support from game developers Better chance with Windows anti-cheat games because it runs on Windows
Driver Support Depends on Linux driver support Broad Windows driver compatibility
Desktop Access Desktop mode available Restricted in SCOS Standard
Windows Activation Not needed Separate from SCOS and handled by the user
Maturity Mature Valve platform Early public beta
Best For Steam Deck users and Linux-friendly Steam gaming Players who want a Windows-powered Steam console experience
In short: SteamOS is the better lightweight Steam-first operating system. SCOS is for players who want a console-like Steam experience while keeping the Windows compatibility layer that many games, launchers, drivers, and anti-cheat systems still expect.

Console-Mode Design

SCOS Standard is designed to behave like a console, not a normal desktop PC. The goal is simple: power on, sign in to Steam, and play.

  • Boots directly into Steam Big Picture / Steam Gamepad UI.
  • Normal Windows desktop access is restricted.
  • Task Manager, interactive Command Prompt, Registry Editor, and similar tools are restricted in Standard.
  • Sound settings may remain available when needed for audio device configuration.

Settings Access

SCOS Standard is intentionally restricted. Normal Windows Settings access is not part of the public Standard experience.

The main approved Windows panel is Sound settings, because it may be needed to select the correct TV, speaker, headset, or microphone device.

  1. Open the Steam menu.
  2. Go to Settings → In-Game Voice.
  3. Under Microphone, choose Select Device to open the Windows sound panel.

Controller mouse emulation may be used where supported. Keyboard and mouse remain useful for setup and troubleshooting.

Steam Behavior

  • SCOS Standard uses Steam as the final shell.
  • Restarting the console returns to the Steam console environment.
  • Exiting Steam entirely may leave a blank or limited shell state. Restart the console to return to the intended experience.

Quick Start Guide

  1. Install .NET Desktop Runtime if required.
  2. Install Windows ADK and select only Deployment Tools.
  3. Download SCOS Builder v0.1.3 from the official GitHub release page.
  4. Extract the release package and run SCOSBuilder.exe.
  5. Select your official Windows ISO.
  6. Select an output folder.
  7. Build the SCOS ISO.
  8. Create a bootable USB from the generated ISO with all USB customization options unchecked.
  9. Boot the target console from the USB drive and install SCOS Standard.
  10. After setup, SCOS boots into the Steam console environment.

Current Beta Notes

  • Time zone and internet clock sync improvements are planned for a future update.
  • GPU driver update support is planned for a future update.
  • SCOS Recovery Environment support is planned later and is not currently included in the Git repository.
  • SCOS Builder customization options may be added later, such as time zone selection and optional recovery support.

Planned Features 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: Full SCOS OOBE or Builder-based customization expansion
  • Future: Windows 11-based SCOS improvements

Privacy & Data

SCOS aims to keep the environment simple, focused, and free of custom analytics by default.

  • Website contact forms: If an external form provider is used, submitted data is handled by that provider.
  • What may be collected: Information entered into the form, plus metadata handled by the provider.
  • Website analytics: None enabled by default. Any future analytics will be documented.
  • SCOS environment: SCOS aims to reduce telemetry where safe for a console-like experience.

Questions about data handling? Reach us via the Contact page.