Invoke Power Shell Windows long path prefix Bug

Windows has a path length limit of 260 characters a workaround for this is to use a \\?\ prefix. Such a prefix works when using a regular PowerShell however using it in UiPath’s Invoke Power Shell activity it doesn’t seemed to be recognized as seen below:

Regular PS:

Invoke Power Shell activity:

Is there a difference between the UiPath’s PowerShell and a regular one? From what I can see versions are the same:

Please let me know whether there’s a workaround to this bug.