"PowerShell" in the command is used to run the command using PowerShell from the command prompt.
You'll just need to run the full command in the tutorial in an elevated command prompt without using "PowerShell" separately first instead.
Hello! Please, could someone tell me if it has been fixed the horrible Windows 10 bug, present in v10586, that destroys default metro apps, instead of re-register them, if you use the powershell command? I'm currently on v10586.318.
Hello Brink! Thank you for letting us know!!! That's really a good news indeed!!!
I was able to install the Store in a Windows 10 Enterprise 64-bit LTSB, after installing first Microsoft.VClibs.140 and Microsoft.NET.Runtime.1.1 which are pre-requisites. As I said, the Store installed without generating any errors in the Power Shell window. It shows in All Apps menu and it starts, but it disappears after one second. I wonder if there are any other packages the Store is depending upon? Like the Microsoft.Accountscontrol package, which I did not find in the normal Windows 10 Enterprise install.wim. The Microsoft.WinJS.2.0 package is also missing from the install.wim of the normal Windows 10 Enterprise 64-bit iso.
Any help with making this work will be appreciated!
Thank you for your prompt tip. I was wrong about Microsoft.AccountsControl package. It was installed but I've missed it. I have also installed Microsoft.WinJS.2.0, which I copied from a Windows 10 Pro computer. Windows automatically updated VCLibs from build 22810 to 24123, .NET.Runtime from version 184.108.40.206.22929.0 to 220.127.116.11.23406.0 and .NET.Framework from version 18.104.22.168.22929.0 to 22.214.171.124.23115.0. It did not update though the WindowsStore and WinJS (which don't come with LTSB). Unfortunately, even after these updates, the Store still shows up for only one second.
Below is the output of the Get-AppxPackage -allusers | Select Name, PackageFullName. The empty line delimits the status before and after the manual installations I've performed. All the SystemApps were installed (checked with your command). If you can think of anything to make the Store work in LTSB, I'll really appreciate it:
PS C:\Windows\system32> Get-AppxPackage -allusers | Select Name, PackageFullName
I forgot to mention I don't ever run Windows under Microsoft live accounts. Consequently, on computers with WindowsApps, when I run the Store (or Mail, Calendar, etc...) it is first asking for Microsoft credentials. I suspect this is what prevents the Store, although correctly installed and registered, to work in LTSB. It may not call whatever routines are required for authenticating the Store app to Microsoft Store site. Of course, this is just a wild guess....