Once again, Microsoft manages to bungle the update process. Why is something that is so simply in GNU/Linux so difficult in Windows?
1.On my test machine, the updater from the "Windows Store" decided to simply uninstall any program it thought incompatible without asking me or telling me. Users will love it when they upgrade and their programs simply vanish.
2.The updater changed my lock screen background and pinned a bunch of stuff I don't want to my task bar. Why is it necessary to re-pin Internet Explorer to the task bar after it has already been removed.
3.It hid my libraries without asking me and then rearranged the order of things under "This PC" (which I promptly renamed back to Computer since my DLNA server is most certainly *not* on this PC) by putting all of the document folders and such above the drives.
4.It neglected to mention that BIOS disk passwords would prevent the update from working (in all fairness, I suspect it was a combination of bugs in Windows 8.1 and the EFI on my test machine); I ended up spending 3 hours trying to figure out why the computer was boot-looping into the EFI setup (apparently, the EFI writers took a cue from Microsoft and decided that an error message to the effect of no boot device was simply not necessary).
1.On my test machine, the updater from the "Windows Store" decided to simply uninstall any program it thought incompatible without asking me or telling me. Users will love it when they upgrade and their programs simply vanish.
2.The updater changed my lock screen background and pinned a bunch of stuff I don't want to my task bar. Why is it necessary to re-pin Internet Explorer to the task bar after it has already been removed.
3.It hid my libraries without asking me and then rearranged the order of things under "This PC" (which I promptly renamed back to Computer since my DLNA server is most certainly *not* on this PC) by putting all of the document folders and such above the drives.
4.It neglected to mention that BIOS disk passwords would prevent the update from working (in all fairness, I suspect it was a combination of bugs in Windows 8.1 and the EFI on my test machine); I ended up spending 3 hours trying to figure out why the computer was boot-looping into the EFI setup (apparently, the EFI writers took a cue from Microsoft and decided that an error message to the effect of no boot device was simply not necessary).