OpenSource Ghost
Member
I don't think there is a way to prevent failures of component store and file integrity verification when too many items are removed, but having a custom attestation feature can be of great help.
In other words, taking image/"snapshot"/state of exising OS files, registry, and components and making OS (DISM, SFC) label them as healthy base to compare against future changes is what would be of help. Typical 1:1 OS drive image backup made by third party software performs attestation against the entire image, not just OS files.
In other words, taking image/"snapshot"/state of exising OS files, registry, and components and making OS (DISM, SFC) label them as healthy base to compare against future changes is what would be of help. Typical 1:1 OS drive image backup made by third party software performs attestation against the entire image, not just OS files.
Last edited: