Registry macros in custom rule path strings are expanded with backslash added
It seems that is not possible to compose a file name from elements stored in the registry.
Creating a custom registry rule using macros results in an extra backslash.
6.0.2 and lower agents assume that all macros target directories or full paths. Therefore they automatically append a "\" for any pattern that has additional text after the macro. 7.x agents, will not add this slash for registry based macros, but will for all macro types.