Comment by skissane

On further research, I believe you are correct.

I am just surprised that Microsoft would change the default behaviour of DeleteFileW in a Windows 10 build. It seems like the kind of thing that would cause backward compatibility issues. Indeed, I've even found people reporting things breaking due to this [1]. Maybe Microsoft's culture doesn't put the same emphasis on backward compatibility that it used to?

[1] https://stackoverflow.com/questions/60424732/did-the-behavio...