LeeAdama

My version of Defender, using the current definitions from a few hours ago (Virus Definitions Version 1.261.1406.0) it shows clean still. I noticed that Windows Defender will keep telling you about the previous detection until you press the button "Apply Actions" and the "Threats Found" goes back to Zero (0). This might delete or quarantine the launcher but you can put it back and future scans should show clean (if your using the updated Definitions). Also, now the image on the launcher should change to match whatever version of WoW you drop it into. Classic, TBC, WOLK, or CATA. That's how you know it detected the correct version. It will recognize but refuse to launch with anything newer than Cataclysm (4.3.4). As seen Here With CATA:

I need people to test it!!! Especially on WOLK. I don't play on any WOLK servers.

A Few Pretty Big Updates in 0.9.6. You can now remove servers by pressing on the minus "-" under the server list. If you upgrade the Launcher or Move it your saved passwords fail as before, but now you'll be prompted to enter it in in again. This was for security reasons. To protect the stored Encrypted passwords. The Launcher Now is aware of which version of wow it's being used with. It will make automatic adjustments to account for this The Logo on the main screen now shows one of the following: Classic, TBC, WOLK, or CATA depending on which version is detected. The Launcher now works With all of the following: WoW Classic (1.X) WoW TBC(2.X), WOLK (3.X) and CATA (4.X) I Changed the name to WoW Custom Launcher, because it isn't just Classic WoW anymore. The Launcher will auto detect what region client it's running on. Only enUS, and enGB are supported for now. The launcher will remember it's position on your screen when you close it and it will startup in the same place. Code Cleanup and significant Refactoring. Updated Download Links and info in the Original Post. NOTE: I believe that you will still need a modified WoW.EXE in WOLK and CATA. Google it. I downloaded my client from TwinStar and just use My Custom Launcher to connect to whomever I want to. You can download the 4.3.4 Client here : http://www.twinstar.cz/how-to-connect/?lang=en#cata orf https://mega.nz/#!lPp1GCSR!1J38jZxPNV3UuzMHPM8FcSnpxUvPxM-Kc5XoomMHzc0 You'll still need to download the launcher from the OP of this thread.

I am planning to add these in the next version. Glad you can use it with no issues now!

Thanks, I was pleasantly surprised how quickly Microsoft answered me. They could have easily dragged it out. They don't make life easy for small developers but at least they responded quickly.

Microsoft has already answered me. The important part is that after you update Windows Defender Definitions to version 1.261.1049.0 or higher my launcher will no longer be detected as malware. You can see the entire report embedded below or by clicking here : https://1drv.ms/i/s!AkFJKno2myAmhfwNSE0dJ4PH5_3ikg

I would point out that Trojan:Win32/Fuerboos has been FALSELY detected a bunch of times by windows defender in the past. From such software as VIM, Kodi and Diablo 2 https://us.battle.net/forums/en/bnet/topic/20760958104 https://github.com/vim/vim-win32-installer/issues/36 https://forum.kodi.tv/showthread.php?tid=325992

I have reported this as a FALSE-POSITIVE to Microsoft. The latest version of the windows defender definitions do detect (falsely) a Trojan in my launcher. Previous scans came up as clean. I will advise what Microsoft says when they get back to me. I would remind everyone of the Virus Total scan results which I re-analyzed today. 67 different virus scanners detected my launcher as clean. Check the SHA-256 and you'll see they match. https://www.virustotal.com/#/file/28bc6d6a0e95fe15aa2469d2e89b575e26dafa92b9c9be28f2a120561168047b/detection I wasn't going to release the source code yet because it's not finished and frankly I'm a little embarrassed. This is the first program I have ever written in .NET. But I guess I don't have a choice given the fact that I've now been falsely accused of spreading malware. If you want you can download the sourcecode here : https://1drv.ms/u/s!AkFJKno2myAmhfsXySA_7eGwT09O0Q You'll need Visual Studio 2017 (the free community version) to open it. You can download it here : https://www.visualstudio.com/downloads/

Now I remember why I stopped developing software for windows in the first place..../sigh If this is going to be a problem than I'll pull the whole thing down and just keep it for myself. I really don't give a shit. I was just trying to do something nice.

Since getting the certificate necessary to bypass this warning costs more than $300 per year I won't be doing it. If the message bothers you then don't use the launcher. https://www.digicert.com/code-signing/ev-code-signing/

Interestingly enough, it will ONLY give you this message if you download the app from the internet. Since I developed the launcher on this computer I didn't download it from anywhere. So, I had never seen this message before.

If you're talking about "SmartScreen" that message is displayed with the newest version of Windows 10 when you first try and open ANY application that isn't digitally signed. Since I'm not a professional developer my apps aren't digitally signed. But you can safely disregard this message and click "run anyway". It will only come up once. You can plainly see it's only because it did not recognize the app. If you actually run a virus scan of the downloaded file it will show 0 threats found. Exactly as the VirusTotal results that I linked in the OP.

Buddy, I use windows 10 with Windows Defender and it has no problem at all with my launcher. The source code has been examined by a staff member of this server. Could you be a little more specific about what exactly your error is ? Lee

Thanks, I mostly made it for myself, but since it worked so well for me I thought I'd share it. The most useful feature to me is the way it handles passwords. With hackers these days you have to have a really good password since that's your only line of defense. I can save the password on the website with a password manager but getting it into the wow client is much more convenient with the launcher.

Update: I tested it and it does in fact work fine with 2.4.3 The Burning Crusade. Obviously you have to have a separate WoW install of that version to put it into. And you need one shortcut for each version of WoW, the server lists are separate. I don't know when they changed things, it might be with 3.0 and higher, I'm not sure.