Jump to content

reinstalling a previously deleted provisioned app


Recommended Posts

Posted (edited)

this is just information in case anyone else needs to do the same (and of course if I google in a year after I forget...)

 

We deleted provisioned apps (pretty much all of them) from one of our W10EDU 1607 images (we have two images, an LTSB for the digital signs and a CB for everyone else). However, our IT teacher wants to play with the store and install a few apps to see if they are worth it (from a teaching point of view). I had deleted the store from provisioned (and user of course). After searching I found that you CAN put the store back but you need a donor machine with the same version and updates. This is the site I used.

 

Restore Microsoft Store application in Windows 10 - Super User

 

I needed to copy these folders from c:\program files\windowsapps on a donor machine (ownership needs changing)

 

Microsoft.WindowsStore_11606.1001.39.0_neutral_split.scale-100_8wekyb3d8bbwe
Microsoft.WindowsStore_11606.1001.39.0_x64__8wekyb3d8bbwe
Microsoft.WindowsStore_11606.1001.394.0_neutral_~_8wekyb3d8bbwe

 

and then run this powershell (note the last command is slightly different as the XML files are in a different place)

 

Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe\AppXManifest.xml"
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.23816.0_x86__8wekyb3d8bbwe\AppXManifest.xml"
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.NET.Native.Runtime.1.3_1.3.23901.0_x64__8wekyb3d8bbwe\AppXManifest.xml"
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.NET.Native.Runtime.1.3_1.3.23901.0_x86__8wekyb3d8bbwe\AppXManifest.xml"
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsStore_11606.1001.39.0_x64__8wekyb3d8bbwe\AppXManifest.xml"
Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.WindowsStore_11606.1001.394.0_neutral_~_8wekyb3d8bbwe\AppxMetadata\AppxBundleManifest.xml"

 

after this you MUST add the local security principal "ALL APPLICATION PACKAGES" permissions (read and execute) to c:\program files\windowsapps

 

voila! store now works. This also means you can search for the other deleted provisioned apps from the store (if you wish)

Edited by KK20
  • Thanks 2
Posted
I found that you CAN put the store back but you need a donor machine with the same version and updates.

Microsoft has an ISO on VLSC (search for "Windows 10 Inbox Apps") containing all of the pre-installed apps. To reinstall the Windows Store, mount the ISO, then run...

 

x64

Add-AppxProvisionedPackage -Online -PackagePath "X:\amd64fre\Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle" –LicensePath "X:\amd64fre\Microsoft.WindowsStore_8wekyb3d8bbwe.xml"

 

or

 

x86

Add-AppxProvisionedPackage -Online -PackagePath "X:\x86fre\Microsoft.WindowsStore_8wekyb3d8bbwe.appxbundle" –LicensePath "X:\x86fre\Microsoft.WindowsStore_8wekyb3d8bbwe.xml"

 

The ISO also contains the 'NET.Native' and 'VCLibs' appx files should they be required.

 

I used this method to install the Windows Store on the LTSB edition of Windows 10. :)

 

AHiDCr.jpg

  • Thanks 2
  • 2 months later...
Posted

Can anyone tell me the purpose of removing the apps in the first place, my work college has now changed his mind and wants to use the store for most of our schools. I have already deployed an image without provisioned apps which my image has come back with zero problems.

 

I thought the point of removing apps is that it doesn't clogg up windows and slows the machine down, although the store has good resources for teaching.

 

Can you share your thoughts on this?

Posted
I found deploying MSI much easier. Hence I don't use (and have removed) the store. I don't trust provisioned apps.
Posted
I've removed a large number of apps, but left ones which may come in useful or are needed for proper operation, including the Store. I can then block the store with Applocker and release it as necessary (and manage this block via groups). It doesn't pay to be too overzealous on app removal - for instance, we use the Windows Camera application frequently so it got left in. Some stuff will never be any use/will be a pain, those are the only apps I remove.
Posted

Can anyone help

 

I am trying to re-install the store with the following above, now does the c mean my local disk or the drive mount on the ISO.

 

My ISO is win10 education which is the same on the laptop

Posted
I am trying to re-install the store with the following above, now does the c mean my local disk or the drive mount on the ISO.

In the example in post #2 the X: drive is the drive letter of the mounted ISO.

  • 1 year later...
  • 1 month later...
Posted

For anyone (like myself) who (i) does not know what the VLSC is, or (ii) when he/she finds out what it is, realises that it is not available for mere punters (maybe it is, but the front page is off-putting):

 

It would appear that the required folders are on the W10 install DVD (or ISO), inside the 'install.wim' file: G:\sources\install.wim\1\Program Files\WindowsApps\. One can use 7zip to view the contents of the .wim file, and extract what one needs to the WindowsApps folder on C:. Then add the packages as detailed above. I had to take ownership of the WindowsApps folder to be able to write to it. Hope that helps someone the way this page helped me!

Posted
VLSC is the portal you log into in order to manage your volume licensing agreements, download ISO's for your licensed products, get your license keys (MAK and KMS) and assign any online agreements or benefits to other accounts (such as assigning office 365 to various tenants). Basically if you have volume license agreements then you use VLSC to manage them.
Posted
Yes, thanks, I had found out that (or the gist of it), but I am not in that field (I'm not managing or even using VLs). But since the info in this thread helped me (a PC user) with the store re-install, I thought I'd add a bit of info that might help others (in the same non-VLSC boat) who wander this way.
Posted (edited)

@martinG, @KK20. There's an even easier way of downloading (free) Store apps now. See the article below for more info.

 

How to download Microsoft Store apps

 

The new Adguard Store interface changes this as it provides anyone with options to download any Store application. All you need is the link to the Store to do so; you can select to download a specific version, e.g. for release versions of Windows 10 or Fast Ring.

 

Double-click on the AppxBundle file afterward to install the application on the Windows 10 device. The EAppxBundle file is used to update the application.

 

The app installs normally on the device. You can check the Store listing of the installed application and will notice that it behaves like any other application installed from the Store.

 

Please note that you cannot use the download option to get paid applications or games for free.

 

9zdeqj.png

 

To download the Windows Store application search on the website linked in the article for the following PackageFamilyName (which I found using "Get-AppxPackage | Select PackageFamilyName").

 

Microsoft.WindowsStore_8wekyb3d8bbwe

Edited by Arthur
Posted (edited)
and another 'thank-you' ! I shall pass this on to anyone else silly enough to have removed the Store app! (but its worth pointing out that with the store removed, I wouldn't have been able to easily find that full family name). Edited by martinG
Posted
when we feature upgraded to 1709 (via WSUS) the test machines put everything back (we were on 1604 at the time). We took this opportunity to leave the store (and lock it down with GPOs) but carried on removing other provisioned apps we werent ever going to use. we leveraged the Users\Default\AppData\Local\Microsoft\Windows\WSUS\setupconfig.ini following the feature update to kick start our removal PS script (and also run snappydriverorigin on a few problematic laptops that had weird drivers). we are still on 1709 now and will probably move to either 1809 (if it is ever fixed) or whatever abomination arrives in april.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...