argumentum

No problem. I like doing that too, but here is seen as necro-posting Your first post, and not even a question, but some code. You're good in my book ( just don't do it again )

We need some of those markers like phones have. Those dot,dot,dot ( ... ) so we get to know that someone is typing

Since @Ace08 is unlikely to thank you for the code and welcome you to the forum, I'll do it. There are some forum rules, like all forums do. One is that all communications are in English. Welcome to the forum

Provider=Advantage OLE DB Provider That above is the "other" I use. MySQL for my "AutoIt as a CGI"** , and the beloved SQLite. ** in apache/php. I either code an AutoIt page generator, or a JSON string "returner", or anything that would avoid me coding perl or php. And use a MySQL UDF from somewhere that is in code I haven't touch in years, and would take for me to go to the client(s) PC(s) to look at to tell you exactly the one. Note to self: get organized !, you 😅

powershell "Get-PhysicalDisk | Select-Object FriendlyName, DeviceID, AdapterSerialNumber" That will give you the info you would need to ask for RMA on the drive and I believe that is the info he is looking for.

...but "8CE3_8E10_02B1_5166" is not the serial number of the NVMe drive. Running "Get-PhysicalDisk | Select-Object FriendlyName, DeviceID, SerialNumber, AdapterSerialNumber", the "AdapterSerialNumber" is the string that is needed. For that I believe that "https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddstor/ne-ntddstor-_storage_protocol_nvme_data_type" needs to be used.

..there should be. But am not a "programmer", just a "scripter", and the knowledge to turn parts of Ntddstor.h into AutoIt, is beyond me

...to be or not to be... ...to theme or not to theme.., that is a good question. I believe that in your project, theme-ing each control will not be possible. Don't worry about themes but do use proper windows coloring if you need to color something: #include <GUIConstantsEx.au3> #include <StaticConstants.au3> #include <WindowsConstants.au3> #include <WinAPISysWin.au3> #Region ### START Koda GUI section ### Form= $Form1 = GUICreate("Form1", 400, 100) GUICtrlCreateLabel("Label just as is, will be seen", 10, 10, 380, 17, -1, $WS_EX_STATICEDGE) GUICtrlCreateLabel("Label with COLOR_HIGHLIGHT will be seen as it should", 10, 40, 380, 17, -1, $WS_EX_STATICEDGE) GUICtrlSetColor(-1, _WinAPI_SwitchColor(_WinAPI_GetSysColor($COLOR_HIGHLIGHT))) GUISetState(@SW_SHOW) #EndRegion ### END Koda GUI section ### While 1 Switch GUIGetMsg() Case $GUI_EVENT_CLOSE GUIDelete() Exit EndSwitch WEnd Therefore, if we respect default coloring, everything should be visible by default. Then give users the ability to use custom colors. But by default, default theme colors should be sufficient.

Yes, eventually shows the items. Not after. No. The reason for forking the process that gives the data to the treeview, is to avoid unresponsiveness of the GUI. But you'll have to look into it. It is quite responsive if the system returns the data fast.

I think that the GUI and the searching should be separated/forked. When listing something slow, like a network share with lots of folders/subfolders, the GUI is "not responsive". Other than that, nice looking.

I'd like to say is my awesomeness but is just the theme I use. Makes everything dark mode. Here is a sample of 2 of them : BIB3 Buuf Regular And that is the way it should be. You choose a theme and that's the theme for the OS, but M$ don't do it and I search the net for ways to get it done.

smartctl.exe will give you what you need and more ( like health status of the NVMe ) "The smartmontools package contains two utility programs (smartctl and smartd) to control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA/SATA, SCSI/SAS and NVMe disks. In many cases, these utilities will provide advanced warning of disk degradation and failure." ( https://github.com/smartmontools/smartmontools )

That sounds more like a non-apology than one. And I'll take offence on his behalf because he did answer your post with good advise ( even if not what you expected ). The best you can do is to ... do what I asked before. Maybe is a problem in AutoIt, maybe is a problem with the your script code. We would welcome a detailed account of, piece by piece of your code, to pin point the exact issue. Do remember that we dedicate time and answer, out of the goodness of our hearts, and nothing else

..like @Nine said, try to zoom into the aspect of the code with the problem. If you want us to look at something, provide simple running code, to run and debug. And keep in mind that we don't have anything to look into MT5 stuff.

They look good.