Windows 9 is the operating system that never happened. Microsoft announced Windows 10 in September 2014 and skipped straight past the version number people were expecting, and the internal builds that would have become Windows 9 (versions 9834, 9838, and 9845) leaked instead. In the years since, a small group of hobbyists have worked through those leaked builds, patched the missing bits, and put together installable ISOs of what Windows 9 Technical Preview could have looked like as a real product. Those community-completed builds are hosted at windows9.4up.eu, and they are what this article is about.

Windows 9 was never released, never supported, never security-patched, and never had a software ecosystem built around it. There is no “getting current” step because there was nothing to get current with. The Chromium base caps at version 80 natively. The Microsoft Office versions of the era (2013 mostly) will install with some coaxing. Almost everything else you might try, if it was compiled against a modern Windows SDK, will crash on launch with a KERNELBASE.dll error because the kernel behaviour on this preview genuinely is unstable in ways Microsoft never had to ship a fix for.

That is the context in which SnipeOffice on Windows 9 makes sense. The project’s stated goal from day one was to run cleanly across the widest possible range of hardware, so the fan-completed W9TP is an obvious target: an operating system with real users (small but real), no supported office suite, and a genuine need for something that works. Our answer is a specific bundle, the SnipeOffice 25.8 Safe Bundle for Windows 9, that goes about the problem differently to how we handled Windows 8.1 or 10. It relies on forcing every launch through safe mode to sidestep the parts of the modern SDK that Windows 9 cannot cope with.

The Windows 9 Pro desktop and System panel on the test VM. The build string in the bottom right corner names the leaked Microsoft internal build the fan-completed ISO is based on.

About What You Are Actually Running

The Windows 9 Technical Preview is not a product. It is a mid-development snapshot of what became Windows 10, released by Microsoft to a small circle of partners in 2014 and leaked to the internet shortly afterwards. The fan-completed builds at windows9.4up.eu have had community patches applied to make them installable and reasonably usable, but the underlying kernel is still what Microsoft shipped internally in September 2014. It has bugs that were fixed later in the Windows 10 development cycle, and those fixes never made it back into 9.

What that means in practice: Internet Explorer works. The stock Chromium base runs up to version 80. VC++ redistributables install cleanly and stay installed. The file system, Explorer shell, and desktop apps behave the way an early Windows 10 preview would. Modern software compiled against the Windows 10 or 11 SDK often fails on launch because it hits kernel paths that were rewritten between build 9845 and the eventual Windows 10 RTM, and the failure is usually loud: a KERNELBASE.dll crash before the application even draws its window.

That is the specific problem the SnipeOffice Safe Bundle exists to work around. The rest of this article assumes you have a working install of one of the fan-completed builds (9834, 9838, or 9845), that you can log in, that you have internet access, and that you have the standard Visual C++ 2015-2022 redistributables ready to install (the bundle ships with them). If any of that is not true, sort it out first before continuing.

Internet Explorer is what ships with the Technical Preview builds and it is the browser you will use to reach the download page and pull the bundles down. It is not the browser you want to use for anything else, and the sections below cover the replacements we recommend.

Snipe Browser 140 for Windows 9

The vanilla Windows 9 Technical Preview supports Chromium up to version 80 natively. Anything newer than that hits the same kernel paths that trip up modern office software, and modern Chromium builds fail on Windows 9 for exactly the same reasons every other modern SDK-compiled binary does. Firefox in a current release is out. Chrome is out. Edge did not exist yet in 9834 and was never backported. What is left, if you want a browser that renders the current web, is Snipe Browser.

Snipe Browser 140 for Windows 9 lives at browser.snipeoffice.org/windows9/ and at snipebrowser.com/windows9/. The download page describes what it actually is: “The niche, comedic, genuinely-working build for the unreleased Windows 9 Technical Preview, the ‘missing link’ OS that became Windows 10. Tuned for the community-restored builds 9838 and 9845, this is a resource-constrained Chromium 140 with serialized threading and instant thread termination, optimised for the experimental W9TP kernel.” That description is accurate and worth reading twice.

The Windows 9 build sits on Chromium 140.0.7339.127, V8 14.0.365.4, and ships under the “Resource-Constrained Profile” label rather than the “Legacy Kernel Wrapper” label the Windows 8.1 build uses. The two builds solve different problems. The 8.1 build is missing runtime DLLs. The Windows 9 build is running on a kernel that cannot be trusted with normal multi-threaded work, so the Chromium threading model has been rewritten to serialise everything it can and terminate threads immediately when they are done. It is slower than a mainstream Chromium build in ways you will notice on any real work, and it uses more CPU. It is also the only current-web browser that runs on Windows 9 without crashing, so the trade is one we accept.

Downloads come as installer or portable ZIP, both from GitHub release assets. The installer file is called SnipeBrowser-140.0.7339.127-win-x86-win9-setup.exe, weighs 127 MB, and comes through Internet Explorer the usual way for a large binary: an in-page save-or-run bar followed by a SmartScreen warning that flags it as an unrecognised app from an unknown publisher.

The Snipe Browser download page for Windows 9 Technical Preview 32/64-bit.

The SmartScreen wall is expected. Snipe Browser binaries are unsigned. Click More info, then Run anyway, then answer Yes to the UAC prompt when it names the publisher as Unknown and the file origin as the hard drive.

Internet Explorer SmartScreen refusing the Snipe Browser installer for Windows 9 by default. The binary is unsigned; the file itself is the real release from GitHub.

The installer itself is the same Inno-style wizard as the other Snipe Browser builds. Install mode picker (per-user or per-machine), destination location (C:\Program Files (x86)\Snipe by default, 531 MB installed), additional tasks (desktop shortcut and Quick Launch shortcut), review, install.

The Snipe Browser installer at the Ready to Install step on Windows 9. Same wizard the other Windows builds use; only the payload differs.

First launch drops you on the Snipe start page at browser.snipeoffice.org. The “Snipe isn’t your default browser” prompt appears at the top. Ignore it or set it as default, your call. The new-tab layout is the standard Snipe ecosystem grid: SnipeSearch across the top, then rows for Social (Toot Snipe, Snipe Diaspora, Snipe Pics, SnipeSocial, TTWrite, SnipeSearch Video), Services (SnipeSearch, Snipe Adclicks, SnipeOffice, SnipeSearch Ark, SnipeSearch Maps, SnipeSearch Asia, SnipeSearch Info), and Resources (Snipe Play, SnipeSearch Movies, SnipeSearch Music, Snipe Support).

Snipe Browser 140 running on Windows 9. The new-tab layout is the same ecosystem grid every Snipe Browser build carries.

Visit browser.snipeoffice.org/check to verify the install. On our test the page returned a green tick and confirmed Snipe 140.0.7339.127 matched the current release for Windows 9. The check page shows the browser identifies as Snipe on the Blink engine, treats Windows 9 as its own release channel, and reports the correct build. Per-platform builds are the model across the whole Snipe project, and Windows 9 gets its own line specifically because the changes needed to make Chromium run on this kernel are not the changes needed on any other OS.

The browser self-check page confirming Snipe 140.0.7339.127 matches the current release for Windows 9. Engine: Blink (Chromium). The Windows 9 channel is treated as its own release track.

Memory footprint is heavier than the Windows 8.1 build because of the serialised threading. Expect somewhere between 100 and 200 MB per tab depending on the site, though single-tab idle sits closer to 60 MB. GPU acceleration is off by default and should probably stay off. The graphics drivers that ship with the fan-completed builds are not something you want to trust with hardware pipelines.

SnipeOffice 25.8 on Windows 9

The Windows 9 desktop bundle for SnipeOffice takes a different approach to every other Windows edition we ship. It is a 64-bit-only package, targets the x64 variants of Builds 9834, 9838, and 9845, and every launch is forced through safe mode. The bundle is not a runtime patch (like the Windows 8.1 build) and it is not a plain installer (like Windows 10/11). It is a wrapper that keeps the modern LibreOffice 25 core alive on a kernel it was never meant to touch.

The download page at snipeoffice.org lists Windows 9 in the Downloads Matrix as “fan TP · builds 9834 / 9838 / 9845 · x64” with a Download Installer link. The matrix at snipeoffice.org/downloads-matrix is worth reading if you have not seen it before, it is the authoritative comparison of what we ship for each Windows and non-Windows platform.

The SnipeOffice Downloads Matrix at snipeoffice.org/downloads-matrix, showing the Windows 9 row alongside the other supported OSes. The Windows 9 line is explicitly labelled “fan TP · builds 9834 / 9838 / 9845 · x64”.

The file itself is snipeoffce25win9.2.zip (yes, “snipeoffce” not “snipeoffice”, the folder name has a typo that has propagated through several builds and we are aware of it), 330 MB, hosted on GitHub release assets. Save it to your Downloads folder or wherever suits you.

Extract the ZIP the standard Explorer way. Right-click, Extract All, accept the default destination. The extract will report about 6,156 items and unpacks into a folder called snipeoffce25win9. Inside are the Application and prerequisites subfolders plus a handful of loose files:

Install-SnipeOffice-Win9.bat (the primary installer), Install-Prerequisites-Only.bat (the fallback if the main installer fails partway through), Create-Desktop-Shortcuts.bat and .ps1 (redeploy shortcuts on their own), Register-Win9-FileAssociations.bat and .ps1 (redeploy file associations on their own), and install-log.txt (created on first run). And most importantly “safe-install.bat” if the normal install fails use safe-install.

The extracted snipeoffce25win9 folder in Explorer. Install-SnipeOffice-Win9.bat is the primary installer; the -Only variants are recovery paths.

Right-click Install-SnipeOffice-Win9.bat, run as administrator, answer Yes to the UAC prompt. The batch launches a PowerShell window with an execution policy bypass and the transcript starts with the header:

SnipeOffice Windows 9 Installer. Step 1: Prerequisites (VC++ redistributables 1-4). Step 2: SnipeOffice application, to C:\SnipeOffice. Step 3: Runtime compatibility patches. Step 4: Desktop shortcuts (safe mode). Step 5: File associations (double-click documents to safe mode).

The Win 9 batch installer running through step 1, applying the four bundled Visual C++ redistributables. The header lays out all five steps up front.

Step 1 installs the four Visual C++ redistributables that the modern core needs (VC_redist-2022-windows9.x86.exe first at about 13.8 MB, then the x64 equivalent, then the older x86 and x64 pair). Two install fresh, two report exit code 1638 meaning a compatible or newer version is already present. Either result is fine.

Step 2 copies the SnipeOffice application files into C:\SnipeOffice. There is no Inno-style wizard here, no destination picker, no Start Menu folder prompt. The install path is fixed and the batch script lays files down in place. This is a deliberate choice: the wizard UI adds complexity that could itself trip up on the W9TP kernel, and there is no useful choice for the user to make anyway.

Step 3 applies the runtime compatibility patches. This is where the safe-mode wrapper gets built: the batch script generates C:\SnipeOffice\program\SnipeOffice-Win9.cmd, a small launcher that starts each SnipeOffice application with the –safe-mode flag baked in.

Step 4 drops desktop shortcuts. Snipe Office (the Start Center), Writer, Calc, Impress, Draw, Base, and Math each get their own icon. Every one of them points at SnipeOffice-Win9.cmd with the appropriate application flag (–writer, –calc, –impress, –draw, –base, –math).

Step 5 registers file associations for the standard document types: .csv, .doc, .docx, .odb, .odf, .odg, .odp, .ods, .odt, .otg, .otp, .ots, .ott, .ppt, .pptx, .rtf, .xls, and .xlsx. All eighteen associations point at the same SnipeOffice-Win9.cmd wrapper, so double-clicking any supported document from Explorer or opening one from a mail attachment lands in safe mode automatically.

The transcript closes with an Installation complete summary block and a Press any key to continue prompt.

The installer transcript at completion. Every file association points at SnipeOffice-Win9.cmd, so double-clicking any supported document launches with –safe-mode.

If the main installer fails partway (usually because a VC++ redistributable installer choked), Install-Prerequisites-Only.bat handles the prerequisites in isolation without touching the SnipeOffice install. That is the recovery path. Once prerequisites succeed, re-run Install-SnipeOffice-Win9.bat and it picks up where it left off.

What Actually Runs After Install

Launching any SnipeOffice app on Windows 9 goes through the SnipeOffice-Win9.cmd wrapper, which starts the underlying binary with –safe-mode. On first launch this triggers the SnipeOffice safe-mode dialog, a modal that asks whether you want to restore from backup, apply various configuration resets, or continue as is. On Windows 9 the answer is always the same: click Continue in Safe Mode, close the dialog, and get on with your work. Restart in Normal Mode is greyed out because that would defeat the whole point of the wrapper.

The SnipeOffice safe-mode dialog that appears on first launch. Continue in Safe Mode is the button to click; the Start Center is already open behind it.

Every window title after that reads “(Safe Mode)” in the title bar, which is a small ongoing reminder of what is happening under the hood. The applications themselves are the full SnipeOfficeCC suite: Writer, Calc, Impress, Draw, Base, and Math, all present, all functional. The safe-mode flag disables user extensions, hardware graphics acceleration, and a handful of configuration paths that could destabilise the launch, but everything else works.

Writer opens with the standard menu bar and toolbar, an info banner at the top confirming this is the first launch of version 25.8 with a Release Notes link. Style dropdowns work. The sidebar loads. Documents open and save. Round-tripping a .docx to a modern Word install works cleanly.

SnipeOfficeCC Writer running on Windows 9 in safe mode. The window title carries the “(Safe Mode)” suffix; the first-run banner offers Release Notes.

Calc runs the full grid with formula bar, sheet tabs, and the Data menu. Impress opens with the template picker (Beehive, Blue Curve, Blueprint Plans, Candy, DNA, Focus, Forestbird, Freshes, Grey Elegant, Growing Liberty, Inspiration, Lights) and does multi-slide presentations with transitions and PDF/EPUB export. Draw handles vector work. Base runs the Database Wizard for HSQLDB Embedded or Firebird External. Math takes equations.

SnipeOfficeCC Impress in safe mode with the template picker open. Every application in the suite launches through the same safe-mode wrapper.

Total resource use for the whole running suite plus Snipe Browser 140 with one open tab sits around 1.4 GB of RAM on our test VM. The document window itself takes about 80 MB, the browser tab another 60 to 80, and the safe-mode wrapper does not add measurable overhead. That is a comfortable ceiling for a machine of the era Windows 9 was written for.

The BOM-first behaviour is intact. Every CSV or text export from Calc, and every .srt or .stl subtitle from Writer, comes out as UTF-8 with a Byte Order Mark. Chinese, Japanese, Cyrillic, Arabic, mixed-language content, emoji all survive the trip to whatever downstream tool is going to consume the file.

Snipe Cloud Office on Windows 9

Snipe Cloud Office is the browser-based edition of the SnipeOffice family, at cloud.snipeoffice.org, and the same account works for both the desktop install and the cloud. Two channels: legacy for older engines, modern for Chromium 80 and up.

On Windows 9 you have two realistic ways to reach it, plus a third that we would rather you did not use.

Snipe Browser 140: modern channel, works cleanly, this is what you should be using. All five apps (Writer, Calc, Impress, myPage, Form Manager) load and behave the way they were meant to. The Chromium 140 build is the reason we recommend installing Snipe Browser before touching Cloud, and every screenshot in this section was taken through it.

Legacy channel via Internet Explorer: if you insist on using the stock browser, the legacy channel works cleanly. You lose Form Manager (which is modern-only) and some of the newer myPage tools, but Writer, Calc, Impress, and the base myPage editor all function properly. Sign in via the same account you would use anywhere else.

Modern channel via Internet Explorer: this is the one to avoid. The Cloud router looks at IE, decides it should be modern-capable, and forwards it there automatically. In practice IE renders the modern app shell in a strange way, layout comes out wrong in places, and some controls do not behave correctly. We have seen the same behaviour on Windows 8 with IE 10 and on Windows 8.1 with IE 11, so this is a persistent problem across the Windows generation IE belongs to rather than something specific to Windows 9. If you land on the modern channel by mistake, click the “Switch to legacy” link in the CHANNEL section of the sidebar to get back to something usable. The saner path is to install Snipe Browser 140 and use that instead.

The Snipe Cloud modern Start Center loaded in Snipe Browser 140 on Windows 9. Five app tiles, full sidebar, cookie banner honoured. This is the way to reach Cloud on this OS.

With Snipe Browser installed and Cloud loaded through it, the Start Center is the front door. Five app tiles across the top: Writer, Calc, Impress, myPage, Form Manager. Sidebar navigation for Create, Storage, Account, and Channel. Cookie banner honoured at the bottom.

Cloud Writer opens .docx directly, preserves basic formatting, and saves back to your local Downloads folder unless you have a Pro or Pro Elite plan set up for Save to Cloud. Cloud Calc gives you a 300-column by 60-row grid with formula bar, AutoSum, sort and filter, and open/save for ODS, XLSX (cell values only), and the CSV family. Cloud Impress runs multi-slide presentations with a thumbnail pane, slide controls, and export to PDF, EPUB, or HTML slideshow.

myPage is the multi-file HTML site editor with folder list, Design/Code/Preview tabs, and the modern-only toolbar row: SEO Meta Inspector, Technical/Contact/Social meta tag builders, .htaccess rule builder with HTTPS/www/301/302/410 presets, error page generator for 404/410/500/503 with ErrorDocument wiring, Check Links, Validate HTML, Box Model, code hints, Embed Video for YouTube, Vimeo, and PeerTube.

Form Manager is modern-only and sign-in only. Free 5 forms / 50 replies each, Pro 10 forms / 500 replies each, Pro Elite 20 forms / 1000 replies each. Payment fields are blocked by policy so nobody uses Form Manager to phish card details.

The whole Cloud stack renders identically to how it does on Windows 8.1 or on a current Windows 11 machine, because once you are on Snipe Browser 140 the underlying OS stops mattering to the browser engine.

Best Office Suites for Windows 9 in the 21st Century

Windows 9 was never officially released, so this list is unusual. There is no vendor support to have lost, no end-of-life date to work back from, no supported ecosystem that has gradually walked away. There is only the question of what actually installs and runs on the fan-completed builds, and the honest answer is a much shorter list than any other OS we have written about.

Every entry below has been tested on our Windows 9 test VM and confirmed to install cleanly and run. Nothing has been included on the strength of “it should work” or “it was contemporary with this OS.” If a suite is not on the list, either it failed on install, it crashed on first launch, or we have not tested it and are not going to claim otherwise. The four things that matter for the ranking are whether the suite handles modern .docx, .xlsx, and .pptx directly, whether it installs cleanly on Windows 9, whether the file it saves back opens correctly on the recipient’s modern suite, and cost.

1. SnipeOffice 25.8 Safe Bundle for Windows 9 (64-bit only)

The full LibreOffice 25 core with BOM-first exports, wrapped in a safe-mode launcher that keeps it stable on the W9TP kernel. Modern DOCX, XLSX, and PPTX handling out of the box. Complete suite: Writer, Calc, Impress, Draw, Base, Math. The only current-generation office suite that runs on Windows 9. Free. Requires a 64-bit install of one of the fan-completed builds. This is what we recommend for anyone who needs to actually work with 2020s-era documents on this OS.

2. Snipe Cloud Office (any Windows 9 build)

Runs modern .docx, .xlsx, and .pptx directly in the browser through Snipe Browser 140 on the modern channel, or through Internet Explorer on the legacy channel. Both channels tested and working on the Windows 9 test VM. Writer, Calc, Impress, myPage, and Form Manager on modern; Writer, Calc, Impress, and the base myPage editor on legacy. Full BOM-first exports throughout. Works on 32-bit Windows 9 too, where the desktop bundle does not. Free. The right choice when the desktop bundle is not an option, or when you want a second working path alongside it.

3. OpenOffice 4.1.16

The current OpenOffice release, and one that installs cleanly on the fan-completed Windows 9 builds without special handling. Writer, Calc, Impress, Draw, Base, and Math all present. Native ODF support and adequate handling of .doc, .xls, and .ppt. Modern OOXML support is more limited than what the LibreOffice 25 codebase in SnipeOffice delivers, so a complex DOCX from Word 2024 may lose formatting on the round trip, but for simpler documents it holds up. Free. A reasonable second desktop option if you want a stock Apache OpenOffice install specifically.

4. FreeOffice 2024

SoftMaker’s free office suite in its current 2024 release, TextMaker, PlanMaker, and Presentations. Tested working on Windows 9 with no unusual configuration. Ships with genuinely current .docx, .xlsx, and .pptx handling as its native format focus, so files saved back typically open cleanly in Word or Excel on the receiving end. Interface leans closer to Microsoft’s ribbon layout than to the LibreOffice tradition, which some people prefer. Free with registration. Worth a look if the modern MS Office file compatibility is your top concern.

5. Microsoft Office 2010

The oldest Microsoft Office we can vouch for on Windows 9, and one that installs comfortably. .doc, .xls, and .ppt out of the box; .docx, .xlsx, and .pptx with the Microsoft Office Compatibility Pack installed alongside. Full Word, Excel, PowerPoint, Outlook, OneNote depending on your SKU. End of extended support was October 2020, so treat it as unsupported for anything security-sensitive, and understand that its modern-format handling is limited compared to the four options above. The catch as ever is licensing, you need a legitimate 2010 key and Microsoft has not sold them in years.

Why We Bother

There is an entirely reasonable question about why anyone would put engineering effort into an operating system that was never released and has no legitimate user base. The straight answer is that the fan-completed Windows 9 builds have a small but real community, and that community has the same problem every other legacy-OS user has: modern documents arrive, modern software will not install, and there is nowhere to turn for a working office suite. The problem is small in scale but genuine, and building for it took a specific and interesting engineering approach (the safe-mode wrapper, the serialised-threading browser build) that we can now apply to other awkward targets when they come up.

There is also a smaller reason. Windows 9 exists in the same collective memory as the version-number joke, the missing OS, the release that was skipped. Getting a full modern office suite and browser stack running on it, cleanly, is a small demonstration that “unsupported” and “will not work” are not the same claim. The hardware works. The operating system boots. What was missing was the software to bring it back to a working state, and that is a problem that yields to work rather than money.

Everything in this article is free: the desktop bundle, the browser, the Cloud suite, the search engine at snipesearch.com. The Windows 9 build itself lives at windows9.4up.eu for anyone who wants to try it. The whole stack costs nothing. If you have a 9834 or 9845 install kicking around from curiosity, or you are thinking of setting one up, the software is there and it works.