Not sure if this is a Keyman issue or a Windows issue. I’m continuing to test making packages and install them on Windows and on mobile devices; and just had a surprising result installing a test keyboard on Windows 10.
I followed the new model of adding a BCP 47 tag to the keyboard in the package, I used the tag fuh-Latn.
This installed fine into Keyman on Windows but I couldn’t figure out how to activate it. Selecting the keyboard in Keyman desktop did not activate it. I looked more closely at my language settings, and saw that Windows had installed the test keyboard under a new language string, QAA. I had to switch from EN to QAA before I could activate the keyboard.
I discovered if I added English (US) to the keyboard in the language list in Keyman configuration, I could then activate the keyboard in Keyman desktop like I was expecting to be able to do, without needing to switch from EN to QAA.
My Keyman developer build is 10.0.1056 and my Windows 10 version is Pro 1709.