Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Split-WindowsImage or Export-WindowsImage with SplitImageFilePattern better? #44

Open
aisgbnok opened this issue Aug 19, 2022 · 0 comments
Assignees
Labels
Documentation Improvements or additions to documentation Question Further information is requested

Comments

@aisgbnok
Copy link
Owner

Description

I'm not sure whether using the Split-WindowsImage cmdlet or the Export-WindowsImage cmdlet with the -SplitImageFilePattern parameter is better. I need to test this and determine if there is any difference.

Split-WindowsImage

This is a dedicated cmdlet for splitting an image into .swm files. However I'm unsure if it does any sort of optimization or cleanup like the Export-WindowsImage cmdlet.

Export-WindowsImage

This cmdlet is for exporting images, and with the -SplitImageFilePattern parameter it can create .swm files. However it also explicitly states that it optimizes images during export:

You can also optimize an image by exporting to a new image file with Export-WindowsImage. When you modify an image, DISM stores additional resource files that increase the overall size of the image. Exporting the image will remove unnecessary resource files.
Source

@aisgbnok aisgbnok added Documentation Improvements or additions to documentation Question Further information is requested labels Aug 19, 2022
@aisgbnok aisgbnok self-assigned this Aug 19, 2022
@aisgbnok aisgbnok changed the title Is Split-WindowsImage or Export-WindowsImage with SplitImageFilePattern better? Is Split-WindowsImage or Export-WindowsImage with SplitImageFilePattern better? Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Improvements or additions to documentation Question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant