This issue still exists in v 1.8.0.448:
Registry Cleaner - Custom fix bug
Some "file does not exist" error types are handled incorrectly by the "Fix manually …" feature.
The screenshot shows the situation.
When you click OK, the bug does the following:
1. uses the data in the "Fix manually …" input box as an entry name
2. causes a new erroneous entry to be put in the registry
3. does not correct the original error which stays in the registry
Notes:
PT2007 contains the same bug
PT2006 handles this type change correctly (it knows the data is data, not an entry name)