worm retention period not working as expected

On a TVS-h674 running QuTS hero h6.0.2.3591, an Enterprise WORM share has always had 31-day retention and a 5-hour, 1-minute auto-lock delay. A file whose NAS timestamps are 28 June 2026 returns “The media is write protected” when deleted over SMB. The Network Recycle Bin is disabled; the storage pool shows Ready; and a newly created test file in the same directory can be created and immediately deleted. The NAS has only had brief firmware-update reboots. Is there a supported read-only way to inspect that file’s WORM state/expiry and the pool’s WORM clock, or a known h6.0.2 issue with deleting expired WORM files over SMB or File Station?

Thanks for your question! May we ask whether your NAS is usually powered on 24/7? We’ll look into this internally.

Thanks for the report! Our internal team was able to reproduce this: files that were locked on QuTS hero h6.0.1 and then upgraded to h6.0.2 during the retention period can’t be deleted after the retention period expires. WORM shares configured directly on h6.0.2 work as expected, and our team is looking into a fix.