Sheridan Posted July 20, 2017 Posted July 20, 2017 I take it there still isn't a clean (i.e GPO!) way to hide the Quick Access folders in W10? I've searched and can't find anything other than a lot of people who want to remove it! I've tried the registry method but it seems flakey and causes the File Explorer to error out sometimes as well.
Chuckster Posted July 20, 2017 Posted July 20, 2017 Here's the reg to modify it.. Windows Registry Editor Version 5.00 ; Disable Quick Access ; For 32-bit and 64-bit Machines [HKEY_CLASSES_ROOT\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder] "Attributes"=dword:a0600000 ; For 64-bit Machines Only [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder] "Attributes"=dword:a0600000 The registry modification is required in 2 separate locations if it's 64-bit machine, otherwise it's only one location modification if 32-bit. 1
Sheridan Posted July 20, 2017 Author Posted July 20, 2017 That looks familiar, although I confess I didn't do both 32 and 64 bit hives! Have you pushed this out using a GPO preference or scripted it? I know those reg entries need their permissions changed to access them Here's the reg to modify it.. Windows Registry Editor Version 5.00 ; Disable Quick Access ; For 32-bit and 64-bit Machines [HKEY_CLASSES_ROOT\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder] "Attributes"=dword:a0600000 ; For 64-bit Machines Only [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder] "Attributes"=dword:a0600000 The registry modification is required in 2 separate locations if it's 64-bit machine, otherwise it's only one location modification if 32-bit.
Chuckster Posted July 20, 2017 Posted July 20, 2017 I have the the code in a .REG file and then have a .BAT file running as a startup script with the following.. @echo off %windir%\regedit.exe /s "\\school.internal\netlogon\Startup\Windows 10\Disable Quick Access x64.reg"
Sheridan Posted July 20, 2017 Author Posted July 20, 2017 Cheers, I'll give it a try that way, I'd been doing it manually on some test PCs to see if it worked. It did work but they got errors when clicking the file explorer in the task bar for some reason.
Chuckster Posted July 21, 2017 Posted July 21, 2017 If that happens, then you need to tell File Explorer to default to 'This PC' and not Quick Access when launched. Windows Registry Editor Version 5.00 ; Open File Explorer to This PC as default [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "LaunchTo"=dword:00000001 1
Sheridan Posted July 21, 2017 Author Posted July 21, 2017 It doesn't seem to work if you put those registry entries in as Computer Preferences in a GPO - shame really as I thought that was the better way to add registry entries these days I wonder if its down to the permissions on those keys?
Chuckster Posted July 21, 2017 Posted July 21, 2017 I am terribly sorry... I am doing a half-bake job on this. You need to do the following... Download SetACL from here: https://helgeklein.com/download/ Place the SetACL.exe in the Netlogon folder. Put the following in a .BAT file and apply it as a startup in your GPO. @echo off \\school.internal\netlogon\SetACL\x64\SetACL.exe -on "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder" -ot reg -actn setowner -ownr n:Administrators \\school.internal\netlogon\SetACL\x64\SetACL.exe -on "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder" -ot reg -actn ace -ace "n:Administrators;p:full" \\school.internal\netlogon\SetACL\x64\SetACL.exe -on "HKEY_CLASSES_ROOT\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder" -ot reg -actn setowner -ownr n:Administrators \\school.internal\netlogon\SetACL\x64\SetACL.exe -on "HKEY_CLASSES_ROOT\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder" -ot reg -actn ace -ace "n:Administrators;p:full" All my workstations are 64-bit, so the above is applicable to that. I've never tried it on a 32-bit.
Sheridan Posted July 21, 2017 Author Posted July 21, 2017 Ahh that makes sense, theres some restrictive permissions on those keys so it explain why normal preferences aren't being applied!
Scorpio Posted October 4, 2017 Posted October 4, 2017 (edited) Ive found a new cleaner way: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer Create a DWORD value named HubMode and set its value data to 1 Scorpz Edited October 4, 2017 by Scorpio
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now