We use the
IExplorerCommand interface so that should work on both Windows 10 and Windows 11. That said, we only test on Windows 11, so if it doesn't work on Windows 10 for some unknown reason then there's not much we can do about that. If you're on Windows 10 and have some Windows development experience, then maybe you could debug the issue and tell us what's making it not work on Windows 10.
CORRECTION

Apparently Windows 10 simply does not support the relevant
AppxManifest.xml sections and ignores them, so it's not registering the context menu with File Explorer. Looks like there's no chance of a Windows 10 port as that would require a traditional installer
(not a Windows Store app; maybe might require a EV code signing certificate too) that installs and registers the context menu extension.
UPDATE

We could probably add an option to generate
*.reg files that could then be used to
configure a classic context menu. You can already do that if you write the
*.reg files yourself:
