Craig wrote:I don't know enough to disagree but what I get stuck on is why would it only seem to be happening, at least my case, on two projects numbers? Couldn't that mean something in the project's programming or its output is at fault? If that is the case should every user be required to uninstall "K" or should the WU be modified? Could it be due to a particular type of video card or model's interaction with those WUs that fail? What video card were you using that worked with those Projects? I'm running an Asus 2060 Super. Could it be a problem with Windows 7 that I'm running that card on? What OS are you using?
Now I don't think my other computer is running "K" I'll have to check and if it isn't a better test might be to add it to that computer but since it is running a 3090 and running on Windows 10 I'm not sure it would be a valid test and I'm not even sure if it has ever had WUs from either of the 2 Project in question.
Is uninstalling "K" a good idea? Is it the actual root cause of the problem or is it a bandaid? Why aren't every WUs having the same problem?
As I said, I'm not qualified to argue with you on any of the actual technical issues and I'm not even sure the logic I used above is correct. Am I really off base or missing something, please let me know?
I had not considered that anyone would take my mentions of "coins" seriously or could think I did! I guess I was wrong and they apparently did and could cause harm so I will refrain from using that attempt of a joke in the future!!!
Firstly, Big Thanks for clarifying the mining bitcoin thoughts were not seriously meant
I am not suggesting uninstalling K - quite the opposite I believe it is a setting thing (see more below) ... To try and answer each of your questions:
Why would it only seem to be happening, at least my case, on two projects numbers?
... because av/security products use "alchemy"/heuristics to guess if things are damaging and sometimes a combination of factors even including such things as text strings or isp[ routings can cause issues ... please note that the two project numbers you are having issues with are run by different servers (fairly sure at different locations ... a flip side question would be if it is a server issue why would it not be happening to everyone (or even most people) folding those projects?
Couldn't that mean something in the project's programming or its output is at fault?
... absolutely it could ... but if it were so then as mentioned in previous it would probably be much wider spread as an issue ... this comes down to balance of likelihoods and tbh give what I am seeing this is not the most likely
If that is the case should every user be required to uninstall "K" or should the WU be modified?
... no - if it is a server side issue then FaH team would need to address/sort out
Could it be due to a particular type of video card or model's interaction with those WUs that fail?
... again it possibly could (but really long shot) ... but again this is quite unlikely - comms issues (which this does appear to be) are really not likely to be gpu related but one can't rule it out - one would expect however that there would be a predominance of reports of XXX gpu setups failing - which there don't appear to have been.
What video card were you using that worked with those Projects?
... personally using three various cards (RTX3070, GTX750Ti, Quadro M1000M) - none have issues ... but as previous I think this may be a very long shot cause of what seems to be a comms issue.
Could it be a problem with Windows 7 that I'm running that card on?
... this possibly might be one of the factors that plays into this as it might be a factor in how the version of Kaspersky you are running interacts ... unlikely to be the main cause - as if all Win7 folders had this issue then reports would be flooding in.
What OS are you using?
... all my kit runs Win 10 pro latest builds ... but to be honest I believe the OS will be a very minor (if at all factor) - and I am fairly sure that other folders who have experienced this type of issue have been running a variety of OS/versions - the common factor doesn't appear to normally be OS but the use of Kaspersky/Bitdefender - hence why I (and others keep harping on about it, sorry !!
Is uninstalling "K" a good idea? Is it the actual root cause of the problem or is it a bandaid?
... if it is K traffic Monitoring injecting/changing the messaging from the server (as various people suspect) then yes it might be the actual cause of the problem)
In summary
I wouldn't add Kaspersky to your other machine
just to test as this would most likely be inconclusive since many setups with K have no issues - hence why this is a pain to diagnose/remediate ... obviously if you want the protection of K on that machine then that is a different matter and I wouldn't let the issues you currently have with the Win7 setup stop you.
As a quick test (to avoid uninstalling/reinstalling) Turning off the Network Monitoring Settings
https://support.kaspersky.com/common/settings/13830 and then rebooting (after pausing/finishing FaH slots) would test if it is the network traffic monitoring ... Hopefully all blocked wus should clear (this is what has happened for others anecdotally) - but even that might (under certain circumstances) not happen - The WUs in your backlog have all probably been received (on first attempt) by the WS/CS and so might still get stuck in the loop ... If it doesn't clear them (or even if it does) you can then restart network monitoring and restore your full protections.
For me uninstalling K would be a final test (if all else fails) and one I wouldn't do lightly (as I would have installed K in the first place specifically because I wanted it to protect my kit) ... However uninstalling and then rebooting/running the kit is run for a short period of time might provide one last check - I might not choose to leave it uninstalled for long though and would reinstall it even if it did resolve the issue - and would then report this to Kaspersky support so the can remediate the issue (which may be down to a change in a signature or part of how their traffic monitoring heuristic works (think folders have done this in the past).
Using the WU status app it is possible to check if your WUs have actually been received - If they have then you can delete the working folders (ask if you want instructions) and they will no longer exist/appear in the web/advanced control interfaces and no longer keep loading your network.
TBH I am not trying to argue - simply help you resolve this ... If anyone actually knew the precise technical details of what is happening the world would be a better place and maybe a permanent resolution could be found - unfortunately all we have is quite a strong association between Kaspersky/Bitdefender/other Traffic Monitoring programs and an intermittent comms issue that in most cases appears that Final WU Upload status messages sent out from the servers are not received by the FaHClient.
AFAIK the FaH team do check the severs if this type of issue happens - and server side comms issues with overloading and other problems do occur - but the pattern of reports/complaints (even "abuse" !!) that happens if the servers are the problem tend to make it very obvious it is a server problem !!
Good Luck ... I keep my fingers crossed that by whatever means this issue gets/is resolved asap for you as has been going on long enough that it must be driving you nuts !!
