[Bug] Cache failing to delete file when restarting resource

[WLVF]

Summary

Whenever you change the code in a resource's client code and then ensure or restart it, you get an error from the relevant server-cache file trying to be deleted but failing because it's in-use by another process.

Error example:
Error deleting file F:/FiveM/_FiveMEnhanced/server-cache/51693ed181e6383e51401d0905f880ca3ff47cce/40f07c4e6e4dd93175fed35abb91289f9aa7d4ad/827315ba6a70dfabefe99c6e03d92b3debbc5118: remove: The process cannot access the file because it is being used by another process.: "F:/FiveM/_FiveMEnhanced/server-cache/51693ed181e6383e51401d0905f880ca3ff47cce/40f07c4e6e4dd93175fed35abb91289f9aa7d4ad/827315ba6a70dfabefe99c6e03d92b3debbc5118"

The print is coming from vfs-core in the log.

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b92 win32

OS

WIndows 11 Home 25H2

CPU

AMD Ryzen 9 7900X

GPU

NVIDIA RTX 3080

RAM

64 GB DDR5

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Localhost

CPU

Same as above

RAM

Same as above

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Create a test resource with a LUA client file defined in the fxmanifest.lua
2. Add some content into the defined client file. In my case, I just put print("Hello world").
3. Ensure the resource.
4. Change the content of the client file. In my case, I put print("Hello world part 2").
5. Error is shown in F8 console

Expected Behavior

The resource's outdated file should be cleared from the user's server-cache directory.

Actual Behavior

The resource's outdated file fails to be immediately replaced with the new cache file and leaves behind an outdated cache file.

Any ensure command used in the future for that resource clears up the old "trailing" cache file. So, if the content doesn't change, the old cache file that isn't the current one will be cleaned up. If the content does change, a new trailing outdated cache file is made.

Evidence

https://streamable.com/0to7rg

Additional Context

No response

[Gogsi]

A fix for this bug has been implemented and is available in the latest patch b95. Please try again and let us know if the issue persists. Thanks for your help!