Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jpm

Pages: 1 2 [3] 4 5 ... 8
If you read the thread, it's the Admins who have been doing the work to get this fixed and the repair program has been proven to be safe.

Tell me - what has this got to do with what is has been reported from those who use the repair program -

Given this really weird time in cyberspace, I have gotten way more careful.  For example, the strong evidence now that the virus checker Kaspersky has been spying in our country's computers, got a 60 minutes sessions about the associated risks, and the US govt has banned it and required that every government agency that installed it must prove they removed it from their computers.   Or how about Facebook - not only is it clearly established that most of the communications on Facebook were fake bot software, but one of the board members at Facebook openly worked with Cambridge Analytica to find ways to help Trump get elected.

No one has mentioned the suspicion about Kaspersky and has no bearing on MS antivirus programs blocking the program - Facebook doesn't come into and neither does data collection or Trump getting elected.

Now do you see why I was questioning this ?

When Norton Security kicked out the .exe on mine, I knew it was a false positive and had no qualms about white listing the website to reinstall the program.

You are correct. the internet is not safe. Not at all. Nothing is sacred and your need to be aware of everything. You need to choose what you install very carefully.

You are also correct that this issue is not your problem and something we need to solve with Microsoft.

Our problem is that it is 100% a problem with Microsoft and we are trying to relay the information.

You can choose to whitelist it or not - but it should be cleared in all their definitions soon. I know they are working on it.

Well, the problem is THEY are Microsoft and we are a couple of guys. So in you analogy - we are the poop. :)

The antivirus world is like this though. You guys are just seeing this one right now. But it is very common for all the smaller authors. Don;t get me started on the whole PUP bullsh*t going on out there now.

I did hear back from tech support who confirmed there is no detection.

They recommended this:

Please try the following steps to clear cached detections and obtain the latest malware definitions.

1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender 

2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”

can someone try it and let me kknow.

Right.. Now you see the dilemma.

I suppose Guinness or a class a rant is in order. 

I filed a dispute with them just now. It felt funny filing a dispute on a clean file but... we live in funny times. ;)


This is becoming an issue for a number of people.
There are a lot more.

All the authors are getting the same issue. The file comes up clean in the submission system, but is dectect on the home user. It effects both VB and Unity game programing languages.  It sems that it is a heuristic issue with defender but it looks like they are having an issue dealing with it.

Maybe if some of you all submitt the false postive as users?

Yeah - I wrote them separately on essentials.  Seems that one takes longer

I JUST updated to the latest 1.263.1584.0 def from Microsoft  and it is showing as clean. Finally!

Our best guess -- and it is just a guess but a guess from experience - is that there was something wrong with the defs over the weekend and they fixed it. Then it looks like they rolled it back - then fixed it again. Probabaly having to fix the fix. But, now it looks fixed. ;)

Problem is not everyone updates at the same time and it can take a few days to roll out.

This is strange because the submission system says it is clean.... and it is.

Clearly they are having some sort of definition issue. I will try and get some clarity.

I literally just got another notification from them saying it was cleared. I reported it on Essentials as well.  Maybe their essential definitions run behind or they missed it the first time. But it should clear up soon.

Just wrote in to let them know that defender is OK but essentials is still a problem.  We will see if that helps. They tend to be pretty quick/

Dang. It is indeed cleared by MS but via virus total and their own site ( see attached)

Defender and essential use the same definitions.  I'll write and see what they think. Could be your didn't update?

Yeah - we contacted them about 3 seconds after we found out. I believe it took them 6 hours to responded that it was fixed. There was never anything to do with anything on a user end. It was their mistake on matching.

No they never told us why, but it wasn't just our program it was a number of them around the web.

I would love it if they told us why - but it was most likely a coding error on their end and if they admitted it they would open up to legal issues.  Especially since what I have been able to divine is the programs that were flagged all used api calls to VB -- which is Microsoft's programming language. So essentially Defender flagged VB.  So whoever or however they made the error - it will never come out of Redmond. :)

Each time we release the exe is recompiled. So the 4.0.14 would have a completely different hash and "look" than 4.0.15.  When we release 4.0.16 odds are something will flag it as a false positive after release. It may not be defender, but it will be something. This shit happens all the time with every one of the antivirus apps - it is the bain of the software authors existence. It's annoying but part of how the security industry works.

I believe if you run the .exe  with  /silent  it will do what you want.
The sinlge click idea we started introducing in 4.0 but would love input on that. In fact. if you would write me are support @ tweaking . com I;d love to pick your brain and hear some of your suggestion as we are working on the UI as we speak.

OK all you tweaking virus experts, I think I'm back in the right place now. I hit the wrong button last time and double posted. Sorry !

We can all carry on about all the virus protection programs giving out false positives, but I'd like Shane or jpm to ponder this :

Why does v4.0.15 get flagged for the Critet virus but v4.0.14 DOES NOT  ??  Something ain't right

And to Boggin, Major Geeks should have v4.0.14. It works just fine.


We do not know exactly why. It could be something as simple as pattern matching. I remember a friend had his credit card number detected as a virus because part of the numbers matched the hash on a known virus - true story. Heck Malwarebytes detected my personal photography as a virus a couple months back. Explain that one.

In this case a LOT of files were detected from a LOT of companies. All we know is that they all use VB -- so it had something to do with that.  But exactly what, no idea.  Our product is 100% clean. They were wrong and they aren;t about to tell us why they were wrong for all the reasons you would suspect. It certianly isn't something we can prepare for either. Someone at MS made a mistake. They fixed it. But that is exactly how the antivirus world works.  Happens ALL the time.

It is better to have an AV than nothing - but really it is a lot of security theater.

People have - because of good marketing - the belief that antivirus companies keep them safe and are perfect.  I have 20 years in the software business that says that they are mainly full of crap. :)

Antivirus apps are more and more becoming modern day scareware and less and less a protection software.

But to restate what I said, false postives with ALL antivirus apps are commonplace.  When it happens, it is incumbant on the author of the software to notify the AV company detecting them to fix it.

In this case, from reading about other software the was hit with the "Critet.BS " designation (Seems BS stands for BullShit) - it looks like Windows Defender was tagging  that used certian funtions in programing language.  For those who don;t know, is a micorosft programming language.

How do you hold responsible for that?

I think you misunderstand how the entire antivirus thing works. Microsoft, Malwarebytes, Avira - all of them have false positive. Hell. Malwarebytes detected some of my photos the other day as virus (which BTW isn't even possible). They do it as a matter of course.

The dirty secret is some company's - the big ones  - are white listed. They can do whatever they like and release whatever they like. That is dangerous. Small companies are not - we use something called code signing which validates our product - but sometimes that is plain ignored, missed and we get  "false positive" detections

The antivirus companies further more depend on from known lists - most of which are t the same. Meaning they all the detect the same known thing. Hence., they realty detect something that isn't known -- until someone discovers it and it comes on the list.

To try and get around this they use heuristics  that try and uses that something may be in the realm of a viral infection -- that leads to more false positives.  Don't believe me, read it from one of the best utility programmers ever.  This is why you see "generic" or "Trojan.gen" a lot. meaning they have no idea what this is and it could be something generic -- or nothing.

There is no way for us to know when and if someone will detect our software as a false positive -- and it happens a lot. We have to wait for them to make a mistake and report it to them. Then wait for them to fix it. Which sucks for us.

Hell I wrote a company called cylance like 3 months ago and they still haven't fixed it. I suppose that is why no one uses cylance. Clearly, they don't keep pace.
In this case Microsoft plain screwed up something and detect a crapload of software with the same thing.

We reported it, they fixed it - I don't expect and apology from them. But that is how the system unfortunately works. It sucks, but that is what it is.

We do our job correctly and produce quality clean software. If you don't want to white list it, that's your call. Just wait for the next update and we will be cleared.   But you, as consumers have to take a stand to help fight the false positive problem.  Authors have been fighting it to no avail.

I would have thought that that shouldn't be our job, we just purchased the license.  I had the impression that the program is supposed was developed with Microsoft's blessing.  It's not right for every user to have to struggle with Microsoft to make sense of it.  I thought the idea was you do the work and we pay for the license.  So now we're supposed to multiply efforts between us all when we have no idea what is going on.

I don't want to whitelist it because maybe how do I know the program doesn't actually have a Trojan in it?  As it is I'm getting paranoid with all this cyber hacking.  E.g., from what I read I'm pretty sure Kaspersky virus checker seems to have been hacking user's computers on behalf of Putin (the US govt is barring its use)

I just got the trojan message from Microsoft Defender today, I bet there will be lots more than already reported it.  Isn't it's job to make sure that we are safe?


I believe the task scheduling you speak of is for the tray icon -- which is a nifty feature of the program. But if you do not like it, simply turn it off in the options.

Just a guess -- But I'll wager there is an error in the audacity manifest.

Scroll about 3/4th down. The US Commercial 6 3/4 is there.

Ok - 1st. If you can restore the registry than the repairs will be put back.  That said, yes, hard without a monitor.

2nd - If you are not seeing any monitor prior to booting - than it is not  a windows driver issue and hence not a repair issue. So if you have no monitor to see the biosd or posts screens - it is either the monitor or vid card.

I am assuming that is no the case else you would not see that message. So you should be able to get to the bios.

If it is driver related, you can boot into safe mode and relaod the driver from there.
YOu can get the driver here:

99% certain you need to speak to whoever is in charge of your firewall at work and have then allow as a site.

I have a center feed HP that works fine.  I haven't used a brother before. Which model?

1) Are you selecting the right printer from the program? It may still be selected to the old dead printer.
2) If you click the print preview window in the program, does it look correct?

I think if you do have a post script enabled printer than the custom settings show up. If now. they don't.

You probably do not have a post script printer as that is sort of old.

The way I handle it is to pick an envelope size that is close - then use the offset functions to dial in exactly what I want.

I haven't heard of this before - but I suspect it may be a permission problem due to you running an old version.  I suspect the issue would not happen if you were current.

However, if somethign does happen, just right click on your taskback in a blank space and select "new task bar"

for the folder paste in this

%APPDATA%\Microsoft\Internet Explorer\Quick Launch

click enter and it should be back.

Seems to work now - but I have no idea who owns or wrote that.

75 Programs & Site Help & Support / Re: Whats up.... :(
« on: January 25, 2018, 01:46:57 PM »
profix - can you email me directly at support @ tweaking . com

I want to get some logs and some data about your machine

Pages: 1 2 [3] 4 5 ... 8