Update Windows 8.1 Pro to Windows 10 – my experience

As I’ve written in my last blog post, I’m one of the guys who likes to test the newest and latest software versions. In this case, Windows 10. So I’ve updated my gaming system with the tool from Microsoft I’ve mentioned.

The setup tool of Windows 10 warned me about two things:

  • All your apps will be removed and only your personal data is kept.
  • Your language pack will be removed (english) and will be reset to german.

The first one was really misleading: All apps? What defines an app? Isn’t that only the one from the market place? Apparently not, because I’ve lost all my installed applications as promised. The update wasn’t able to reuse the installed applications, which is really sad for an update imho.

The language pack is reset to german: well, that’s somehow ok, although I’ve installed an english Windows 8.1 pro and only enabled the german keyboard layout and date/timezones. I would have assumed that it continues to use english as the system language, but it seems that you need to install one of the language packs again.

This left me only with one possible choice: restore Windows 8.1. Open start, type „update“ and open the update settings. Select „restore“ from the left menu and select „return to Windows 8.1“.

This option exists only for 31 days after your update and will ask you for the reasons why you want to restore your system. A few restarts later and your system is thankfully restored to its previous state: All apps are working, your Windows 10 reservation is still active.

So if you ask me: It’s too early to update to Windows 10. At least with this media creation tool which seems to support only the creation of new installations of Windows 10.

How to update to Windows 10 immediately without waiting

I’ve reserved on my Windows 8.1 machine the Windows 10 update a few weeks ago. Since yesterday you can now officially install Windows 10 in its final version. The Microsoft update tool should notify you, when the update is ready to install.

However, Microsoft decided to deliver the update files in several waves to keep the load from their content delivery network.

If you are like me interested in getting the newest versions immediately, you’ll probably checked your Windows update setting and didn’t notice any new updates for you.

Yesterday Ginny Caughey recommended to just use a certain command:

The recommended command is this one:

This command should circumvent the limitations given by Microsoft regarding your position in the update waves. However, it always ended in error messages for me, besides downloading around 2,7GB of setup files.

Today I’ve read that there is already a tool available from Microsoft which allows you to create a bootable installation media from a downloaded Windows 10 iso file. This tool also allows you to start the installation of Windows 10 immediately, so you don’t have to wait any longer.

Right now this tool is running and updates my PC to Windows 10 🙂

Forward Kodi/XBMC video information to hyperion on Raspberry Pi

My current network setup allows me only to use small bandwidth connections between the living room (that’s where my Raspberry Pi is used as my Mediacenter) and office (my NAS). However, my Macbook is fast enough and can access the NAS wirelessly, so that I often use it as a replacement for the hardwired Raspberry Pi.

However, I cannot use my Hyperion Ambilight setup behind the TV in combination with the Macbook, because its only connected to the Raspberry Pi. But yesterday I’ve found this plugin which enables the Kodi setup on my Macbook to connect to the Hyperion Server on my Raspberry Pi over network.

  1. Download the zip file with the content of the git repository.
  2. Start Kodi on the Macbook and install it using the add on manager. You can point to the zip file directly without the need to unzip it first.
  3. Configure the installed plugin to connect to the ip of your Hyperion server.
  4. Start a video and be amazed that the lights on your TV will work wirelessly 😉

Office Mac 2011 cannot open files from network folder with home in its name

It’s unbelievable: Microsoft Office Mac 2011 cannot open files from network folders when the share name contains „home“. My Synology NAS uses shared folders for each of its users. The user folders can be reached under the „home“ share and are automatically mapped to the user’s home folder on the Synology. This is the default setting for every new standard setup of Synology NAS.

I’ve tried recently to access an Excel file from my home folder. After double clicking in the Finder, Excel opened with this error message:

Excel File cannot be opened

So it cannot find the file. This is due to a known Office bug that exists now for several years and appears to be still unpatched.

It’s inexplicable how an error of this severity is still unpatched. All my search results suggest me to stop using the home folder and use instead a different name. That’s working for my user, because it has admin rights and can open the „homes“ share with a subfolder to my username. However, not all of the users on my network should have this right.

I only hope that the new Mac Office will address this issue. The currently available preview is pretty unusable and tends to crash when I’m working with network volumes.

iMessage mit portierter Rufnummer benutzen

Wenn man ein neues iPhone besitzt muss man auf einige Details achten. Das ist insbesondere dann der Fall, wenn man einen neuen Vertrag abgeschlossen hat und seine alte Handynummer portieren möchte und diese für iMessage verwenden möchte.

Im Falle einer Portierung bekommt man eine temporäre Telefonnummer und kann diese erst einmal in dem neuen iPhone benutzen und dort für iMessage einrichten.

Am Tage der Portierung wird diese alte Nummer aber ungültig. Beide iPhones haben dann kein Netz mehr und Anrufer erhalten entsprechende Meldungen (temporäre Nummer: ist z.Z. nicht vergeben, portierte Nummer: ist z.Z. nicht erreichbar). Nach einem Neustart des neuen iPhones bucht sich das iPhone wieder im Netz ein und ist dann unter der portierten Nummer erreichbar. Allerdings stimmen die iMessage Einstellungen nicht und verweisen nach wie vor auf die temporäre Nummer. In diesem Fall muss man einige Einstellungen auf dem alten und neuen iPhone bearbeiten, so dass die temporäre Nummer entfernt und die portierte Nummer auf dem neuen iPhone aktiv wird.

Auf dem alten iPhone mit alter Sim und alter Nummer:

  • iMessage deaktivieren

Auf dem neuen iPhone mit neuer Sim und temporärer Nummer:

  • iMessage ist eingeschaltet und ist für die temporäre Nummer eingerichtet
  • iMessage abschalten
  • SIM Karte entfernen
  • Einstellungen, Allgemein, Zurücksetzen, Netzwerkeinstellungen
  • Bestätigen und iPhone neustarten lassen
  • SIM Karte wieder einsetzen
  • iMessage wieder einschalten und über die portierte Nummer in den iMessage Einstellungen freuen 🙂

Auf dem alten iPhone hat man jetzt die iMessage Einstellungen entfernt, es empfängt jetzt nicht mehr die Nachrichten.