http://bugs.winehq.org/show_bug.cgi?id=59550 --- Comment #5 from smcclenahan@gmail.com --- I am unable to reproduce my particular use case at this time because it was a software update process which has since successfully completed so I won't get the error again like I always do until another update to the game is released. I don't know if or how I can profile the commercial application/game, maybe I can add some logging or debugging when I launch via Crossover and wait for the next update? I am not maintaining multiple versions I can test or rollback to, sorry. I have observed that the error has happened every single time there has been a software update (at least for this game, every month or so), the workaround is to just ignore it and manually restart but I'm trying to address the root cause for a smoother update for this and any other game with this known issue. I tested manually a command with / options and both \ and /-delimited path inside a Wine cmd session and it indeed works there: Z:\>cmd /c C:/windows/system32/attrib.exe (Success) However, I'm sure the failure will re-occur when the command is called programmatically from the game engine. This suggests the parsing discrepancy in wcmd occurs during the initial process startup (the transition from CreateProcessW arguments to wcmd's internal state?), rather than within the interactive shell parser. The exact failure log remains: Can't recognize 'C:/users/crossover/Documents/My Games/Borderlands 4/Saved/PersistentDownloadDir/GbxRelaunch.bat' as an internal or external command This indicates that when wcmd receives this string as its starting argument via /c from an external process (e.g. main game engine binary Unreal Engine 5), it is misinterpreting the first forward slash in the path as a switch. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.