OPEN and CLOSE HWINFO

[balala]

Yes. It is a program that must be run "As Administrator", and thus can only be killed "As Administrator".

Oh, sorry in this case. I'm going to edit my post striking my reply.
Sorry if I did create an inconvenience with my reply.

[jsmorley]

Oh, sorry in this case. I'm going to edit my post striking my reply.
Sorry if I did create an inconvenience with my reply.

Your approach is fine, if you simply replace the call to taskkill.exe in the RunCommand measure to a call to KillHWiNFO.exe instead.

[balala]

Your approach is fine, if you simply replace the call to taskkill.exe in the RunCommand measure to a call to KillHWiNFO.exe instead.

Probably. Can't say, since as said I'm not using HWiNFO, so don't know KillHWiNFO.exe.

[Yincognito]

Yes. It is a program that must be run "As Administrator", and thus can only be killed "As Administrator".

taskkill.exe is not a Windows application, and has no ability to ask for administrator privileges itself. Whatever command environment it is run in must be run "As Administrator" or have the ability to request an escalation from Windows. The RunCommand plugin does not have this ability, and so any call to taskkill.exe that tries to kill a "protected" application will simply fail.

The AutoIt program I wrote does have the ability to request escalation from Windows, and although this will cause a UAC prompt requesting confirmation from you, it will work.

There could have been another way of doing this ... if HWiNFO had a parameter that you can execute with, so that it closes itself. Say, HWiNFO.exe -close or something like that. But apparently, according to their forums, such functionality might be only available in HWiNFO SDK, and the limited functionality of their hotkeys doesn't help in this case either (in order to be taken advantage of using Rainmeter's own Hotkey plugin)...

[PHILleHUt]

welll don't worry.....

It's coool for U to help me

[balala]

There could have been another way of doing this ... if HWiNFO had a parameter that you can execute with, so that it closes itself.

Yes, but it's not needed in my opinion, since KillHWiNFO.exe does exist (as jsmorley said - and if he said, I suppose he is right). It can be used, don't overcomplicate things...

[Yincognito]

Yes, but it's not needed in my opinion, since KillHWiNFO.exe does exist (as jsmorley said - and if he said, I suppose he is right). It can be used, don't overcomplicate things...

Okeydokey then, no overcomplication. Keeping it simple: kill the hardware, kill the info.

[jsmorley]

Okeydokey then, no overcomplication. Keeping it simple: kill the hardware, kill the info.

I can confidently say that KillHWiNFO.exe exists, since I wrote it...

[Yincognito]

I can confidently say that KillHWiNFO.exe exists, since I wrote it...

I know - I was just joking around with killing the hardware and its info...
I don't want to suffocate any computer, so everything is cool.

[balala]

I can confidently say that KillHWiNFO.exe exists, since I wrote it...

Oh, congratulations in this case. Didn't know, but as said, I'm not knowing HWiNFO, so no wonder...
And additionally a huge thanks for all the work you do for all of us.