Windows path slashes not escaped
Unfortunately, eventlog analyzer does not know to escape the
slashes used by windows for its paths. I think it is important that
a hot fix to be produced to address this bug because it could
have security implications over the computer that run the eventlog
analyzer or/and the client viewing the data.
New to ADSelfService Plus?