The section objects are created with `OBJ_PERMANENT` and a specific sharing mode (`FILE_SHARE_READ | FILE_SHARE_DELETE`) by wineboot, and it's done once for each prefix architecture (system32/syswow64). That permanent object is still open on the second go-around (next architecture), so when the setup tried to open that object with a different sharing mode, it ran into `ERROR_SHARING_VIOLATION`. Refer to this documentation if that still wasn't clear: https://learn.microsoft.com/en-us/windows/win32/fileio/creating-and-opening-... https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-creat... https://learn.microsoft.com/en-us/windows/win32/api/ntdef/ns-ntdef-_object_a... -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7705#note_99857