Ahh yes, the logs are revealing. Than you for providing the screenshot for the supported devices.
@rei0083 I would create an issue in the framework-system repo and ask for a timeline on supporting laptop 13.
That’s what I did for the laptop 16 back in Jun 2025 and @Daniel_Schaefer responded 
Seems like you have two instances running somehow 
. I’m assuming you’ve already tried uninstalling and restarting the laptop and re-installing right?
Try going to your “services”, you can search for it in the start menu. In there look for framework control service and see if you have two for whatever reason.
You may have to hunt for the second one in the apps in the settings and uninstall fully → restart → check services again
Thanks for responding 
Yes, I’ve already tried the uninstall - reboot - reinstall and uninstall - reboot - remove all folders that are left - reboot - reinstall.
In services I can only see one instance running though.
I’ll uninstall and mess around for a bit, and see if that resolves something.
Edit: reinstalled again, tried restarting the framework service etc.
The website one works without issues? That’s pretty weird…
Do you have any logs? You can check logs in the settings menu now.
There is definitely ‘something’ in there. Seems like RyzenADJ doesn’t want to load on the local version?
Hmm this very weird. I wonder if there’s anyone else having this issue. Seems quite odd for the web version to work and the local version to fail…
I have noticed that the latest release (installed from aur non bin version) reports on the web as the 5 beta 2, instead of 5.1. Looking at release’s source files in github, the web package.json is indeed still on the older version, while the rest of the application is 5.1. Am I missing something?
That non-bin aur release is something I put together super quickly, I need to build CI for it and do some proper testing. Consider it as “alpha” for now
Easily this software has made the most difference to my temps and max frequecy during gaming on my 7840u. Thank you so much. It was averaging 3.9GHz on BF6 to now 4.3GHz at the same temps. amazing work!
I’m glad it worked out for you. Happy fan curving!
Concidering that the LED module control is on the roadmap, it would be nice if it had the logic for autoswitching on/off depending if the laptop is on AC/battery (or powerprofile). The matrixes are very nice, but I haven’t used them after the first week of having the laptop due to them eating too much power.
It would be doubly nice, if that also was exposed as maybe systemd service target so a user could tie his own scripts to. I have tried to implement that myself, but (maybe not only) because I made them user services I ran into a problem of them not triggering on boot.
Thank you for keeping the development running.
I’ve been using the app for a while to monitor thermals and such, and I really like it. One question for @Kemal_Ozturk : in the future, do you plan to change the power management helper on Windows so that it doesn’t use the WinRing0 driver? Every so often, Windows Defender flags and quarantines it due to WinRing0, even though I set Defender to allow it, and that’s a bit annoying. Apart from that, the app is really good, and I’m glad it exists.
His app is using ryzenadj to change settings and that app is using winring0.
You can achieve power management on windows with Universal x86 Tuning Utility
It uses pawio which is signed alternative to winring0
Ok, hear me out.
I have both the Laptop 13 (AMD Ryzen 7040 Series) and the Laptop 16 (AMD Ryzen 7040 Series).
I absolutely hate that the Laptop 13 is spelled incorrectly without the space between “7040” and “Series”. Screenshots below (click to reveal).
So I thought, “Let’s make that one-liner GitHub pull request and not bother anyone.”
But I could not find that line anywhere in the Framework Control repository, so I asked Copilot. And down the rabbit hole I fell.
What I found out is that Framework Control uses framework-system to parse that line from UEFI/BIOS, meaning this is a UEFI/BIOS problem, which could be addressed only by a new UEFI/BIOS version release.
But it gets more interesting.
The existence of both lines 206 and 207 in smbios.rs indicates that the problem was fixed in one of the UEFI/BIOS releases. However, I have the latest UEFI/BIOS version and still observe that eye-watering spelling mistake. And the Windows System Information app shows the model name with that spelling mistake too, which only proves that this is what SMBIOS tells the operating system. Screenshots below (click to reveal).
As far as I am concerned, I should report this to the latest Laptop 13 (AMD Ryzen 7040 Series) BIOS version thread. Is that correct?
And before you laugh (or cry) after reading about this “extremely important” matter, think of it as something that could potentially help find some other bugs that may somehow be related. At least that’s what I tell myself after spending a few hours of my life on that…
TL;DR
Please point me to the people I could bother to get that spelling from the screenshots fixed. Thanks.
Hahah, that made me laugh for sure. I love your dedication.
The answer you’re looking for may be in the framework system repo. This app uses the framework_tool as you mentioned, and who knows how that tool is reading the BIOS values. Wherever the discrepancy is, it’s probably fitting to create an issue in the framework-system repo with this same information and see if they’re willing to entertain/fix this issue.
Like @wojciech_migas mentioned, this app uses the 3rd party RyzenAdj and at the time of implementation I couldn’t find an alternative to it. If an alternative arrives in the future, I can definitely move over to it. I don’t enjoy getting flagged from AV all the time.
One thing you can try is to add the install location as a folder exception in your Windows Defender. That will be more persistent compared to “allow”ing it once it gets deleted.
The x86 Tuning Utility is nice but it didn’t feel polished enough for me to use so I opted to add my own power management using RyzenAdj.
I wonder what the “pawio” thing is, maybe we can use that here too 
Yeah, sometimes I get very passionate about not very important aesthetic stuff… 
That’s what I thought, but I wasn’t brave enough to create an issue, as some devs get very angry when you post unrelated issues, so I started a discussion instead.
I have a feature request/fix for your amazing Framework Control software. I upgraded to the 5070 last night and notice an abnormally high idle power draw and have concluded it’s from the background service not letting the 5070 sleep/park. Do you think it’d be possible to have a feature to stop monitoring the dGPU sensors to let the dGPU park. The idle power draw with the background service stopped is around 19-21W and with the service running the idle power draw is 30-38W on the battery.
Same here, I stopped using the program because of this issue.
I also noticed this issue. If I disable/uninstall, my power draw drops by half.
I’m not sure if it’s directly tied to the 5070 however. I disabled the 5070 in device manager, and unchecked all use of dGPU sensors as far as I can tell, but I still draw around -25 to -30W
