It seems to be a common issue that renaming a file after writing it fails because of indexer of virus scanner access.
I think this https://stackoverflow.com/questions/11021639/overwriting-files-in-windows-by-renaming-randomly-fails post matches our issue.
I am not sure if the ReplaceFileA Api function is able to work around it: https://docs.microsoft.com/de-de/windows/win32/api/winbase/nf-winbase-replacefilea?redirectedfrom=MSDN
Maybe it fixes the issue of multiple file handlers when accessing the Windows API via QFile.
This will be at least a workaround for the birth time issue in https://bugs.launchpad.net/mixxx/+bug/1955314
It seems to be a common issue that renaming a file after writing it fails because of indexer of virus scanner access.
I think this https:/ /stackoverflow. com/questions/ 11021639/ overwriting- files-in- windows- by-renaming- randomly- fails post matches our issue.
I am not sure if the ReplaceFileA Api function is able to work around it: /docs.microsoft .com/de- de/windows/ win32/api/ winbase/ nf-winbase- replacefilea? redirectedfrom= MSDN
https:/
Maybe it fixes the issue of multiple file handlers when accessing the Windows API via QFile.
This will be at least a workaround for the birth time issue in https:/ /bugs.launchpad .net/mixxx/ +bug/1955314