About BlueSystem

A small library of full version software for Windows, maintained by the people who test what goes into it.

BlueSystem started as a shared folder between four people who kept sending each other the same installers. Someone would rebuild a package, someone else would ask for it two weeks later, and the same links would get pasted back and forth until they expired. Putting the folder behind a web page was easier than answering the messages, and the page turned out to be more useful than the folder.

That was several years ago. The library is larger now, the mirrors are properly hosted, and there is a small group of people who test releases rather than one person doing it between other work. What has not changed is the idea: one page per release, written by somebody who actually installed it, with the details that matter and none of the padding.

What we list

Software that people pay for and mostly should not have to. Design applications billed monthly forever, engineering packages that cost more than the workstation they run on, office suites sold three times to the same household. If a program is already free, it is not here, because there are better places to get it and no reason for us to sit in the middle.

Every release is limited to the current version and, where a program has meaningfully different generations, the last one that many people still prefer. We do not keep an archive of every build ever released. Old packages accumulate problems, nobody tests them, and they make a library look larger than it usefully is.

How a release gets listed

It starts from the developer's own installer

Nothing here is a repack of a repack. Recompressing an installer to shave a few hundred megabytes off the download is where broken installations come from, and it saves an amount of time that stopped mattering when broadband did.

It gets installed on a clean machine

Each package goes onto a fresh system, gets opened, and gets used long enough to see whether the interface is complete, the components are all present, and the program still runs after a restart. Releases that fail this step do not get listed, and there are more of those than you would expect.

It gets written up by the person who tested it

The page you read is written from that installation rather than copied from a product listing. The system requirements are the ones that apply to the release, the installation steps are the ones that actually worked, and the notes about what goes wrong come from watching it go wrong.

It gets rebuilt when the build changes

New point release, new package. We do not patch an existing package and call it current, and we remove the previous one rather than leaving it up. A library full of stale versions is a library nobody can trust.

What we do not do

There is no account system on this site, and there never will be. Nothing here requires a sign in, an email address, or a survey, because every one of those exists to make money from a visitor rather than to give them a file. There is no link shortener chain and no waiting page between you and a download.

We do not put passwords on archives. The practice exists to defeat automated scanning, which means the only people it inconveniences are the ones downloading the file. If a page here tells you an archive is password protected, that page is not ours.

Mirrors

Every release sits on three regional mirrors, and larger packages carry a torrent magnet as well. The mirrors are checked on a rolling schedule, and a link that starts failing is pulled rather than left to waste the next visitor's afternoon. If you find a dead one, the contact page is the fastest way to tell us.

Talking to us

The contact page reaches the people who maintain the library. Broken links, wrong version numbers, and packages that do not install are the messages we want most, and they get read. If you are looking for something that is not listed, the requests page is where that goes, and it is checked weekly.