After installing Pollination, all LB, HB and DF plugins went red + are leabeled OLD

Hi there, I’m a bit stuck here. I’ve been working fine with the LadyBug 1.8.0 version, then updated to 1.9.0 a month ago. Then I’ve installed Pollination and all the Grasshopper components turned red saying:

  1. Solution exception:No data is available for encoding 0. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

I tried even the latest Pollination version (plugins_release_PollinationGHInstaller-1.66.28) but the problem persists.

My Rhino is currently on this version:
Version 8 SR29
(8.29.26063.11001, 2026-03-04)

Or is there something wrong with my Windows or .NET ?

Windows 11 Education, 25H2 10.0.26200 Build 26200.8037

Microsoft ASP.NET Core 8.0.14 - Shared Framework (x64)
8.0.14.25112 | Microsoft Corporation | 23.09.2025

I’ve also spotted this thread elsewhere, seems like the same type of problem.

Hi @simonprokop , I had this issue a couple of weeks ago. You can check this post if it helps

1 Like

Thank you for trying to help, @asisnath but I can see that @simonprokop 's exception message is very different from the ones that you were getting recently and it appears to match the one that Natasia reported on the LBT forum, which somehow fell through the cracks a few months ago.

Let me see if I can recreate it with the instructions Natasia gave and post back here.

In the meantime, you might want to try some of the things that Natasia recommended, @simonprokop (eg. removing any components that might be importing the codecs library or running Rhino as admin).

1 Like

Hey @simonprokop ,

Just to rule out some possible explanations, is there a chance that you have a non-ASCII character in your username?

Also, I have a sense that this error might be triggered by an update of Rhino 8 rather than an update of Ladybug Tools since we haven’t changed anything about the line of code that is causing the failure in several years. Is there a chance that there was an update to Rhino 8 (or a switch between Rhino 7 and 8) sometime around when you started noticing this error?