TheDcoder

Windows Defender does not have a reliable detection consistency, each user has different experience with files. I guess it depends on the heuristics and origin of the files. I have also found that not using UPX greatly reduces false positives... I had 46 detections when using UPX, went down to 2 without UPX .

@KaFu I just scanned the downloadable ZIP from your website at virustotal: https://www.virustotal.com/#/file/c4712de727cc59974e6afd9f53e285c37d68c8158271261a159b4bc1db681ef3/detection It shows false positives

Well, Visual Studio is very large, 7 GB last time I checked. Also doesn't it download the C# compilers and tools? My laptop cannot handle that beast of an IDE anyway, keeps freezing and eats all of the resources.

C# is a big beast packed with tons of wrappers and libraries for almost everything. Not really a simple one to work with...

There is a good chance that they lost the source code... or some have been saying that.

Also there have been a lot of long topics on the same topic over the months, TL;DR version of all of them is, what feature/issue are you missing/having?

Are you supplying your user account's API key to the UDF?

@badcoder123 Nice! Should be more universal than my solution

@Chimp

Don't know if it works in other versions of Windows but I tested it in Windows 8.1: ShellExecute(@UserProfileDir & '\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\System Tools\Run')

Ah, yes. I just noticed. Maybe try this one?: https://github.com/loganch/AutoIt-VSCode

@argumentum

@badcoder123 I suggest using $VK_CAPITAL: #Include <WinAPI.au3> #include <WinAPIvkeysConstants.au3> $_Status = _WinAPI_GetAsyncKeyState($VK_CAPITAL) ConsoleWrite($_Status)

Oops, grabbed the wrong thing

Good work, a great program, I might use it but I am not really into games, GoG is awesome though, got many freebies overtime .

Well, that looks suspicious. No idea why Explorer dies, I recommend you to investigate the problem further with tools like Process Monitor... or wait for @junkew's comments.

The error is not what I expected, was expecting a COM error. Anyway looks like one of the Arrays is not formatted properly, @junkew might be able to help furthur

Try running the script uncompiled and take a screenshot of the error, the screenshot of the compiled script doesn't help very much.

@Earthshine UIAutomation should be available by default from Windows Vista and Server 2008 and you can get it on XP and Server 2003 by installing .NET Framework 3.0. So I doubt your server lacks something important, is it a hard crash (i.e Windows shows a "This program has crashed" dialog) or an error thrown by AutoIt?

I doubt it is possible in pure AutoIt, because of the stack overflow error. The interpreter will at some point stop recursive function calls to prevent stack overflow . A reliable way of doing this would be to use Windows API (Win32, WMI etc.)

For UIAutomation: Inspect from Windows Development Kit and Simple Spy supplied in @junkew's wrapper.

@Earthshine UIAutomation might be a more universal alternative for automating GUIs:

More than a year later I am no where better than I was at Post #1, lol . Still struggling to navigate through Microsoft's documentation for WMI COM API, I might try Script-o-matic, at the moment I cannot recall what I was looking to do with WMI.

Not related to your question, but I would personally prefer making my script accept custom parameters like /copy "source" "destination" instead of using /AutoIt3ExecuteLine

It shouldn't eat memory, it would reuse a limited amount.