Homegroup - Add or Remove from Navigation Pane

Ritjesman said:

Update2: The plot thickens. Using regedit find (& runassystem) for:
B4FB3F98-C1EA-428d-A78A-D1F5659CBA93


I find 4 instances with the Shell Folder\Attribute subs all set to 0xb094010c and HomeGroup is still showing in explorer. When I use a tool called Registry Finder (Registry Finder) it finds a plethora of entries for B4FB3F98-C1EA-428d-A78A-D1F5659CBA93. Searching for b094010c it only finds 3 instances. Searching for b084010c gets us 2 instances:

So a total of 5 instances, one less of the Delete code than expected, 1 that this tool is showing with Add code that's displaying as a Delete code via regedit and 1 (HKEY_LOCAL_MACHINE) that I'm not seeing via regedit.


Searching for b094010c or b084010c using regedit find w/keys, values and data all checked results in "not found". I'll defer to you to interpret these findings.

Usually, you will only need to do as outlined in the tutorial.

Brink said:

Usually, you will only need to do as outlined in the tutorial.

Hi Shawn - I've just completed a fresh install (as at of prep for migration to Win10). The only non-standard aspect of this set up is consolidation of System an C: into a single partition boot disk using EasyBCD which I believe only copies boot required files.


Ran through the steps per the tutorial and rebooted. While having a fresh install eliminated all of the anomalies from above I've still got this situation:



So now I confidently state that -- for whatever reason -- the regedit approach does not work on this computer.


'Nuff said & 'nuff time spent on this for both of us.

Ritjesman said:

Hi Shawn - I've just completed a fresh install (as at of prep for migration to Win10). The only non-standard aspect of this set up is consolidation of System an C: into a single partition boot disk using EasyBCD which I believe only copies boot required files.


Ran through the steps per the tutorial and rebooted. While having a fresh install eliminated all of the anomalies from above I've still got this situation:

So now I confidently state that -- for whatever reason -- the regedit approach does not work on this computer.


'Nuff said & 'nuff time spent on this for both of us.

Just to confirm, did you do both steps 8 and 9 and restart the computer afterwards?

Your screenshot shows the registry path for step 8, but the change must also be made below from step 9 in 64-bit Windows 10.

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B4FB3F98-C1EA-428d-A78A-D1F5659CBA93}\ShellFolder

Brink said:

Just to confirm, did you do both steps 8 and 9 and restart the computer afterwards?

Your screenshot shows the registry path for step 8, but the change must also be made below from step 9 in 64-bit Windows 10.

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{B4FB3F98-C1EA-428d-A78A-D1F5659CBA93}\ShellFolder

Hmmm ... I interpreted that as only needed for also removing from "open" and "save" dialogues; will give it a try ...

Ritjesman said:

Hmmm ... I interpreted that as only needed for also removing from "open" and "save" dialogues; will give it a try ...

Actually, since I searched on B4FB3F98-C1EA-428d-A78A-D1F5659CBA93 in regedit (rather than navigating to the key) I had already done the WOW change also:



So, unfortunately, nope, regedit approach not working on my (obviously peculiar) setup & those are the only instances of B4FB3F98-C1EA-428d-A78A-D1F5659CBA93 with Shell Folders found.

@Ritjesman,

I just tested on a Windows 7 VM on my system to see if anything may have changed, but it still works for me after making the two registry changes and restarting the computer to apply.

Odd why it's not working for you since you show the correct changes in your registry.

Computers --- don't ya just love 'em?