Is Microsoft planning a ‘bait and switch’ with the ‘free’ upgrade to Windows 10?

There’s a lot of uncertainty around exactly what Microsoft are offering for the ‘free’ upgrade to Windows 10 that’s going to start rolling out on July 29th. winsupersite.com have a good collection of questions people are starting to ask about what is included in the upgrade offer.

An article in Forbes discussing some internal presentation slides that ComputerWorld obtained is suggesting that the ‘free’ upgrade may not turn out to be entirely free after all, as a cryptic statement from Microsoft states:

“Revenue allocated is deferred and recognized on a straight-line basis over the estimated period the software upgrades are expected to be provided by estimated device life…. [The estimated device life] can range from two to four years”

We can only speculate exactly what Microsoft means by this statement, but it implies the ‘free’ upgrade is only initially free, and thrn at some point during the lifetime of your installation, the cost will be recouped. Exactly how or on what timescale the cost is recouped is unclear, but this statement implies at some point you will be charged for your Windows 10 – possibly ransomware style (‘Pay $199 now to continue using Windows 10’), or maybe subscription style (a monthly subscription to keep the install active?) – at this point there’s not enough information to be able to say. But it does seem clear, we’re not getting Windows 10 for ‘free’.

Windows 8.1 update 4/8/14

I picked up the 4/8/14 Windows 8.1 update today and was pleased that the Metro apps can now appear in the ‘classic’ desktop taskbar. It still seems odd to me that Windows 8 has two distinctly different personalities – the touchscreen friendly Metro apps from the new Start screen, and the classic desktop with regular looking Windows apps. It just seems confused to me – which is it? A post-PC touchscreen OS or a classic Windows desktop? Well, now at least the two are somewhat more combined.

Rather more odd however is that this cumulative update is required if you want to continue to receive Windows Updates. Pretty sure some internal IT departments are going to be pretty annoyed with this approach – “You want updates in the future? Install every update up to this date then we’ll give you new updates”. Uhuh.

Cygwin, git and ssh: ‘cannot spawn c:cygwinbinssh’

Using Cygwin and git on windows, I ran into an issue where git was working fine in a cygwin shell, but I was trying to setup a Jenkins build accessing a git repo, and git from Windows was giving errors like this:

$ git push myremote master
error: cannot spawn c:cygwinbinssh: No such file or directory
fatal: unable to fork

Running shell commands on Windows in Cygwin this was somewhat misleading, as I wasn’t expecting it to be looking for ‘ssh.exe’.

Turns out my GIT_SSH env var was causing the issue, had to replace this:

GIT_SSH=c:cygwinbinssh

with

GIT_SSH=c:cygwinbinssh.exe

and then all was good.