I’ve been a loyal Listary PRO user for a long time and greatly appreciate its functionality. However, since updating my laptop to Windows 11 24H2, Listary has stopped indexing.
Specifically, the application displays ‘0 items indexed,’ and attempting to rebuild the index yields no results. I’ve already tried reinstalling Listary and clearing the appdata folders, but the problem persists.
I’ve noticed other users on the forum reporting similar indexing issues. It appears the 24H2 update may have introduced permission conflicts or other incompatibilities affecting Listary’s indexing process.
Any assistance or insights would be greatly appreciated. Thank you!
It’s definitely not a general Windows 11 24H2 problem
as it works with the latest official build here.
You should have a list of Listary tasks like this
I wanted to share a solution to an issue I was experiencing with rebuilding my index. A big thank you to Lily for pointing me in the right direction!
It turns out the problem was indeed related to the BBR2 congestion control algorithm that Lily pointed out. After switching back to CUBIC, I was able to rebuild my index without any issues.
For anyone encountering similar problems, here’s how to switch your congestion control algorithm from BBR2 to CUBIC in Windows:
How to Disable BBR2 and Switch to CUBIC:
Open PowerShell as Administrator.
Run the following commands:
netsh int tcp set supplemental template=internet congestionprovider=CUBIC
netsh int tcp set supplemental template=internetcustom congestionprovider=CUBIC
netsh int tcp set supplemental template=Datacenter congestionprovider=CUBIC
netsh int tcp set supplemental template=Datacentercustom congestionprovider=CUBIC
netsh int tcp set supplemental Template=Compat CongestionProvider=CUBIC
You can copy and paste all these commands at once.
This will display your current TCP settings, including the congestion provider. Confirm that it shows “CUBIC.”
How to Re-enable BBR2 (if needed):
If you want to switch back to BBR2, use these commands:
netsh int tcp set supplemental Template=Internet CongestionProvider=bbr2
netsh int tcp set supplemental Template=Datacenter CongestionProvider=bbr2
netsh int tcp set supplemental Template=Compat CongestionProvider=bbr2
netsh int tcp set supplemental Template=DatacenterCustom CongestionProvider=bbr2
netsh int tcp set supplemental Template=InternetCustom CongestionProvider=bbr2
I hope this helps anyone facing similar index rebuild issues.
Windows does not enable BBR2 by default, but some users may have manually configured it.
Additionally, when Windows 11 24H2 was first released, many people installed it using pre-configured Windows ISOs. From what I know, many Chinese installation ISOs had BBR2 enabled by default, which caused issues with various software, including Listary.
This is the first case I’ve seen where an English system had BBR2 enabled.
My laptop was automatically updated from Windows 10 version 22H2 to Windows 11 24H2. Following the completion of the update, I began experiencing the issues described in my previous post. I believe these problems are directly related to the 24H2 update I received.
Usually, I would completely reinstall Windows for a major update like this, but as I mentioned, this update was performed automatically (I accidentally left auto-updates enabled).
