• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

UNC Path doesn't work, mapped drive does, powershell does...

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Well, it wasn't the key that was causing the problem directly. It was a permissions change to that folder of the registry. When the policies were built for the new environment, the inheritance option wasn't selected and thus, all permissions were stripped from that path. Windows then couldn't read the keys, and Windows Explorer broke. Once the permissions are corrected and the key is properly modified, it works just as we want it to.

CASE CLOSED. 🙂
 
Back
Top