Monthly Archives: October 2015

Upgrading Windows 7 to Windows 10

After installing Windows 10 on a friends’ computer, I thought it was time to upgrade my own. My primary concern was my limited available space on my C-drive (I have two more drives with plenty of space). I tried to find good advice or information online, but no luck, so here is my report:

Upgrading Windows 7 to Windows 10: storage requirements

My Windows 7 computer had a C-drive with the following available capacity:
12.6 of 55.3 GB Free (after running disk cleanup).

That is, Windows and some programs were installed on C, most files on other drives. Anyway, Windows 7 was pretty eager to upgrade, and I started the procedure.

  1. It was “Checking requirements” (3 times, different dialogues)
  2. Downloading: available space down to 9.4GB
  3. Preparing for installation: down to 8,1GB

So far it had been the typical low-quality MS experience of different dialogs giving quite dull information and no real sense of progress, but now it got really bad:


The f**k is this? I did not know anything about installing the Insider Preview (there has never been any pre-release W7 whatsoever on this computer). And “something needing my attention”, being thrown back from the Windows 10 upgrade wizard to the Windows 7 system upgrade, not very impressive. Anyway, I just clicked “check your PC”, the Windows 10 upgrade continued, and I got this:


This is really crap! It had already checked requirements three different times, yet not figured out I had too little space. I could have told it, before it even started, that I probably had too little space. The good thing however was that I could pick another drive to use for extra space, and I happened to have an internal drive available.

After that, up to 10.5Gb availble space on my C-drive, and restart. Now my computer was working on its own for almost an hour. After that Windows 10 came up, and everything seemed fine.

With Windows 10, I now have 17.8GB free space on my C-drive. That was nice! Perhaps a reason in its own to upgrade to Windows 10.

Conclusion: upgrading to Windows 10 with limited available space on C is a good idea, but make sure to have an extra external (or internal) drive for the process itself.

Syncthing on Android

I installed Syncthing a few weeks ago. Now I found it was time to connect my Android mobile to it. Installing Syncthing via Google Play was easy. Configuring it, not that easy. The amount of useful error messages… close to zero.

I found:

  1. When I manually write the address to my other syncthing unit (like my NAS), only IP address works (with :port after it). Writing a domain name fails.
  2. When sharing a folder, I can not share a folder on the SD card: I get something like “Error (100%)”. To me, this is a pity, because I could put a big SD card (32-64GB) and have synchronised music there… but it seems not possible.

Update 2015-11-14: Upgraded to new syncthing version (0.12.2). Syncthing (for Android) now does not start properly. It just keeps “Loading”. No error message. No way to interact with it.

Upgrading to El Capitan deleted pkgsrc

I used to have pkgsrc on my Mac Book Air. Not anymore. I upgraded to El Capitan, and now there are no traces of /usr/pkg anymore.

I guess other package managers for OS X could face the same destiny. And I dont know if this has been a problems with previous upgrades either (my Mac Book Air came with Yosemite).

(Tried) Installing Windows 7 for the last time

A friend of mine came to me with his broken gaming computer. He does not know much about computers, but had surely invested in good hardware (some store configured and built it).

Why did it break? Well, a 90GB SSD + 1TB HD, Windows 7, is a guaranteed disaster for someone not an expert. Paging is on the SSD and it can be hard to get out of there. Everything installs on C: and it can be hard even for en export to not put stuff there. Eventually, the C drive will be full, fragmented, thrashing, and the SSD drive will break down.

We put a brand new 250GB SSD drive in place of his old broken down, and started installing Windows 7. I decided to try a Windows 7 with SP1 DVD – that worked fine with his original product key. That was the end of the good news.

First thing to do is Windows update… millions up critical updates I expected… except the only thing it updated was Windows update itself. After that, it got “stuck”. I tried numerous things like:

  • Waiting…
  • Someone suggested a proxy reset, or other network related problems.
  • Windows Update Troubleshooter (found 4 problems, fixed 3 of them). This is possibly the most retarded Windows tool I have seen. How would “working in the first place” be?
  • Some command line command to search for corrupted system files (there were none on this 1h young system and brand new hard drive).

After about two hours I thought enough is enough. Microsoft offers a free upgrade from 7 to 10, but not for my friend who had a legitimate Windows 7 key, with no way of getting to the point where upgrade to 10 is possible.

I believe Windows 7 (even with SP1) is just “too old and outdated” to successfully communicate with the Microsoft upgrade servers, and without some special knowledge it is impossible to get through.

Why is this Microsoft?

  • Are MS incapable of keeping old (but still supported) versions working?
  • Are MS intentionally breaking fresh Windows 7 installations to enforce Windows 10 migration?

In any way, it

  • Wastes peoples time.
  • Drives people to hacks and cracks to install software they already paid for.
  • Drives people to pay for something (Windows 10) that they should be able to upgrade to for free.

Anyway, while I spent several hours trying to install Windows 7 on his desktop, without much assistance he installed Xubuntu on his (Virus-sick Windows 8) laptop. And he was very happy with it.

In the end we installed Windows 10 on the desktop, and I think it is the only version of Windows currently worth installing (unless you have a server). That was, admittedly, a quite positive experience and it worked quite fine.