File permission errors in newer versions
Posted: 08 Sep 2020, 19:49
Hi Michael,
Long time AllDup user here. Thank you for this wonderful piece of software!
I have used AllDup to slim down Windows system partitions by hardlinking duplicate system files regularly for many years. I would always do his on an offline Windows installation, booting form another partition/system. All through AllDup version 4.2, I never had any issues with replacing system files with hardlinks on an offline Windows installation.
Recently, I was unable to complete this routine task (for me, fwiw) using the latest version, 4.4.34, due to getting an appalling number of file permission errors. The latest version refuses to either delete or move to Recycle Bin any file I do not specifically have the appropriate permission for. Even though I run it elevated, as administrator, many system files are still untouchable (usually owned by SYSTEM or TRUSTEDINSTALLER).
There was a very fundamental change between versions 4.2 and 4.4.34 in how ACLs are treated. 4.2. just glossed over missing permissions and executed whatever I told it to do. 4.4.34 is picky, and respects file permissions strictly.
From my point of view, this is a regression - but I can see how, from a general aspect, it could rather be a fix of an earlier omission. Unfortunately, I can not find any trace of this change in the version history, thus have no idea if this change is even intentional at all.
Michael, would you mind, please, shedding some light on this issue?
Thanks,
George
Long time AllDup user here. Thank you for this wonderful piece of software!
I have used AllDup to slim down Windows system partitions by hardlinking duplicate system files regularly for many years. I would always do his on an offline Windows installation, booting form another partition/system. All through AllDup version 4.2, I never had any issues with replacing system files with hardlinks on an offline Windows installation.
Recently, I was unable to complete this routine task (for me, fwiw) using the latest version, 4.4.34, due to getting an appalling number of file permission errors. The latest version refuses to either delete or move to Recycle Bin any file I do not specifically have the appropriate permission for. Even though I run it elevated, as administrator, many system files are still untouchable (usually owned by SYSTEM or TRUSTEDINSTALLER).
There was a very fundamental change between versions 4.2 and 4.4.34 in how ACLs are treated. 4.2. just glossed over missing permissions and executed whatever I told it to do. 4.4.34 is picky, and respects file permissions strictly.
From my point of view, this is a regression - but I can see how, from a general aspect, it could rather be a fix of an earlier omission. Unfortunately, I can not find any trace of this change in the version history, thus have no idea if this change is even intentional at all.
Michael, would you mind, please, shedding some light on this issue?
Thanks,
George