Upgrading From Windows 1.0 to Windows 8 On Actual Hardware

Jacob Aaronson · 7.3M views · 2013-09-03 · 1:14:16

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

A 74-minute video of upgrading Windows 1.0 through every release up to Windows 8 on a real netbook rather than in a virtual machine.

On Hacker News

HN cites it as the example proving Windows has an unbroken upgrade path from 1.0 to 8.

Discussed on HN; no positive recommendation is recorded in this export · HN mentions 2015–2020

Topics

History of computing Demoscene & retrocomputing GUI, HCI & interface history

What people said

trimbo · 2020-08 · Reference
I was hoping for an upgrade video, like people have done for Windows Here's one that goes from Windows 1.0 -> Windows 8: [VIDEO]
Read the original HN comment ↗

UweSchmidt · 2015-04 · Reference
These upgrade-shortcuts could introduce a significant increase in testing complexity if you want ensure that you can go from any system version to the current version. On the other hand, with the current system people upgrade from Windows 1.0 to 8 (e.g. [VIDEO] ).
Read the original HN comment ↗

mkautzm · 2015-01 · Reference
You are the person I'm talking about when I say that people that blame Windows for problems are their own worst enemy, and it's way worse when Dunning-Kruger is in full effect as well... > Inexperience with a computer doesn't cause ntdll to break. Inexperience with a computer doesn't cause Windows activation to break. Inexperience with a computer doesn't cause shutdowns to take hours instead of seconds. Inexperience with a computer doesn't cause suspend to spontaneously bork. Inexperience causes all these things. Listen, my experience goes way, way beyond 'anecdotal' when it comes to managing end users running Windows. Never, ever, ever with the exception of a small handful of updates, does Windows fundamentally break itself. When you see a bluescreen, 100% of the time it is your fault or it's your hardware's fault. 100% of the time. Sometimes it might look like it's not your fault. Sometimes it's McAfee removing important files that break the OS because it's being stupid, but that's not a Window's problem. If shutdowns are taking awhile, something is broken. Your inability to diagnose that isn't the fault of the OS. Ever. If your computer 'suddenly borks', then your hardware failed, or you are bad at computer. 100% of the time. If you can't manage to upgrade Windows, than I can't help you. Someone did it from 1.0 to 6.2 in a straight shot: [VIDEO] When stuff like this happens: > According to jjoonathan, the ntdll segfaults started happening after an update It usually means t
Read the original HN comment ↗

Sources

Video by Jacob Aaronson, played through YouTube.

HN Library · Source license

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks

SaaS & AI candidates: Topic keywords do not match
Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources