come good, i also use ltsc w10, not w11 version, too bad it have store, will test it today great job @balanadi i going add some custom OEM pack will remove more crap, and see the result's if you want remove this crap store credit @abbodi1406 Code: # Remove the AppX Package for all users $WindowsStore = 'Microsoft.WindowsStore' Get-AppXPackage -AllUsers | Where-Object { $_.Name -match $WindowsStore } | Remove-AppxPackage -AllUsers # Remove the AppX Provisioned Package for all users Get-AppxProvisionedPackage -Online | Where-Object { $_.DisplayName -match $WindowsStore } | Remove-AppxProvisionedPackage -Online --------------------- So, i got an hwid activation error even it found matched hwid license i guess it because home edition + modified build = PRoblem's but kms38 succeed, OK, at least ise removed, why ...?
To remove all the Store crap you can just delete the Appx folder !!!!! Thanks for using it and hope that it is satisfying your needs...
You need Microsoft-Windows-Client-LanguagePack-Package-amd64-ru-ru.esd in your casee from UUP files when you download 10.0.26100.1_ru-ru and you exract in lp folder deleting the en-us
Got it, thank you very much! Of course I could have guessed about "lp" myself, but it only occurred to me after your hint...
@balanadi I tested your script without an error ran in a vm worked very well for mine! I will customize to remove store and do more testing, thank you for your script.
I found this one in a 26100 pro to LTSC reconstruction ... Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>
to remove store just delete the folder Appx cause already is removing store before starting the reconstruction
I see, but in my case the task is different. I don't need to transform anything because I already use IoT Enterprise LTSC. Therefore I think that in my case file 1.xml should look something like this: Spoiler Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-IoTEnterpriseSEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-IoTEnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum" /> </package> </servicing> </unattend> I assumed that these actions would clear the WinSxS folder and replace its contents with the sxs package files. Which would significantly reduce the size of the WinSxS folder, but this did not happen, to my regret. Apparently, in my case, there is no need to do all this at all and just delete the sxs folder as unnecessary?
My question to you is : if you just install Microsoft-Windows-IoTEnterpriseSEdition without removing Core and Professional maybe that is the reason you have so many in winSxS folder ... there are 3 editions in your image now ...
@balanadi I have included modern calc in the appx dir, it installs no problem as I added to the Add-Appx.txt However I have both Calcs now & tried to delete the win32calc though the script complains & causes some errors in the process, can you advise a simpler way to achieve this?
It's been a while since anyone has thrown out anything new. Either it's time for summer vacations, or all the ideas have run out?
Most people want both small size and the ability to update, so there really isn't much to talk about.