Hello,
Sorry for the late reply, but only today, while troubleshooting this issue, I came across your discussion and comments.
I spent about six hours investigating the problem and finally managed to get my Sun Type 7 USB keyboard working properly under Windows 11, including not only the Russian keyboard layout, but also all of the Sun-specific keys (Help, Open, Props, Front, Stop, Again, Undo, Cut, Copy, Paste, and Find).
For anyone trying to do the same, here is the complete process that worked for me.
First, install a Mac-style keyboard layout -- MagicKeyboardLayouts-Setup-2.0 . The standard Windows layout does not match the legends printed on the Sun Type 7 keyboard. The Mac layout is much closer to the original Sun layout.
Next, verify that Windows is actually receiving the special key events. Install USBPcap and Wireshark, start a USB capture, and press each special key individually.
The keyboard sends the following HID usage codes:
74 = Open
75 = Help
76 = Props
77 = Front
78 = Stop
79 = Again
7A = Undo
7B = Cut
7C = Copy
7D = Paste
7E = Find
This proves that the keyboard is functioning correctly and that Windows receives the key presses. The real problem is that Windows does not assign useful actions to these HID codes.
The next step is to install and configure usbrawmap.
A working configuration should include mappings for the special Sun keys. For example:
Open → Ctrl+O
Help → F1
Undo → Ctrl+Z
Cut → Ctrl+X
Copy → Ctrl+C
Paste → Ctrl+V
Find → Ctrl+F
You can customize the mappings further to suit your workflow.
A major obstacle on Windows 11 is Smart App Control and Windows reputation-based security features. Because usbrawmap is:

an uncommon utility,
unsigned,
rarely downloaded,
and interacts directly with USB input,

Windows may block it completely. This was the biggest obstacle during my troubleshooting process.
Once usbrawmap is working, I recommend launching it hidden in the background using a small VBS launcher and Task Scheduler. Create a scheduled task that starts at user logon and runs with highest privileges. This prevents a console window from appearing every time Windows starts.
One important lesson: be very careful when reconnecting the keyboard to a different USB port.
Windows may assign the keyboard to a different USB controller path. When that happens, USBPcap numbering may change and usbrawmap may stop working.
In my case, everything worked correctly, then I unplugged the keyboard and connected it to a different USB port. After that:

usbrawmap stopped responding,
USB-related tools behaved differently,
the USBPcap device number changed.

The solution was to identify the new USBPcap device number, update the usbrawmap configuration, and finally reboot Windows.
After that, everything worked again.
Final result:
All Sun Type 7 special keys now work correctly under Windows 11:
Help
Open
Props
Front
Stop
Again
Undo
Cut
Copy
Paste
Find
After more than ten years of occasionally trying to solve this problem, it turned out that the keyboard had been sending the correct HID codes all along.
Windows simply did not know what to do with them.
Hopefully this saves somebody else several hours of investigation.
Best regards,
A stubborn Sun Type 7 user, former Sun Solaris System Administration, and Oracle Database Administrator. 😄

Quote from: phinix on Wed, 29 July 2026, 07:58:43

tp is going to Canada?
or entirely diff continent?

Probably shanghai,  medium case shenzen, worst case yiwu.

work travel? for long?
Shanghai sounds interesting, no?

For those of you wanting to keep this a GMK set please make sure you fill out the IC form so we can track that data accordingly

tp is going to Canada?
or entirely diff continent?

Probably shanghai,  medium case shenzen, worst case yiwu.

tp is going to Canada?
or entirely diff continent?