http://bugs.winehq.org/show_bug.cgi?id=37789 --- Comment #10 from Mykola Mykhno <klimmihno5+wine+bugzilla@gmail.com> --- Comment on attachment 80771 --> http://bugs.winehq.org/attachment.cgi?id=80771 Add a second set of illegal characters for the quotes strip to add support for parentheses in path or file names. This bug relates to the rules for stripping quotes. Prior to XP Professional x64 Edition, logic was that special characters such as: &,<>,()@^ were forbidden in quotes. Quotes must be stripped if any of these characters appear in a parameter. This logic is documented in the cmd.exe documentation at MSDN. However, after XP Professional x64 Edition, Microsoft added the "Program Files (x86)" directory, and it seems like they removed parentheses from the list of forbidden characters in quotes. The documentation doesn't mention it. To check this hypothesis, I have checked that XP Professional SP 2 x32 bit strips quotes when it finds parentheses in a parameter passed with /C, and XP Professional x64 Edition and all versions after it, whether 32 or 64 bit, preserve quotation marks when parentheses are in a parameter. Also, I checked that XP Professional x64 Edition is based already on NT 5.2, same with Windows Server 2003. So, the solution is basically to add a condition at https://gitlab.winehq.org/wine/wine/-/blob/master/programs/cmd/wcmdmain.c#L4... that will check the version. If the version is prior to 5.2, then use the list of special characters with parentheses. If the version is greater than 5.2, then use the list without parentheses. -- 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.