This is a minor bugfix release for bugs discovered after the general availability of RD Tabs 3.0.

DOWNLOAD NOW:
https://www.avianwaves.com/Software/Tools/RDTabs/RDTabsSetup_3.0.10.exe 

Changelog:

3.0.10

---

- Fixed bug: an arithmetic overflow was possible under certain conditions when closing a tab.
- Fixed bug: various DPI display issues when running in native high DPI mode on a system with a high DPI display.

Symantec Endpoint protection is deleting the 3.0.10 update file identifying it as WS.Reputation.1 risk. Haven't had any issues with RDTabs updates before.

"Because this detection is based on a reputation score, it does not represent a specific class of threat like adware or spyware, but instead applies to all threat categories." Well, based on that, I guess until RD Tabs gets more popular, this may be a problem. There was a similar issue with Microsoft's SmartScreen filter when the first alpha copies of RD Tabs 3.0 were being distributed to my private tester group. Though, it wouldn't delete it, it popped up the big bad warning. When I started signing the installer binaries, that allowed the SmartScreen to "learn" the installers were safe. Basically what was happening is that every time my app or installer ran with that signature it aggregated data that showed nothing malicious happens, and then eventually Microsoft white lists the signature. I'm guessing something similar needs to happen for Symantec. Thanks for pointing it out. I'll see if they have any way to fast track the process.

Annoyance with that issue seems fairly common: https://www.ghacks.net/2...-ws-reputation-1-system/ 

I submitted it for review. Who knows how long that will take... 😕

Well, that happened a lot quicker than I expected.

Upon further analysis and investigation we have verified your submission and, as such, the detection(s) for the following file(s) will be removed from our products:

File name: RDTabsSetup_3.0.10.exe
MD5: BDE89496BF8A356E308346BDCA278EFD
SHA256: C3658FE460886175037B82EFF092A292113E5A8E9E9FB9BDF623C97DE940E173
Note: Whitelisting may take up to 24 hours to take effect via Live Update

Thanks for looking into it. I usually just go ask my InfoSec team to whitelist any tool that I have been using for years that all of sudden throws some error with their "protection" tools but thought I would mention it.

Edit: It is working fine now, thanks again.