I’ve made a couple of updates to phreplace and created a new version 2.0.24 which is available here. The changes include:

• Handling an exception that occurs in the vbscript Regex object when using a badly formed regular expression (e.g. reader.(\w)+\(reader.GetOrdinal\(“(\w)+”)); – note I forgot to escape the last parenthesis).
• Added Write to Log option (which defaults to off) to write some debugging log events to a ‘phreplace.log’ file in the same folder as the ‘phreplace.dll’ library. This should help identify the issue for a user where the latest version of phreplace just doesn’t open (no error – no nothing).
• Not a change but rather a note: Tried to understand the vbscript Regex object’s handling of ‘.’. Apparently it matches a new line (\n) but not a carriage return (\r) which is why doing a replace all with ^(.+)$  was acting  strange, try this instead ^([^\r\n]+)$.