Java Development Kit (JDK) 25 introduces significant changes to how file operations are handled on Windows, aimed at enhancing safety and consistency. One of the key updates is to the <code>File.delete()</code> command, which will now fail when attempting to delete read-only files. Previously, the command would automatically remove the read-only attribute before deletion, but developers must now explicitly clear these attributes themselves.
Furthermore, file operations involving pathnames containing trailing spaces will now consistently result in failure. Trailing spaces in pathnames have always been illegal on Windows, and this update ensures that operations on such paths fail uniformly.
To assist with migration and allow applications time to adapt, a system property <code>-Djdk.io.File.allowDeleteReadOnlyFiles=true</code> is available. This property can temporarily restore the legacy behavior of allowing the deletion of read-only files without manually clearing attributes. These changes in JDK 25 underscore a focus on improved safety and adherence to Windows file system standards.

Collections

JDK 25 introduces breaking changes to Windows file operations for improved safety. The File.delete() method now fails when attempting to delete read-only files instead of automatically removing the read-only attribute. File operations with trailing spaces in pathnames will consistently fail. A temporary system property -Djdk.io.File.allowDeleteReadOnlyFiles=true is available to restore legacy behavior during migration.

JDK 25: Updates to Windows File Operation Behaviors