Recurring pop-up BitFefender Threat Scanner errors

U

urrguru

New member
AV seems to be working, but with all IE & Windows updates in order, fresh SpyBot install immediately displayed the error pop-up as soon as SB S&D2 Pro was installed.

Worse, the pop-up returns during shutdowns, etc.

Anyone in the know have a clue?
 

Attachments

  • Recurring 'error' pop-up for BitFefender Threat Scanner.jpg
    Recurring 'error' pop-up for BitFefender Threat Scanner.jpg
    76.3 KB · Views: 12
Hello urrguru,

Bitdefender Threat Scanner.dmp

If you receiving the following message, it is possible that one of Spybot’s files has become corrupted and needs to be replaced.



To fix this issue:

  • Please go to the Spybot program folder and check if a 32kB “SDAV.dll” file is present.
    C:\Program Files (x86)\Spybot – Search & Destroy 2
  • If the file is not present, please download this file from our “Missing Files” page, and copy it into your Spybot folder to fix this issue.
  • This file may have been removed accidentally by another antivirus or security program installed on your PC.
  • If the file is present, please check the file to see if it is the same size as the attached file. (32KB)
  • If the file has been corrupted, please replace it with the attached file.

Best regards. :)
 
Seems others reported the issue of the unexplained pop-up, Ref...

https://forums.spybot.info/showthread.php?74238-bit-denfender-windows-temp-file-Spybot-av-pro

https://www.safer-networking.org/faq/bitdefender-threat-scanner-dmp/

And yet despite the resulting link for fresh SB files, which hopefully resolves the unexplained BitDefender pop-up error, as yet how come the issue isn't or hasn't been addressed as to how and/or why a fresh SB install appears to always produce the 12KB file instead of the 32 KB "SDAV.dll" file?

Sorry for going on about over a 'dead horse' here, but for goodness sakes people, there's a dead horse lying here, and what, we all just will have to walk around it forever?

Makes me wonder how much confidence I should have in SB S&D2's AV, if it can't even point users to the problem resolution, let alone fix it by itself.
 
i went back to 2.4

image1.jpgimage1.jpg
went back to 2.4
i coundnt do anything to fix this and uninstalling 2.6 was a pain i got boxes over boxes FINALLY got rid of em
 
I had the same bitdefender threat scanner popup start while Spybot was installing. I just ignored it until my computer rebooted. When I booted back into windows the popup was gone. The popup stayed gone except for twice when I went into Spybot's System Services and stopped and uninstalled Scanner Service.

I did replace sdav.dll with the one available from the Spybot website, but it didn't stop the popups when I was messing around with the scanner service.

I don't know any way to fix it, so I think I'll just leave Spybot 2.6 installed with the scanner service off, and wait to see what Team Spybot posts. It's probably best for you to stick with Spybot 2.4 for now until you see something posted(unless you and I are the only ones with the error, that is.)

Or, if you prefer, you could open a ticket to support:
https://www.safer-networking.org/support/ticket/
 
went back to 2.4 ill let it get fixed NEWER isnt always BETTER
uninstalling 2.6 was a PAIN it kept popping the alert over over filling screen i linally got rid them and took it out
ill wait it out too much mess
 
I just registered to add my name to the list of frustrated users of 2.6 with this error.

I'm on Windows 10 home 64-bit.

Every shutdown I get this notice:

"A problem has occurred in BitDefender Threat Scanner. A file containing information. A file containing error information has been created at c:\windows\temp\BitDefender Threat Scanner.dmp. You are strongly encouraged to send the file to the developers of the application for further investigation of the error."

I uninstalled the software fully, removed all leftover folders, and re-installed. I still got the same error when shutting down. I then downloaded the replacement SDAV.dll file from the safer-networking site as directed, and replaced the file. I still get the error with each shutdown.

I give up. I never had this issue with 2.4 (or any previous version) and this doesn't give me any confidence in 2.6. This is a problem that hopefully gets addressed soon. For now I'm going to just uninstall 2.6 and wait to see if there's an update to fix this issue. Very disappointing that this error has not been resolved yet.
 
Hi. I was starting to think me and cootmaster were the only ones with this error. :)
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). 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. After I installed the Scanner Service and enabled it, I didn't get the threatscanner error. So I stayed on the computer for about an hour or so to see if it would start again, and it didn't.

After that, I decided to reboot the computer to see if I'd get the error, and I still didn't.

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.

By 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. Just what, I do not know. :laugh:

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.

I wonder why only us three have this so far?

Anyways, 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. :)
 
Hi, also just registered to comment here.

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. Also tried uninstalling, manually cleaned up all remaining remnants, and reinstall, but again, no joy.

Seems it only occurs on the shutting down of the scanner service (it must have started first though, i.e. no error if it never starts). 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. 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.

I haven't decided what I'm going to do yet, i.e. 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.

Anyway 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.
 
Thanks very much for posting and confirming it is scanner service stopping. Now I know it isn't just me with that happening. :)
 
Spybot 2.6.46 Shutdown pop up Bitdender Thread Scanner error

I have installed Spybot 2.6.46 over my previous installation which I had version 2.4 updated with the postwin10.exe file. All updates installed this way and have always got the program to update from the bottom up.
Every time I shutdown my Windows 10 Pro 64 bit edition with the Windows Creators Update I get a pop up about Bitdefender Thread Scanner. Sometimes I get the error A problem has occurred in Bitdefender Thread Scanner. A file containing error information has been created at C:Windows\TEMP\Bitdefender Thread Scanner.dmp. You are strongly encouraged to send the file to the developers of the application for further investigation of the error.
After several attempts to fix this with replacing the SDAV.dll which is stated on the website it is exactly the same size and even when replaced the error still occurs.
Can a fix please be made for this please as this is very frustrating especially from a program I have used for years without any issues.
The uninstall does not even work properly so I have forcefully removed and reinstalled without success either.
I run my own business and always recommend Spybot and install it only to find this issue.
Hopefully a solution can be found soon. Please can this be fixed as I am not the only person to experience this now.
So far just within 3 days I have seen this 4 times on different machines all running Windows 10 Creators Update edition.
Anything I can do to help please ask. Thank you.
 
Spybot 2.6.46 Shutdown pop up Bitdefender Thread Scanner error

Having updated Spybot 2.5 to 2.6.46 I keep getting the reoccurring error on my Windows 10 Pro 64 Bit Creators Update edition stating there is a problem with the Bitdefender Thread Scanner on shutdown and various other messages stating the Bitdefender thread scanner.dmp file needs to be sent off etc...
Having used Spybot for years this error is very frustrating and needs to be addressed. Replacing the DSAV.dll file which is exactly the same in the programs files (x86) spybot folder does nothing whatsoever as recommended by fixes posted on the forum.
Please can this error please be fixed?
I have tried everything from uninstalling to reinstalling forcefully as the uninstall routine has been altered so the process is not smooth without this constant error popping up.
Nothing from installing back to 2.4 will get rid of this rather annoying error which also stops my machine from shutting down properly.
I am new to here so hopefully my post will be displayed as my last one was not showing up.
Thank you.
 
Hi tk2017,

When you say it stops your machine shutting down properly, do you mean it displays the error but does eventually shut down, or that it actually never shuts down unless you physically turn it off.

Reason for asking is since my last post, I've been wondering if perhaps the fast Start-up option in win 10's power settings is a factor in this error. Despite it's name which implies it's affecting the start-up, windows achieves the fast start-up by actually altering how the machine shuts down, (i.e. kind of hibernates it instead of actually shutting it down). Personally I have this setting set to off, and my thoughts are that this error may/may not show if it's set to on, but also after reading your post, perhaps yours is set to on, and it's actually worse if it's set to on. Anyway just thinking out loud on this aspect, won't really help fix the error but may help safer-networking narrow down factors contributing to it.

I've since uninstalled the latest version, I got a couple of BSOD errors which were known to be caused by anti-virus issues among other things and so I went for the likely suspect since other scans showed no problems. Also haven't had any BSOD's since uninstalling and never had any in Win 10 prior to installing it either. Perhaps this is a coincidence, perhaps not, either way I'm boycotting version 2.6.46.
 
Got the same problem, reported it to the SupportTeam, got a ticketnumber, got a mail about the assigned ticketnumber, tried to answer to that mail, but that was not accepted, and that's it. Didn't hear anything anymore, don't know how to look into the item corresponding the ticketnumber to have a look at the status.
Compared SDAV.dll in V2.6 with the one downloaded from 'missing files', no difference whatsoever. Yet replace the original SDAV with the downloaded one, but of course that did not solve the problem
So for now I stopped the scannerservice and unchecked the on-boot option. The BitDefender error has vanished, but that is not the purpose of the program, I believe.
Marcel
 
Spybot 2.6.46 Bitdefender Scanner Error

After much annoyance from constant errors on shutdown about this error and my machine taking much longer than it should to shut down I have uninstalled.
I have used Spybot for years without any issues and it seems such a shame that the latest version has done this.
I shall try putting 2.4 back on and update this way which does not automatically take you to 2.6.46
It was working fine until I updated so hopefully this will correct the problem otherwise I shall be forced to Malware bytes instead.
The uninstall does not work without the error also popping up but after resetting the program is not running but several folders left behind only.
I have done a clear up of these.
 
Marcel6969 said:
The BitDefender error seems not to be vanished, duringshutdown my system this morning it was back again.

Marcel
Click to expand...

Yeah I had the same issue, disabling the service start on reboot, caused the startup type of the service to change from automatic to manual (in windows services view), but it would still start (presumably due to one of the other services running). I tried setting it to disabled via services and then stopped the service manually, which naturally produced the error, and then when I tried to log off (so I could get rid of the error box) My system started to do it but locked up and never got me back to the log-on screen. When I rebooted, the service startup setting was still set to manual, and the service was running, and upon checking to see what happened with my system, there was a log for a BSOD (KERNAL_DATA_INPAGE_ERROR), although I got no actual blue screen, but the log time corresponded with the time of the event. Anyway I set it to disabled again, only I left the service running this time, and then about an hour later I got a proper BSOD (UNEXPECTED_STORE_EXCEPTION, no log was created for this one). When the system automatically timed out and attempted to re-boot from that BSOD, I got a bios error message saying it couldn't boot from the specified drive as it wasn't a boot drive. After manually switching off the system and turning it back on, the drive light lit up (unlike a few moments ago) and windows booted. The service was back to manual startup & running again. After reading a bit about the latest BSOD, as that sequence of events had me thinking the worst, turns out it's actually kind of normal behavior for that error type and one of the causes mentioned was anti-virus software, so I decided to uninstall 2.6.46, and reverted to 2.4 and everything has been fine since.
 
The only solution I have found that keeps Spybot working is uninstalling 2.6.46 completely and deleting all the folders and registry entries left behind.
Reinstall 2.4 only and update but do not run Post Win10 Spybot-install.exe as it will just update back to 2.6.46 and there error will be back again.
Hopefully a fix for this will be found soon and everyone will just have to keep an eye out for 2.6.47 or 2.7 or whatever they decide to call it.
I'm not really certain if 2.4 works properly on Windows 10 hence why the 2.5/2.6/2.6.46 updates have been released but when it is running it appears to be working as it should do.
When you go to download 2.4 it states it is for Windows XP and Vista now which is not entirely true.
I just wish they had tested this properly as clearly this happens every time and I have done fresh installs and it always happens on Windows 10 with 2.6.46.
 
You must log in or register to reply here.
Back
Top