rcmaehl

A released a new version of one of my programs recently and of course the 32-bit version is triggering all sorts of False Positives. I did some diving into result details and there ARE a couple things the interpreter or default functions seem to do that tag "Medium Risk" MITRE rules. "User-agent is suspicious or fake" (Fixable with HttpSetUserAgent set to something believable) "Collects information to fingerprint the system" (MachineGuid is read at some point) "Exhibits possible ransomware or wiper file modification behavior: overwrites_existing_files" (FileInstall or some other function sometimes overrides its own temp\aut####.tmp files) I haven't tested every single function so I'm sure there's more, but reviewing and minimizing what functions you use that cause Medium or higher MITRE detections will these help reduce false positives. HOWEVER, The BIGGEST issue of almost all the default (~20/~70) 32-bit compiled Virustotal false positives have are the fact that AutoIt can, by default: "electronically spy on the user’s activities (intercept keyboard input, take screenshots, capture a list of active applications, etc.)" (for some reason 64-bit compiled applications don't really have this issue) It would be nice if the compiler had the option of compiling in "automation mode" with all the bells and whistles, or a "application mode" that breaks automating + execute(), but this has been discussed over and over again as not happening.

It's no problem. I'm starting to fall behind with street lingo myself. Kids these days with their "sigmas" and "mewing" and such

Props for detecting VSC and allowing it as the default editor!

Odd. Here's what I'm getting. Tried with a few different accounts.

@seangriffin All the files linked in the OP appear to be restricted. Even if signed in.

You should be able to disable that specific one by going to Windows Settings> System> Projecting to this PC> Always off Or Opening Services.msc, finding Windows Media Player Network Sharing Service, Clicking Stop, then changing Startup Type to Manual or Disabled

Check powercfg /requests. Things that don't require user input, but prevent the computer from sleeping are listed there.

EDIT: These bugs are for the unmodified UDF (not the one with the proposed changes) Bug Report 1: If GUICtrlSetDefColor was called anywhere in the code before your RGUI functions the rounded corners get squared off. Bug Report 2: Having a Pic behind an _RGUI Control causes the Rounded Elements to not be drawn. #include <GDIPlus.au3> #include <WinAPITheme.au3> #include "RoundGUI.au3" ; #DESCRIPTION# ======================================== ; Title .........: Round GUI UDF - Example 1 ; AutoIt Version : 3.3.16.1 ; Description ...: Example of the Round Corner GUI UDF ; Goal ..........: Show creation of different controls ; Author ........: Nine ; Date ..........: 2025-03-28 ; ====================================================== Opt("MustDeclareVars", True) Example() Func Example() Local $hGUI = GUICreate("Example", 600, 500, -1, -1, $WS_POPUP, $WS_EX_LAYERED + $WS_EX_CONTROLPARENT) GUISetBkColor(0xC0FFEE) GUISetFont(11, 0, 0, "Comic Sans MS") _WinAPI_SetLayeredWindowAttributes($hGUI, 0xC0FFEE) _GDIPlus_Startup() ; Background that screws things up Local $hBackground = GUICtrlCreatePic("", 0, 0, 600, 500) Local $hBackgroundFile = _GDIPlus_ImageLoadFromFile(@ScriptDir & "\" & "test.png") Local $hBackgroundImage = _GDIPlus_BitmapCreateHBITMAPFromBitmap($hBackgroundFile) _WinAPI_DeleteObject(GUICtrlSendMsg($hBackground, $STM_SETIMAGE, $IMAGE_BITMAP, $hBackgroundImage)) _GDIPlus_Shutdown() _RGUI_RoundRect(0, 0, 600, 500, 0x202020, 0x202020, 20) _RGUI_RoundLabel("Example", 0xFFFFFF, 10, 10, 580, 30, 0xFFFFFF, -2, 15, True) GUICtrlSetFont(-1, 13) _RGUI_DrawLine(110, 40, 110, 480, 0x808080) Local $idClear = _RGUI_RoundButton("Clear", 0xB0B0B0, 10, 50, 80, 30, 0xFF00, 0X404040, 15) Local $idCopy = _RGUI_RoundButton("Copy", 0xB0B0B0, 10, 90, 80, 30, 0xFF00, 0X404040, 15) Local $idExit = _RGUI_RoundButton("Exit", 0xB0B0B0, 10, 450, 80, 30, 0xFF00, 0X404040, 15) Local $idInput = _RGUI_RoundInput("Enter something", 0xFFFFFF, 130, 60, 400, 30, 0xFF00, 0X404040, 15, 6) Local $idEdit = _RGUI_RoundEdit("Enter something here also", 0xFFFFFF, 130, 110, 400, 180, 0X404040, 0X404040, 15, 8, $ES_WANTRETURN + $WS_VSCROLL + $ES_AUTOVSCROLL) Local $idGroup = _RGUI_RoundGroup("Group", 0xB0B0B0, 130, 320, 180, 150, 0x808080, 0x202020, 15, 3) GUICtrlSetFont(-1, 10) Local $idOpt1 = GUICtrlCreateRadio("Option 1", 150, 350, 80, 20) _WinAPI_SetWindowTheme(GUICtrlGetHandle($idOpt1), "0", "0") GUICtrlSetBkColor(-1, 0x202020) GUICtrlSetColor(-1, 0xB0B0B0) Local $idOpt2 = GUICtrlCreateRadio("Option 2", 150, 390, 80, 20) _WinAPI_SetWindowTheme(GUICtrlGetHandle($idOpt2), "0", "0") GUICtrlSetBkColor(-1, 0x202020) GUICtrlSetColor(-1, 0xB0B0B0) GUICtrlCreateGroup("", -99, -99) _RGUI_RoundLabel("Auto-Size", 0xB0B0B0, 350, 320, -1, -1, 0x404040, 0X404040, 15) GUISetState() Local $idCtrl While True Switch GUIGetMsg() Case $GUI_EVENT_CLOSE, $idExit ExitLoop Case $GUI_EVENT_PRIMARYDOWN $idCtrl = _RGUI_ButtonPress($idClear, $idCopy, 0xFF00) Case $GUI_EVENT_PRIMARYUP _RGUI_ButtonReset($idCtrl, 0xB0B0B0) Case $idInput ConsoleWrite("Input" & @CRLF) Case $idEdit ConsoleWrite("Edit" & @CRLF) Case $idClear GUICtrlSetData($idInput, "") Case $idCopy ClipPut(GUICtrlRead($idEdit)) EndSwitch WEnd EndFunc ;==>Example Test.png:

For the functions to be more user-friendly and similar to the default functions... Can the Color parameters possibly be replaced with a parameter that's a handle to the parent GUI, where you can get DefBkColor (_WinAPI_GetBkColor) and DefColor (_WinAPI_SetTextColor return value) from there? (and optionally add _RGUI_SetColor / _RGUI_SetBKColor) Edit: I've attached a modified UDF mostly working with the proposed changes implemented... but the background keeps drawing as transparent for some reason. RoundGUI.au3 RoundGUI Example1.au3

Try adding -mx=0 in your CI for 7z

I wonder if @guinness remembers a similar program from their pre-MVPdeveloper PortableFreeware days. Granted that was... nearly 16 years ago. Edit: Oh yeah, they're a dev now

I mean GitHub says to have to run on startup with starts it auto-locked

What if I forget my password?

I'm sure there's some CPU Branch Predictor Optimizations that can be done. However, as you've seen in your Process Name from Handle thread, there's a LOT more performance that can be gained by reusing resources, cutting out unneeded code, and other optimizations. Also, don't be afraid to do things out of order. You may be surprised what still works $iSIHost = ProcessExists("sihost.exe") While True $aProcessList = _WinAPI_EnumChildProcess($iSIHost) If @error Then ContinueLoop ProcessClose($aProcessList[1][0]) $sCommandline = _WinAPI_GetProcessCommandLine($aProcessList[1][0]) $sProcessPath = _WinAPI_GetProcessFileName($aProcessList[1][0]) WEnd And you can always fix a mistake if you're overzealous $iSIHost = ProcessExists("sihost.exe") While True $aProcessList = _WinAPI_EnumChildProcess($iSIHost) If @error Then ContinueLoop ProcessClose($aProcessList[1][0]) $sCommandline = _WinAPI_GetProcessCommandLine($aProcessList[1][0]) $sProcessPath = _WinAPI_GetProcessFileName($aProcessList[1][0]) If Not $aProcessList[1][1] = "msedge.exe" Then ShellExecute($sProcessPath, $sCommandLine) WEnd

I decided to investigate by inverting the conditions via NOT (and inverting variable values and assignments) with the following results. If-OneLiner False becomes the slowest of the bunch. Edit: Fixed variables. Got similar results as previous. name time -------------------------------------- IfNot-EndIf True: 0.000334 ms IfNot-EndIf False: 0.000226 ms IfNot-OneLiner True: 0.000539 ms IfNot-OneLiner False: 0.000156 ms