I had a great 18 months with my Framework 16 running Fedora Linux, but circumstances have required me to move to Windows for a while. Specifically, changes to the Kernel in Fedora over time made some software I needed unusable (I needed to stay on an LTS kernel). I’m currently running Windows 11 on my 16 and hope to return to Linux soon. I have the FRANMZCP09 (A9) board.
During my search for a solution, I wanted to avoid some privacy concerns I have with Windows 11 by installing Windows Server 2022 or 2025. 2025 ended up working better for me, but some hardware couldn’t be made to function even by seeking out component manufacturer sourced drivers. I seem to recall I had the most difficulty with the touchpad and TPM.
I found that the touchpad driver would most likely have worked on Server 2025 if its INI INF were to be lightly modified for applicability and then re-signed. I wonder if this would also hold true where the TPM is concerned?
All of this brings me to these questions:
What components used in Framework products will include drivers that work on Windows Server OS?
Will the Framework desktop support Windows Server drivers?
If my Framework product reaches EOL and I want to re-use components (think about the FRANMZCP09 in a blade-style case or something), how far does driver support reach for that?
Previously, it was stated that Framework 16 (AMD 7040) only officially supports Windows 11 22H2+ (obviously on the Windows-side; not including any Linux). This means it also doesn’t support Windows 10 (which, at launch, still had over a year of life left before EOL). Therefore, only drivers for Windows 11 were provided, and support for any other Windows version is solely supported by the user. If Windows 11 drivers worked (as many did for Windows 10 users), great! If they didn’t, it’s not Framework’s problem.
I can’t find a touchpad driver in the driver bundle here. On my Windows 11 touchpad says it uses Microsoft drivers and doesn’t require any installation.
Am I missing something?
Also, the .INF files don’t require any signatures as they are just text configuration files, I think. Only the driver code (.SYS and .DLL) does, so you can modify .INF freely and the system will install the signed SYS/DLL stuff for your device. At least that’s how I think it works, sorry if I’m mistaken.
Yeah, unfortunately changing the INF requires regenerating the catalog for the driver and therefore a new signature. Back in Windows 8 days, I could edit and load a driver even in kernel mode without having to worry about it as long as I was ok with lower system security. Not these days though.
Related reading: