How can I solve the problem offline servicing in Windows 10

Confirmed, Servicing Stack (64-bit) is necessary, as it was in the OOBE compatibility already.

Added Runtime Broker to it as well from the next update, same story on Win11, this was a newer component so it slipped the radar in regards to OOBE.

Thanks.
So how can I reduce the size of the iso without getting the above error?
 
So how can I reduce the size of the iso without getting the above error?
With the risk of sounding snarky, there are other components.

As stated above, try the Templates in the Components page toolbar for a quick start.
Then keep on removing things that you don't need.

Btw if you want to remove deep removals (WinSxS cleanup), disable Components - toolbar - Compatibility - Servicing Stack compatibility.
But know that then updating is only possible via Host Refresh or a reinstall.
 
With the risk of sounding snarky, there are other components.

Btw if you want to remove deep removals (WinSxS cleanup), disable Components - toolbar - Compatibility - Servicing Stack compatibility.
But know that then updating is only possible via Host Refresh or a reinstall.
As your run of the mill "home user(plus)" i have never run SFC and whatever equivalent we had in XP, never had to enable a feature, apart from net 3.5 and when im working on a captured image i would have enabled net 3.5, disabled whatever, disabled whatever capabilities before capture so winsxs is dead space to me.

Depending on how you want to work i prefer to skate around the outside and remove the things that wont affect the meat and bones of the os, keyboards languages fonts 3rd party published drivers(with a captured image i would have a full upto date(at time of build) driverstore backed up). The next step would be remove more drivers then all disabled Features.

Ive seen the numbers some of the home brewed frankenbuilds proudly boast and i can do that in my sleep ffs just by going around the outsides.

You can do quite a lot before you even touch the meat of the os.
 
Last edited:
Ive never run it but i can see why people would keep winsxs intact. To be perfectly honest a 1GB is nothing compared to what i write in a single session doing my stuff, i can easily do 30GB and over.
 
JamessJ Preset v2
Built on 17763.1 en-gb_windows_10_enterprise_ltsc_2019_x64_dvd_cd49b901.iso - not updated.
Removed 3rd party published drivers, keyboards and languages)keep what you require), .net setup cache, cache and temp files, winsxs and winsxs backup, point of sale, smart cards, defender, PE and LTSC N edition. Installed size will be about 5.5GB once a user account is created.
 

Attachments

  • v2.JPG
    v2.JPG
    189.9 KB
  • Cabhbpture.JPG
    Cabhbpture.JPG
    40.2 KB
Last edited:
JamessJ Preset v2
Built on 17763.1 en-gb_windows_10_enterprise_ltsc_2019_x64_dvd_cd49b901.iso - not updated.
Removed 3rd party published drivers, keyboards and languages)keep what you require), .net setup cache, cache and temp files, winsxs and winsxs backup, point of sale, smart cards, defender, PE and LTSC N edition. Installed size will be about 5.5GB once a user account is created.
Thanks brother, it works perfectly for me.
 
Of course it works, ive been using that same basic configuration since nlite n xp.
Not knowing your requirements i kept things i would remove, anything for Host Refresh(popular), MS Office etc.
 
Yes but thanks I finished my iso I will publish the iso tomorrow

is it legal?

no it is not, rather it has activation or not. you can only share your guide. sharing homebrew iso is just nonsense it is not tailor made for downloader and also can contain malicious codes. I can easly share an ISO and steal anything you got. people download homebrew repacks and ISOs don't understand the risks. same goes for the people share them. someone could easly report you. like me.
 
Last edited:
is it legal to publish a customized M$ OS ISO online on any community forums :)
No, you're violating the EULA where it explicitly covers redistribution or modification.

You're not prevented from sharing instructions or tools, but users must modify the ISO themselves. Releasing a working custom ISO can be a DCMA strike. MS is too busy to check every site, but NTLite community is not allowed to upload ISO's.

Sharing a preset is the best way. Users can adapt it to their needs unlike a modded ISO, where removed packages cannot be restored.
We're not trying to pick on you. This discussion comes up many times.
 
All it takes is the wrong person in the right place at the right time and boom we get a strike and that person will be all over us like flies on poo.
 
Back
Top