![]() ![]() keep 2.6 without scanner service starting up or go back to 2.4, One thing I did notice after unchecking the on-reboot option is it started up anyway, but it may have been because I used spybot settings to check if it was running, and unchecking the box did set to manually start in services (instead of automatic), so perhaps the act of starting spybot started it and I need to set the service to disabled in sevices to prevent it starting completely.Īnyway I hope a fix for this is found soon, and regarding the number of people getting this error, I suspect there is more than just us, we're just the ones who have posted about it, and also realize it's to do with spybot since the error states it's bitdefender, many will be thinking virus not realising it's used with spybot, and then there will be a bunch of people who rarely shutdown/reboot their systems, using sleep/hibernate instead, and I'm not sure it happens under those conditions, But they will possibly realize next time windows wants to reboot to complete an update.Virus Scanner Plus by Bitdefender brings the company's top rated antivirus technology to the App Store! I haven't decided what I'm going to do yet, i.e. Manually shutting down the service via spybot settings or through services management however produces the same popup error, but it is perpetual and can't be resolved or dismissed by re-starting the service, or any other means that I've discovered, except by doing a shutdown, reboot or user logout. This for me is completely repeatable, and naturally this happens when shutting down & rebooting as well, since the service is stopped during those events (again if it was on), the popup appears, but at least with reboot/shutdown, it is killed off. Seems it only occurs on the shutting down of the scanner service (it must have started first though, i.e. Also tried uninstalling, manually cleaned up all remaining remnants, and reinstall, but again, no joy. I'm getting the same problem, the sdav.dll file doesn't seem to be the culprit this time as replacing it doesn't fix it, and for me the size was correct anyway, but still tired a couple of times, under varying conditions, like scanner service both on & off. Hi, also just registered to comment here. I wonder why only us three have this so far?Īnyways, just thought I'd post this for info, I'm not suggesting that anybody shutdown Scanner Service or anything like that, it is needed for certain things in Spybot like scanning single files, etc. Okay, I just tried it a fourth time, and after unchecking Active After Every Reboot, and then stopping Scanner Service the Bitdefender Threat Scanner error came up again. ![]() So after I logged back into windows, I opened Spybot start center, then Settings, went to the System Services tab, unchecked the Active After Every Reboot, stopped the Service, all was well, and then when I hit uninstall the threatscanner error boxes started happenng again.īy Murphy's Law and my luck, it's some mad coincidence, but this is the third time the threatscanner errors have happened connected to Scanner Service, so I think it must be something with it. So I stayed on the computer for about an hour or so to see if it would start again, and it didn't.Īfter that, I decided to reboot the computer to see if I'd get the error, and I still didn't. After I installed the Scanner Service and enabled it, I didn't get the threatscanner error. After reading your post, I decided to reinstall and turn on the Scanner Service to try to get the error again, or to try to see if having the Scanner Service running and the threat scanner error was some sort of mad coincidence. ![]() I've kept Spybot 2.6 up to now with the Scanner Service uninstalled and haven't been getting the threatscanner error(I posted about that in my previous post). I was starting to think me and cootmaster were the only ones with this error. Very disappointing that this error has not been resolved yet. For now I'm going to just uninstall 2.6 and wait to see if there's an update to fix this issue. This is a problem that hopefully gets addressed soon. I never had this issue with 2.4 (or any previous version) and this doesn't give me any confidence in 2.6. I still get the error with each shutdown. I then downloaded the replacement SDAV.dll file from the safer-networking site as directed, and replaced the file. I still got the same error when shutting down. I uninstalled the software fully, removed all leftover folders, and re-installed. ![]() You are strongly encouraged to send the file to the developers of the application for further investigation of the error." A file containing error information has been created at c:\windows\temp\BitDefender Threat Scanner.dmp. "A problem has occurred in BitDefender Threat Scanner. I just registered to add my name to the list of frustrated users of 2.6 with this error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |