Removal of biometrics-related, HomeGroup and Store packages

mattybi

New Member
There are Microsoft.BioEnrollment and homegroup packages in NTLite but they do not include these packages (as known through DISM):
Microsoft-OneCore-Biometrics-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Microsoft-OneCore-Biometrics-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Microsoft-OneCore-Biometrics-Fingerprint-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Microsoft-OneCore-Biometrics-FaceRecognition-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Media-FaceAnalysis-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Media-FaceAnalysis-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0

Microsoft-Windows-Shell-HomeGroup-Package-printscan~31bf3856ad364e35~amd64~~10.0.14393.0

Also, I haven't found a package that could remove Windows Store:
Microsoft-Windows-Store-Client-Package~31bf3856ad364e35~amd64~~10.0.14393.0

I wonder if you could add these packages to component removal. So far I only worked with LTSB 2016 so I don't know how this stuff looks like with other OS releases.

Cheers
 
Hi Matt,

there is the "Windows Biometric Service" component, and in 1.6 beta under it "Face Recognition".
I skipped merging of the Biometric Service and the App, even though it was done for some like Store, Defender and similar as if the app is removed, doesn't make much sense to keep the backend.
But in the case of Biometric, you might want to use 3rd party Biometric drivers/apps, just not Windows app for it.
Let me know if you disagree, if that app is crucial to set it up regardless of what uses the functionality.

Microsoft-Windows-Shell-HomeGroup-Package-printscan is removed when both Printing and HomeGroup are both removed.
The exact reason why not with just HomeGroup, I think it was about Settings-Printing demanding one of the HomeGroup control panel files.

Microsoft-Windows-Store-Client-Package should be removed with Store "Microsoft.WindowsStore" app or if not existing "Windows Store" component.

There is the Search function on the Components page toolbar to find these easier.

Let me know if some of these do not fit reality on your side.
Thanks.
 
Hey, thank you for replying.

I agree with you on Biometric. I just didn't know that I would need to remove Windows Biometric Service, Face Recognition and BioEnrollment to include the packages I was interested in removing.

I have removed the HomeGroup-Package-printscan in past using the DISM method and never had any issues with printing, but I understand your reasons to keep it with Printing package.

I have used the search function and cycled through results for "Store". It seems that in 1.5.6080 the Microsoft.WindowsStore is not listed for LTSB 2016 (could be a finding). Is it listed in 1.6 beta? I haven't used it yet, I'll give it a shot!
 
Last edited:
Please search for "Windows Store" in LTSB components, I see it listed under "Windows Apps", doesn't need to be the beta.
If using "Store", you need to press Next - Next ... until it focuses on that one, there are others with the "store" in the name.
 
This is genuine en-gb LTSB 2016 image with SHA-1: 21D25006B7F0C00D035A200B0FE4CB7DA1C1E2EF. I do not see Windows Store but I can remove this package: Microsoft-Windows-Store-Client-Package~31bf3856ad364e35~amd64~~10.0.14393.0 with DISM.

Capture.PNG
 
I apologize, loading the image indeed is not showing it, I was testing live VM install (C:\Windows) of the LTSB, then it is listed in this particular case.

The flag was set to detect LTSB Store only Live, in other words if the deployed app doesn't exist, as in this case, it's just an underlying package.

Will test how it works, as the very old note states it breaks Metro (UWP). If OK, will unhide in the next update, out on Monday. I can send you a PM with the test version if you want.

Thanks!
 
If it removes more packages than the single one I listed above then I imagine it might break UWP. I have been using various Windows builds without the Store client for three years now and never had stability issues. This isn't a big deal altogether because if I remove the package with DISM I don't get any errors in either online checkhealth or sfc's scannow.

I will gladly test the related changes for you.
 
Last edited:
Uploaded in the build 6105, please let me know how it goes. Thanks.
 
I have tested an image with Store removed.

I understand now that I never run into problems because I haven't used any Windows Store-related functions before. I tried installing Duolingo by going to Microsoft Store website on IE but it simply didn't do anything. The rest seems to work just fine.

I would like to install some UWP app from other source than Store to check if it's broken or not, but I don't know where to find one yet.
 
Back
Top