Changing only the Service Name or the File Name will result in a profile that could have file or service name conflicts, and the service package might fail to install. You should either create a new profile by changing both the service name and the file name, or restore the original name so that it will cleanly overwrite the existing profile. Would you like to return to Service and File Names?
Changes to Summary properties could not be saved; access has been denied. The file may be marked read-only or may be in use ...
Changes to the view of a console file are saved in your profile. The files in your profile that store these console changes ...
Changes will be made to the system registry, however the user session now active on the %s connection will not be changed. ...
Changes will be made to the system registry, however the user sessions now active on the %s connection will not be changed. ...
Changing only the Service Name or the File Name will result in a profile that could have file or service name conflicts, ...
Changing the active partition on a disk might make the disk not startable if the partition does not have valid system files. ...
Changing the async device for connection %s will cause it to be recreated with the new device. If you continue with this ...
Changing the drive letter of a volume might cause programs to no longer run. Are you sure you want to change this drive letter? ...
Changing the license mode to Per Device or Per User will result in current Per Server license loss. Press F1 for further ...