3.8.1 - Data protection during the restore disk permissions, folders or files.

[makinero]

Use Tweaking.com 3.8.1 Restoring privileges to the disk while the disk are written to the file can cause corrupted to the structure of files and need run CHKDSK.

[Shane]

Settings permissions shouldnt corrupt anything. The program calls the Windows API and windows does it. if the file system already has corruptions then that could do it.

I am not sure what I am seeing in the screen shot you posted. Can you explain?

Shane

[makinero]

Eg. I restore the permission to the multi-million files after a certain time it shows "ManageACL_64.exe" - Corrupt File and should run CHKDSK.
The application not restore permissions on the local disk for example E: . . . Z:


Google:

"ManageACL process designed by Tweaking.com, This file not necessary for your system"

https://msdn.microsoft.com/en-us/library/bb470212%28v=vs.85%29.aspx

Code: [Select]

Remarks

Note that there is no associated header file for this structure.

This structure definition is valid only for major version 3 and minor version 0 or 1, as reported by FSCTL_GET_NTFS_VOLUME_DATA.

The multisector header and update sequence array provide detection of incomplete multisector transfers for devices that either have a physical sector size greater than or equal to the sequence number stride (512) or that do not transfer sectors out of order. If a device exists that has a sector size smaller than the sequence number stride and it sometimes transfers sectors out of order, then the update sequence array will not provide absolute detection of incomplete transfers. The sequence number stride is set to a small enough number to provide absolute protection for all known hard disks. It is not set any smaller or there might be excessive run time or space overhead.

The update sequence array consists of an array of n USHORT values, where n is the size of the structure being protected divided by the sequence number stride. The first word contains the update sequence number, which is a cyclical counter of the number of times the containing structure has been written to disk. Next are the n saved USHORT values that were overwritten by the update sequence number the last time the containing structure was written to disk.

Each time the protected structure is about to be written to disk, the last word in each sequence number stride is saved to its respective position in the sequence number array, then it is overwritten with the next update sequence number. After the write, or whenever the structure is read, the saved word from the sequence number array is restored to its actual position in the structure. Before restoring the saved words on reads, all the sequence numbers at the end of each stride are compared with the actual sequence number at the start of the array. If any of these comparisons are not equal, then a failed multisector transfer has been detected.

The size of the array is determined by the size of the containing structure. The update sequence array should be included at the end of the header of the structure it is protecting because of its variable size. The user must ensure that the correct space is reserved for the containing structure: (size of structure / 512 + 1) * sizeof(USHORT).
Error:
MULTI_SECTOR_HEADER structure for VCN 0x11 OR 0x12 OR 0x13 index $I30