Only for Gimp-2.10.xx Win10 64bit
Explanation read here.

Place files in this location:
c:\Program Files\GIMP 2\lib\gegl-0.4\plug-ins\

Official GEGL Bevel




Official GEGL Inner Glow

Make sure to rename official inner glow because both the plugin and it share the same `inner-glow.so` name. All you have to do is rename it to `inner-glow2.so` GIMP 3 doesn't have this problem because its stored differently. If this plugin is used in GIMP 3 it will crash it because two plugins cannot share the same enum list naming. If two plugins have the same name on a drop down list they crash GIMP

Is `c:\Program Files\GIMP 2\lib\gegl-0.4\plug-ins\` and `c:\Program Files\GIMP 3\lib\gegl-0.4\plug-ins\` valid directories on Windows? I always tell users to put the binaries in ` C:\Users\(USERNAME)\AppData\Local\gegl-0.4\plug-ins` and the last time I checked 5 months ago on Windows 10 GIMP 3.0.4 and 2.10 that is a valid directory

A few things for Windows:

1. C:\Users\(USERNAME)\AppData\Local\gegl-0.4\plug-ins this is a localization for all versions of Gimp (except for the portable version Gimp-2.10 samj).
2. ... lib\gegl-0.4\plug-ins\ is the localization for a specific version of Gimp.
3. If users of both Gimp-2.10 and Gimp-3 placed the files Official GEGL Bevel.dll and Official GEGL Inner-Glow.dll in the C:\Users\(USERNAME)\AppData\Local\gegl-0.4\plug-ins directory in Gimp-3 they would be loaded twice (from that directory and as a built-in plugin), which is not a good practice.
4. The choice of the name of the 'plug-ins' directory may not have been the luckiest (because it was used for the third time), but let's leave it that way (although instead of plug-ins it could be named anything you want, e.g. WindowsBinaries and/or vibe_coded_windows).
5. Compiling two Gimp plugins takes very little time, so I wonder why you waited?

official innerglow has to have its binary renamed manually so it loads on GIMP 2.10 alongside lb:innerglow. Unless they are in different folders. ( i think)