Summary of "Bringing back a dead Microsoft product"
Summary — “Bringing back a dead Microsoft product”
Context and high-level points
- The video documents an experiment: installing Microsoft’s shelved OS Windows 10X onto a first‑generation Surface Duo using the community “Windows on ARM” project.
- Background: Microsoft announced dual‑screen hardware (Surface Neo / Surface Duo) and Windows 10X in 2019, then cancelled Neo and 10X (many ideas folded into Windows 11). No Microsoft device shipped with 10X; the OS largely disappeared except for developer previews.
Hardware / DIY work
- The creator made a DIY keyboard case for the Surface Duo (3D‑printed, magnets adapted from Surface Pen mounts).
- It’s a concept/fancy case for a generic Bluetooth keyboard — functional but imperfect (fit, magnet placement, FDM print limitations).
Installation steps (what the creator did)
- Obtained a Windows 10X FFU image.
- Used an FFU loader + device manager workflow:
- Put the Duo in boot/flash mode (Andromeda logo), press volume up to enter Windows mode.
- In FFU loader: select image → flash FFU image → wait for installation and first boot.
- Discovered Device Portal (a web interface) on the Duo that allows controlling the device, sideloading UWP / Microsoft Store apps, and running apps remotely.
What worked
- Windows 10X booted on the Surface Duo and ran; UI animations and app transitions felt polished even on relatively weak hardware.
- Core UWP apps (file explorer, Photos, a terminal with tabs, remote desktop, calculator) were present or sideloadable.
- Bluetooth keyboard pairing and the Wonder Bar (Touch Bar–like feature) could partially function.
- Device Portal enabled sideloading of UWP / ARM64 store apps.
Key technical limitations and failures
- Windows 10X forced Microsoft account sign‑in — no local account option (worse than Windows 11 in this respect).
- No native Win32 support: 10X was designed for UWP/modern apps or virtualized Win32; that limitation was a major reason 10X struggled in practicality.
- App compatibility issues:
- Spotify’s dependency failed to install.
- Firefox and some other browsers crashed or didn’t render pages.
- UWP browsers required WebView2 (not present), leaving only an old Edge build usable for web browsing.
- Audio was broken on the Duo under Windows 10X, making media playback practically unusable.
- Some UI elements and touch calibration were off; certain pre‑installed apps didn’t behave normally (e.g., apps refusing to close).
- Bluetooth and Wonder Bar functionality were spotty.
Observations and analysis
- Windows 10X delivered a clean, polished UI/UX vision for modern and dual‑screen devices; the author found the experience pleasing despite practical shortcomings.
- The project highlights the strengths and limits of the UWP ecosystem: elegant when it works, but too restrictive and poorly adopted by third‑party developers.
- The cancellation of 10X reflects Microsoft’s shift away from being primarily an OS company toward focusing on cloud / AI / data‑center services; 10X’s vendor‑lock risks and lack of legacy app support were key problems.
- Community projects like Windows on ARM are invaluable for porting and experimenting with unsupported hardware/OS combinations.
Practical takeaways / checklist
- You can flash Windows 10X FFU to a Surface Duo using an FFU loader and the device boot menu.
- Device Portal is useful for sideloading UWP apps (ARM64 builds required).
- Expect major compatibility issues: Microsoft account required, limited app availability, missing dependencies (e.g., WebView2), broken audio, and unstable peripheral support.
People / sources mentioned
- Video narrator / creator (YouTuber) — main speaker and experimenter.
- Microsoft — Surface Neo, Surface Duo hardware and Windows 10X OS (announced 2019, later cancelled).
- Windows on ARM project authors / open‑source contributors — credited for enabling Windows on the Duo and this experiment.
- Microsoft Store / UWP ecosystem and various app developers implicitly referenced (Spotify, Firefox, Edge, WebView2).
Category
Technology
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...