Groupy tab colours do not persist for folders opened from File Explorer navigation pane

Groupy correctly saves and applies tab colours when I open folders through their normal filesystem paths.

However, when I open the same folders from the File Explorer navigation pane/sidebar, the saved colours do not persist or inherit. This mainly affects pinned/root locations like Google Drive and Repositories, where Explorer appears to expose them as sidebar roots rather than their actual child folder paths.

Applying a colour to a folder and its children works through normal navigation, but not when those folders are opened from the sidebar.

Is this a known Groupy limitation with Explorer navigation-pane locations, or can Groupy resolve these entries to their real paths so tab colours work consistently?

195 views 4 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues. I can't reproduce your issue. Check my screenshot below. The first "Stuff" folder open via the pinned quick access button and another one "Stuff" folder by right clicking on that same folder via left navi panel. Both have that same saved color.

So I need more information.

  1. Your Windows full version and OS Build number. Please use Winver.exe to get these numbers.
  2. Groupy full version numbers installed.
  3. Post a short video showing us how you reproduce this issue so we can try it step by step ourselves.

Thank you,

Basj,

Stardock Community  Assistant

Reply #2 Top

Thanks. I did some more digging and I think the important distinction is that this is not happening with a normal Quick Access pinned folder.

My affected sidebar entries are custom Explorer navigation-pane namespace roots, created by Winaero Tweaker:

 

Repositories:

HKCU\Software\Classes\CLSID\{628a8101-badd-4857-998e-c0659c88d723}

Instance\CLSID = {0afaced1-e828-11d1-9187-b532f1e9575d}

Instance\InitPropertyBag\Target = C:\Repositories

 

Google Drive:

HKCU\Software\Classes\CLSID\{71c269db-bacd-4608-bfff-a565bc34b218}

Instance\CLSID = {0afaced1-e828-11d1-9187-b532f1e9575d}

Instance\InitPropertyBag\Target = C:\Google Drive

 

They are also registered under:

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace

 

So Explorer resolves them to real filesystem paths, but they appear to Groupy as shell namespace/PIDL locations at least some of the time. In Groupy’s SavedColoursDocs registry data I can see both normal path entries like C:\Repositories and encoded shell/PIDL entries containing those custom CLSIDs.

 

That may explain why your normal pinned-folder test works while this case does not.

 

Windows version:

Windows 11 Home, version 25H2, OS build 26200.8655

Groupy:

Stardock Groupy2 2.3.1.1 installed at C:\Program Files (x86)\Stardock\Groupy2

 

Repro:

1. Create or use a custom Explorer navigation-pane root that targets a real folder, for example C:\Repositories.

2. In Groupy, assign a tab colour to C:\Repositories and/or child folders.

3. Open the folder through its normal filesystem path. The colour persists correctly.

4. Open the same location from the custom navigation-pane root. The colour does not consistently persist/inherit.

 

Question:

Does Groupy currently treat Explorer namespace/PIDL locations separately from their resolved filesystem paths? If so, could Groupy resolve these navigation-pane entries to their filesystem target before applying saved folder colours?

Reply #3 Top

Hello,

I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,

Stardock Community  Assistant

Reply #4 Top

Thank you. One note for reproducing this is that assigning a folder like this and all children a tab colour works temporarily but once explorer is restarted is goes back to default.