Script install of 1903 windows 10 update

If you already have and use WSUS, I'd use it. Where'd you get that advice?

Ok thanks, we use wsus, I've added the product 'windows 10 1903 and later' as guide, do I then need to sync 'feature packs' as the classification?

No, you don't need to sync the Feature Packs classification.

Maybe the 'upgrades' classification?

This is what I select in my environment:


This is what all the classifications represent:

Critical Updates: Specifies a widely released fix for a specific problem that addresses a critical, non-security-related bug.

Definition Updates: Specifies a widely released and frequent software update that contains additions to a product's definition database.

Feature Packs: Specifies new product functionality that are first distributed outside of a product release and that are typically included in the next full product release.

Security Updates: Specifies a widely released fix for a product-specific, security-related vulnerability.

Service Packs: Specifies a tested, cumulative set of all hotfixes, security updates, critical updates, and updates that are applied to a product. Additionally, service packs may contain additional fixes for problems that are found internally since the release of the product.

Tools: Specifies a utility or feature that helps to complete one or more tasks.

Update Rollups: Specifies a tested, cumulative set of hotfixes, security updates, critical updates, and updates that are packaged together for easy deployment. An update rollup generally addresses a specific area, such as a security or product component.

Updates: Specifies a widely released fix for a specific problem. An update addresses a non-critical, non-security-related bug.

Upgrade: Specifies an upgrade for Windows 10 features and functionality. Your software update points and sites must run a minimum of WSUS 4.0 with the hotfix 3095113 to get the Upgrade classification.

Thanks for all the replies, I will look at all the options, whichever method I go with testing has shown it leaves a 30GB windows.old folder, is there a simple way to script the removal after install or maybe even prevent creation?

Thanks

You would need to run Disk Cleanup in System Mode (cleanup system files) after 30 days.  It could be scheduled to run in Task Scheduler with Admin Privileges.

The contents of the folder will go away on its own and there is generally no rush to force its removal.

Thanks, I think disk cleanup has been deprecated to 'Storage Sense'. I dont mind what I use but I would prefer a command line to run the cleanup, can you please advise?

Disk cleanup (cleanmgr.exe) still works on the newest version of win10. Storage sense should be preferred, but for scripted cleanup, cleanmgr.exe still works.

You need to indicate whether it still matters to clean it up at once, since windows will automatically purge these folders after 10 days.
To do it with cleanmgr, you would need to get familiar with the documented parameters sagerun and sageset.

hey I can wait 10 days, so that windows.old folder will just disappear after 10 days, no config required? ive noticed n my newly installed PC storage sense is not set to on by default.

It will just disappear.

Yes, agree.  I also noted that above.