Add Store to Windows Enterprise LTSB new methods

So could you confirm what is within the folder?

 

You need to login to view this posts content.

 

The script is clearly for Updating Apps, not adding them (it's my script actually )
while it might work becaue of sideloading apps mode, but it's not the correct way to add an app

what's wrong with using this one simple command?
x86

Code:

Add-AppxProvisionedPackage -Online -PackagePath Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle -DependencyPackagePath Microsoft.VCLibs.x86.14.00.appx,Microsoft.NET.Native.Framework.x86.1.3.appx,Microsoft.NET.Native.Runtime.x86.1.3.appx -LicensePath Microsoft.WindowsStore_8wekyb3d8bbwe.xml

x64

Code:

Add-AppxProvisionedPackage -Online -PackagePath Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle -DependencyPackagePath Microsoft.VCLibs.x64.14.00.appx,Microsoft.VCLibs.x86.14.00.appx,Microsoft.NET.Native.Framework.x64.1.3.appx,Microsoft.NET.Native.Framework.x86.1.3.appx,Microsoft.NET.Native.Runtime.x64.1.3.appx,Microsoft.NET.Native.Runtime.x86.1.3.appx -LicensePath Microsoft.WindowsStore_8wekyb3d8bbwe.xml

insead copying files from other system and taking ownership, setting permission... blah blah of that nonsense

 

Nice!

Couldn't one add this to the "RunOnce" reg key(Pointing to a script file) in the Software hive, so it executes automatically after/during install?
(And the ps1 script somewhere on the DVD/Install media)
Just an idea

 

Or integrate it into wim image the same way
using -Path C:\Mount instead -Online

 

I wonder if the store app can be "injected" to an image with Add-AppxProvisionedPackage ?

Add-AppxPackage only works -Online as far as I know, hence you can't inject it into a image/WIM file.

I'm no pro at this so please correct me if i'm wrong.

The above is done to the already running system after/during install, and my idea would be to script it into the "RunOnce"
key as that seems feasible, and you would have the store installed without any user input.

A third alternative if one is hellbent on having it incorporated 100%, would be to run the above
Pshell script on a live system, and use a registry snapshot tool to figure out the differences, which
one then tries to incorporate into the offline hive, but that's a longshot that I have no clue if it's doable...?

Running the above "one liner" from shewolf will not only register the store app, it will register all apps,
so you will have a lot of registry changes to contemplate

This would probably work and narrow it down somewhat:
Add-AppXPackage -Register '%ProgramFiles%\WindowsApps\Microsoft.WindowsStore*\AppXManifest.xml' -DisableDevelopmentMode

 

Provisioned = installed for all users
it's not to define an app type
the command is Add-AppxProvisionedPackage, what's more clear you want?

Code:

Add-AppxProvisionedPackage -Path C:\Mount -PackagePath Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle -DependencyPackagePath Microsoft.VCLibs.x64.14.00.appx,Microsoft.VCLibs.x86.14.00.appx,Microsoft.NET.Native.Framework.x64.1.3.appx,Microsoft.NET.Native.Framework.x86.1.3.appx,Microsoft.NET.Native.Runtime.x64.1.3.appx,Microsoft.NET.Native.Runtime.x86.1.3.appx -LicensePath Microsoft.WindowsStore_8wekyb3d8bbwe.xml

powershell is easier, dism require more parameters for each dependency package, but both function the same

Code:

dism /Image:C:\Mount /Add-ProvisionedAppxPackage /PackagePath:Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle /DependencyPackagePath:Microsoft.VCLibs.x64.14.00.appx /DependencyPackagePath:Microsoft.VCLibs.x86.14.00.appx /DependencyPackagePath:Microsoft.NET.Native.Framework.x64.1.3.appx /DependencyPackagePath:Microsoft.NET.Native.Framework.x86.1.3.appx /DependencyPackagePath:Microsoft.NET.Native.Runtime.x64.1.3.appx /DependencyPackagePath:Microsoft.NET.Native.Runtime.x86.1.3.appx /LicensePath:Microsoft.WindowsStore_8wekyb3d8bbwe.xml

 

Just a think good to know that seem very few people are aware of

We know (I hope) that in most part of the windows command line the linux like tab autocompletion works

But it doesn't after a colon, which is common on dism commands, so if you write

dism /Image:C:\Mount /Add-ProvisionedAppxPackage /PackagePath:M

an then you push the TAB button, nothing happens

But a quote is enough to restore the functionality: just write the command above as

dism /Image:C:\Mount /Add-ProvisionedAppxPackage /PackagePath:"M

and the filename will be autocompleted, sparing a lot of typing or copy/paste

 

The Microsoft.WindowsStore_8wekyb3d8bbwe package/s you would copy to mounted image path:
Program Files\WindowsApps.
It will then be copied over automatically during install, then use "RunOnce" reg key to run Pshell script which will
execute when the first user log in "registering" the store app.


That is, if you can't "inject" it directly with abbodi1406's Add-AppxProvisionedPackage command,
to the "offline" image, cause that would be the best thing offcourse

 

This is very interesting. Is it possible to make a step-by-step guide?
The files still have to be downloaded I assume?
Sorry for asking, you guys go pretty fast.

Cheers.

 

You need to login to view this posts content.

 

Muchas gracias me a servido, Activado store x86 LTSB, and server 2016, gracias ,saludos.