Have the Windows Live Essentials 2012 on here but hardly even use it! The main handler is strictly kept online rather then any app in order to avoid these kinds of problems. The 2012 is simply used to import from multiple MS accounts kept separate.
Fellow geeks, as the PowerShell OneGet has been mentioned a few times in this thread, I thought it would be important to inform you that because MS has changed the name of it to PowerShell PackageManament, I have asked admins to rename the tutorial and edited it replacing all mentions of the old name with the new one.
Tutorial will be brought fully up to date today, I will also remake the video in it.
PowerShell PackageManagement - Install Apps from Command Line - Windows 10 Forums
Thank you again for a most informative tutorial meeting on PowerShell PackageManagement last Saturday. I learned a lot, although I know there's more to learn.
PowerShell is, well, powerful.
Their new name will be difficult to remember - OneGet will be the search I will use, and keep forgetting what to call it....
I tend to remember when I get my hands slapped . . .
Edit: Also, Kari's new and revised tutorial should be up later today.
Forgive me if I seem bemused, but Windows is built as a Graphical User Interface, with a raison d'etre to perform operating system tasks that previously required a command-line interface to accomplish.
More and more, since NT- and DOS-based Windows were brought together in Windows XP, and to a greater extent in subsequent Windows versions, the need to use console-based tools to do operations that could be accomplished by point and click applets becomes more apparent.
As an example, in Windows 98, if I wanted to find out my current IP address configuration, the winipcfg.exe utility would show this. In XP and since, I had to open a command console and type IPconfig and some switches to see the same information (I admit IPconfig does a lot more than Winipcfg.exe, but the latter could have been developed to give the same functionality as the command-line tool does).
When I moved to Windows 7 after skipping Vista, I was shocked with the increased complexity of searching without simple clickable filters as I had in XP.
Still now I have the answer:
Choco Install Everything
That's just it. Older versions were just GUI attached to DOS, roles have been reversed since. Looks like there is tendency to merge some features with Linux like functions and it's Console to work at kernel level.
There's still a lot of people that like using KB instead of mouse/pad. My nephew doesn't even have mouse with his computer running windows, uses KB only.
It's not just using keyboard though, Mike - it's syntax and remembering commands and switches, when the computer is a much better remembering and symbol handling tool than I am. It's like a waste of all the processing power in front of me, and no doubt the product of the lack of programming skills that 20 years of Graphical User Interfaces on computers has engendered, through spoiling users with lots of GUI and multimedia wonders.
How hard is it to encompass all these commands* into a point and click, list and process, user interface, much in the same way as I used to design, in a past life as an Access 2.0 -> Access 2003 database application developer? Even the Clipper interfaces I did before were mouse aware to hide the user from the DBase language which these ran upon.
Linux in various distributions and flavours does graphical package managers aplenty amongst other utilities, while Windows has less and less in the way of built-in new utilities, but masses of 3rd party trivial apps that generally do very little.
*e.g. powershell cmdlets