Re: capture wim compatible with windows7 setup.exe
Posted: Thu Jan 21, 2016 12:20 am
@larsm
The --flags option actually controls the FLAGS element in the XML document. So the equivalent would be --image-property FLAGS=[your value here]. It could be added to 'wiminfo' but I'd rather consider the --flags option deprecated now that wimlib automatically sets the Windows-specific XML information on newly captured images and the more general --image-property option is available.
@bliblubli
First of all, if you're creating archives from a live Windows system then the filesystem absolutely will change even if you "aren't doing anything". Windows has many services running in the background.
The case with Windows PE is a little more mysterious. Are you saying you still used the --snapshot option even though the system wasn't live? That's not really necessary, but perhaps what you observed is an artifact of wimlib selecting to back up the "bootable system state" while creating the snapshot. Can you please provide more detail about exactly what files changed?
The --flags option actually controls the FLAGS element in the XML document. So the equivalent would be --image-property FLAGS=[your value here]. It could be added to 'wiminfo' but I'd rather consider the --flags option deprecated now that wimlib automatically sets the Windows-specific XML information on newly captured images and the more general --image-property option is available.
@bliblubli
First of all, if you're creating archives from a live Windows system then the filesystem absolutely will change even if you "aren't doing anything". Windows has many services running in the background.
The case with Windows PE is a little more mysterious. Are you saying you still used the --snapshot option even though the system wasn't live? That's not really necessary, but perhaps what you observed is an artifact of wimlib selecting to back up the "bootable system state" while creating the snapshot. Can you please provide more detail about exactly what files changed?