i just found this inside the packages ... i do not know which one ... is more safe to remove with my chopping..
i did Standalone Core removing professional package , and in this moment i am doing original Core... does not really matter which one ... as long as i have media codecs and is more lite ... cause encoding a movie takes around 8 to 14 hours .. so i need i very stable and lite one ...
If original, it is useless: https://forums.mydigitallife.net/th...nstruction-project.80939/page-67#post-1635575 Remove a package from Core, the whole Professional is still there.
good point ... sorry .. i was doing a core standalone with the 00000.0_Core_to_Standalone way ... and then i added the codecs and remove some apx ... i am trying almost every thing what i found useful from your work ...
Of course. This package tells that you are using original Core: Microsoft-Windows-Printing-LocalPrinting-Enterprise-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Now that I have shared the comparison list, how could I don't know what's all about these two editions.
this and all the others i was trying to remove them but they were giving error ... so maybe i was trying to remove the professional packages from a standalone core .. so maybe that was the error ... ok let me explain what i did : 1. i use the 00000.0_Core_to_Standalone and i remove the professional package from original home edition 2. i start adding all that media codecs 3. i remove the additional packages 4 i was trying to remove the printing packages and all the other which i found them in the uup files of professional esd folder 5. they were giving error
Start from the scratch making sure that you are using standalone Core. 1. Remove unwanted packages. 2. Remove unwanted Apps. Done. Good luck.
No. it is already there. These primary packages: Microsoft-Windows-Printing-Foundation-Package Microsoft-Windows-Printing-LocalPrinting-Home-Package Microsoft-Windows-Printing-PrintToPDFServices-Package Microsoft-Windows-Printing-XPSServices-Package Microsoft-Windows-SMB1Deprecation-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-SMB1-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-SmbDirect-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Telnet-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-TFTP-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-WinOcr-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-WinSATMediaFiles-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Windows-Defender-ApplicationGuard-Inbox-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.19041.1 PS. The sub-packages together with language packs will be removed along when a primary package is removed. e.g. Package A has 5 sub-packages a to e. To remove them, simply remove A: A A-Lang a a-Lang b b-Lang c c-Lang d d-Lang e e-Lang On the contrary, to add, both A and A-Lang are needed to be installed. (No need for sub-packages) Some package need to remove both amd64 and WOW64 packages. (You have to spend time studying mum file to see the relationship between primary package and sub-packages.) If you are not sure, check \Windows\servicing\Packages to see if there is WOW64 package left after amd64 package is removed.
Except some updates like LCU and SSU, you can directly remove those packages shown with this command: dism /english /image:C:\MOUNT /get-packages For those you see in C:\MOUNT\Windows\servicing\Packages, before the package is possible to be removed, the registry needs modification to 1. set its visibility to 1 2. remove its owner For your information , please go to https://forums.mydigitallife.net/forums/mdl-projects-and-applications.34/ for Masters' help.
THANKS ... waiting to try it so this can not integrate updates offline ? it is perfect as long as i have the drivers up to date ... anyway i hate all this monthly changes ... too many ..
I manage to build 19041.685 Windows 10 Home Standalone (Lite) but with some adjustment : 19041.1 Windows 10 Home Standalone (Lite) updated with latest servicing pack monthly [HowTo] 1. Extract 19041.1_Core_to_Standalone_Lite_amd64.zip 2. Place install.wim of 19041.1 amd64 Core in 19041.1_Core_to_Standalone_Lite_amd64. 3. Modify and save 19041.1_Core_to_Standalone_Lite_amd64\files\Remove-Appx.txt. 4. Modify and save 19041.1_Core_to_Standalone_Lite_amd64\files\Remove-Pack.txt. remove only this feature on demand packs as you wish in order not to destroy the update process for the future: Microsoft-Windows-Hello-Face-Migration-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Hello-Face-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-StepsRecorder-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-TabletPCMath-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.19041.1 OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 5. Run 19041.1_Core_to_Standalone_Lite_amd64\Start-As-Admin.cmd as Administrator. 6. Update created 19041.1 Windows 10 Home Standalone (Lite) only with: - Servicing Stack Update KB4593175 - Adobe Flash Player Update for Removal KB4577586 - Cumulative Update KB4592438 NOW TO CHOPPED THE WAY YOU WANT : I faced a new challenge when i was trying to remove this packages with DISM command from the updated 19041.685 Windows 10 Home Standalone (Lite) : acces is denied , error 5 , so i used Dism++10.1.1001.10 Microsoft-Windows-UserExperience-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Printing-Foundation-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Printing-PrintToPDFServices-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Printing-XPSServices-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Printing-LocalPrinting-Home-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-SMB1Deprecation-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-SMB1-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-Telnet-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-TFTP-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-WinOcr-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Microsoft-Windows-WinSATMediaFiles-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Update the new image with : microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~ and the preview of net-framework monthly The new created up to date image 19041.685 Windows 10 Home Standalone (Lite) Thanks for the hint !!!!