MID server not starting due to parentheses in the home folder's path, leaving MID Server Down after Upgrades - Known Error

MID server not starting due to parentheses in the home folder's path, leaving MID Server Down after Upgrades Description Having a parenthesis '(' ')' in the mid server path fails upgrades when upgrading from the Yokohama version.

Note: This problem is specific to the Set-FolderPermissions.ps1 script. A similar problem exists for start.bat: PRB1942577 KB2536752 Mid Server with a closing parenthesis ')' in the windows service name, doesn't start itself after upgrading, leaving the MID Server Down

Steps to Reproduce

Create a MID Server with a parenthesis '()' in the path. Run start.bat and notice that it fails with this line: \ was unexpected at this time. The upgrade log will include a "was unexpected at this time" syntax error specific to the Set-FolderPermissions.ps1 path:

... 2025-08-12 11:00:14+0100 (226) | INFO | Copying files to MID server installation path. Copying attempt (1/5). 2025-08-12 11:00:23+0100 (633) | INFO | Finished copying files. 2025-08-12 11:00:23+0100 (633) | INFO | Correcting file permissions for directory: C:\Program Files (x86)\Service-Now\MID001_2025\agent-new 2025-08-12 11:00:24+0100 (047) | INFO | Executing command `"C:\Program Files (x86)\Service-Now\MID001_2025\agent-new\start.bat"`. Working dir: `C:\Program Files ( x86 ) \Service-Now\MID001_2025\agent-new`. Current user: `MID001$`. 2025-08-12 11:00:24+0100 (845) | INFO | Execution result: ExitCode=255 Output=\Service-Now\STUVWSMID001_2025\agent-new\bin\scripts\ Set-FolderPermissions.ps1] was unexpected at this time.

Workaround This problem has been fixed. If an upgrade is possible, please refer to the Fixed In section to determine the latest version with a permanent fix that the instance can be upgraded to.

To avoid the problem when installing a new MID Server, use parent folders that have no parentheses, or remove the parentheses from folder names first, and don't include parentheses in the MID Server name either.

If this problem was seen during the upgrade process, please follow the steps below to prevent the same happening next patch:

Log on to mid server host. Stop the MID server service. Rename the folder, by removing the parenthesis, perhaps adding underscores instead. Once the folder is renamed, open Command Prompt as an Administrator. Change directory to " \agent\bin" run the command below: mid.bat update This will the update the windows service to the updated path. Start the service. Related Problem: PRB1898139