Project Horizon
Project Horizon helps benches stop waiting on the same Windows updates again and again. It separates system updates from driver work, checks what is already available, builds a reusable update archive, and makes long update passes visible to technicians.
Every machine should not restart the same wait.
Windows setup and refresh work can burn time while each machine discovers, downloads, installs, reboots, and repeats. Across refurb batches, repairs, and fleet refreshes, the same approved updates may be downloaded again and again.
A reusable archive with visible progress.
Horizon checks local and shared update sources first, shows what is ready or missing, captures approved updates once, and tracks install/reboot state so technicians are not waiting blindly.
Update work you can actually see.
Update Scan and Sources
Download Progress and Archive Growth
Install Pass and Reboot State
Scan, filter, cache, install, and track.
Scan
Find required and optional updates for the current machine and show what needs attention.
Filter
Separate driver findings from general system updates so driver work can route toward Project Verta.
Cache
Check reusable update archives first and capture missing approved updates for future machines.
Install
Run cached update installs while tracking progress, failures, and reboot state for the technician.
Without Horizon
- Every machine waits through the same discovery and download cycle.
- Technicians have little visibility into which updates are ready, missing, oversized, or blocked.
- Driver updates can get mixed into the system-update workflow.
- Long install passes feel idle because progress and reboot state are not clear.
With Horizon
- Approved updates become reusable across bench systems, repair jobs, and managed fleets.
- Live progress, source status, and reboot tracking make update work visible.
- Driver update findings can be routed to Project Verta for cleaner driver resolution.
- The update archive grows as useful work is captured once and reused later.
The pieces that turn update work into reusable value.
Reusable Update Archive
Checks available update archives first, so captured updates can help the next refurb unit, repair job, or fleet refresh.
Source Visibility
Shows whether each update is ready, available elsewhere, or still needs attention, so technicians can see the work.
Managed Downloads
Captures approved updates with visible progress, retry handling, and clear failure reporting.
Install and Reboot Tracking
Runs the correct install process for cached updates and surfaces when Windows asks for a reboot.
Verta Driver Bridge
Keeps driver updates out of the general update pass and gives Project Verta cleaner driver-resolution findings.
Bench Safety
Marks oversized, blocked, or non-reusable updates clearly for technician or IT follow-up.
Built for repeated Windows setup work.
Refurb benches
Reuse approved update files across batches instead of burning time on repeat downloads.
Repair operations
Make OS reload and post-repair update work more visible, repeatable, and less dependent on manual notes.
Enterprise refresh
Support refresh and redeployment work from a shared archive that grows with each approved update pass.
Designed to work beside PCCheck and Verta.
PCCheck helps document the machine. Verta helps resolve drivers. Horizon focuses on reusable Windows update work. Together, they reduce repeated bench labor and make common processing steps easier to see, repeat, and improve.
Want reusable Windows update work?
Talk with Source Potato about Project Horizon, update archive strategy, and how your Windows setup workflow runs today.