Hey all, apparently one can submit the file to Microsoft for analysis to clear the flag. I just did that. Fingers crossed, hopefully Microsoft calms down with the COBALT STRIKE!
So I got this issue November 30th and didn’t have time to look into it. Finally had time today and I’m still getting the issue. This pops up when I go to use the shortcut that was created on the desktop. I’ve got a feeling that I’m not using the latest version. Should I just manually install the latest version?
Your antivirus probably deleted the app. Try downloading and installing it again, keep an eye out on your Windows Defender. If it flags and removes during installation, recover the file and install again if you have to.
I submitted a ticket to Microsoft to stop this madness.
Had this happen constantly until I went into Malwarebytes and excluded all the .exe’s in the folder.
Prob similar for whatever antivirus you’re using. First excluded only the folder, but that didn’t stop it. You may need to first reinstall from scratch, to ensure you can get all the files in the exclusions
Hey all, exciting news! I just got a response from Microsoft saying they will remove the alert for this app! Hoping that it slowly clears out from your Windows Defender malware definition caches with time.
I read something earlier about it potentially overwriting the UEFI battery limits, is that still an issue? I’m trying to figure out what the default was. I remember a while back when BIOS 3.06 came out it enabled some charge limit status functionality so that Windows smart charging could work. On Windows hovering over the battery icon would say “fully smart charged”, but after installing Framework Control it seems to just be going to 100%.
Is 80% the default charge limit in UEFI, or is that just what a lot of people have been setting it to?
There’s no default charge limit in the UEFI as far as I can remember. Whatever you set holds unless the app also has the charge limit function enabled in which case it will overwrite the limit. If you disable the app, BIOS limit will be respected.
As far as my usage goes, I have it set to 90% in the BIOS and 80% in the app and so far it’s been working pretty well. Even if I turn it off the 80% limit stays unless I disable it explicitly.
You’ll have to do your own testing and play around to be 100% sure it works for your flow. Disabling it will get it out of the way so you should be fine either way
The windows smart charge system just automatically enables a 80% charge limit after a time plugged into power. It gives no control on whether to turn it on or off and what limit you want set.
Honestly disabling windows smart charge and having your own controls like this is better. If you just set the bios or this app to charge to only 80%, you now have smart charge. When you don’t want it just turn it off. No random windows shenanigans suddenly deciding it’s on one day and you unplug thinking you have 100% only it’s 80%.
Or the opposite, you want to enforce a lower limit to save battery health and windows decides smart charge should turn off because you plug/unplugged one too many times…
Question for you. Before 4.3, when I opened the app, it was all in a single contained window. However now, it opens up a new window for the app, and when I try to pin THAT window to the desktop, it pins Microsoft Edge browser instead. Any idea why this is happening and how I can stop it?
Recently I came to the conclusion that 0.4.3 works. Though it works quirky.
UEFI controlled state to app controlled state change works as expected. No replunging necessary. There is a few seconds delay for app to update system state and few more seconds for Windows to show heart icon.
App controlled state to UEFI controlled state change does not work as expected, requiring reboot to show that heart icon and correct max charge state in the app. Simple replugging does not help, reboot required.
However, if the app is upgraded from 0.4.2 I previously thought there were some issues, but now I am not sure if they are related to what I described above.
But I didn’t want to dig them up so I disabled the charge limit in the app, then set it back to 100% in the UEFI, then uninstalled/reinstalled the app back. Long story short, I believe somehow I reset app settings, and it worked like I described above ever since.
Will be testing further. Sorry for providing very scattered information all the time, but testing this is kind of hard and slow process to do on main working machine. That is still Laptop 13 (AMD 7040) by the way.
One thing to note though. When I uninstalled the app it somehow uninstalled only partially and remained registered in All Apps section in Start menu, but not registered in Applications section in Settings. It was impossible to launch the GUI in this state (I have no clue about the backend).
Also the app icon looks blurry on my PC. Is it just a reused favicon?
I get the blurry icon as well, only when I pin the program to the taskbar, the icon is perfect. However, when I launch the program, a second, microsoft edge based window pops up with the blurry icon. Before, the program worked in itself, no second window, no blurry icon.
The app is wonderful, great job! Have you considered talking to the framework team about making it the official app, like other brands such as ASUS have?
Most complaints about Framework 16 were about the fans, TDP, or heat. This app has solved many of those problems. Others were fixed by the framework team.
However, MSRT just ran and nuked something from Framework Control (CobaltStrike detection again)….
from C:\Windows\debug\mrt.log:
Microsoft Windows Malicious Software Removal Tool v5.138, (build 5.138.25120.1002)
Started On Tue Dec 9 21:05:12 2025
Engine: 1.1.25100.9002
Signatures: 1.441.106.0
MpGear: 1.1.25100.9002
Run Mode: Scan Run From Windows Update
Quick Scan Results:
-------------------
Threat Detected: Trojan:Win64/CobaltStrike.U!MTB and Removed!
Action: Remove, Result: 0x00000000
process://pid:6980,ProcessStart:134096679385959321
SigSeq: 0x000026786FE824E4
Results Summary:
----------------
Found Trojan:Win64/CobaltStrike.U!MTB and Removed!
Successfully Submitted MAPS Report
Successfully Submitted Heartbeat Report
Microsoft Windows Malicious Software Removal Tool Finished On Tue Dec 9 21:17:39 2025
Return code: 6 (0x6)
Damnit.
Hopefully eventually the definition update also propagates to MSRT, not sure if any manual intervention is needed to get MSRT to stop removing it.
In the meantime, I’m disabling MSRT from running automatically by:
Open registry editor
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft
Right click Microsoft, select New > Key, name it MRT
Right click the MRT key, select New > DWORD (32-bit) Value
In the right hand pane, name the newly created value DontOfferThroughWUAU, set it to 1
Close the registry editor and restart PC
Once the issue is resolved, you can re-enable MSRTs monthly sanity check scan by just deleting the reg key.