I think you should try two approaches:
(1) Changing the file encoding
As mentioned in the comments, �
is a replacement of a invalid character in the selected encoding.
First, check that the column data type is DT_WSTR
not DT_STR
**
Also, try setting the encoding to Unicode
or try using a encoding detection tool such as:
But i don't think until now there is a powerful encoding detection application or library where all encodings are supported
To change the flat file connection manager encoding, you can check the Unicode checkbox or select a Code Page from the drop down list:

(2) Removing unwanted characters
If you don't have a problem with encodings and you know the right file encoding, if the file creation is not done correctly, these �
characters have no meaning and cannot be reverted, you must check the file creation operation and check if there is a problem or difference between the data source encodings or collation and the flat file encoding.
Or you should remove these characters using a script component or derived column:
(DT_WSTR,1000)REPLACE([Comments] ,"�","")
*Note: Don't use N
literal before the �
mark and don't convert to DT_STR
since it might be other unicode characters that cannot be converted.
Additional information