Auto Delete of VHD/VHDX if Corrupt
When a container is becoming corrupt we are finding that the VHD/VHDX is stuck on 0MB and is pretty much useless. Rather than troubleshooting/manually deleting the container it would be good if a GPO could attempt to re-create a fresh container on logon rather than mounting the same container that is obviously corrupt.
If a there was a configurable GPO that could for example delete and re-create any container that was <500mb then it would fix the corrupt container itself by re-creating it.
This is being tracked for possible inclusion. Other than size, what variables would need to be considered (if any)?
Ross White commented
Containers are continuingly corrupting which FSLogix have confrimed happens when a hard reset is performed. Thich means OST files are becoming corrupt and Windows Search is not being enabled. We really need a solution for this.