nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Is DiscoverySrv.exe 27.1.1.45 buggy? [fixed with Bitdefender Agent version 27.1.1.48]

bjrazumich

The DiscoverySrv.exe version 27.1.1.45 that installed on my laptop on 14 August continuously is using 25% of my CPU and generating a lot of heat on the laptop. This was not an issue prior to this version being installed during the 14 August update. The file itself shows as created on 11 August. My laptop is running Windows 10 with extended security updates turned on (because, of course, it can't be updated to Windows 11). If I kill the executable from task manager my laptop will gradually cool down and so far as I can see, it does not restart until the next time I restart my laptop.

If there is a bug report site here I apologize for not finding it and will be happy to follow whatever path is suggested. Thank you.

Find more posts tagged with

Accepted answers

Alexandru_BD

UPDATE: the issue has been fixed through Bitdefender Agent version 27.1.1.48, available to 1k users at the moment + fresh install. An automated update is rolling out.

All comments

JAFFrisco

SAME, on BOTH of my laptops. I've talked to Support twice in the last 2 days, and they don't know what to do. I'm stopping DiscoverySrv.exe from the task manager, and Bitdefender shows it is still protecting my computer(s). They need to retract that update

Alexandru_BD

Hello,

I would like to ask everyone encountering this issue and reading this thread to contact Bitdefender Support directly, as they already received a few similar reports and more information is required for troubleshooting.
You can get in touch with them by choosing one of the contact channels listed here:

https://www.bitdefender.com/consumer/support/help/

State your contact reason, choose request category, then select from the available contact channels, chat, phone and email/ticket. Chat would be the fastest way to reach them.

Let us know how it goes.

bjrazumich

Thanks for the reply and the support link.

JAFFrisco

I renamed DiscoverySrv.exe to .bak to keep it from running. It was driving me nuts, kicking the fan on high when I was away from the computer.

bjrazumich

As requested by user Alexandru_BD, The current status.

TLDR version: Still eating CPU and generating heat.

Details: I interfaced with the AI chat feature. It told me to:

1. Update Bitdefender to the latest version.
2. If you have any other antivirus software installed, remove it.
3. Run System File Checker:
   - Open Command Prompt as administrator
   - Run: `sfc /scannow`
   - Wait until it finishes, then restart the PC
4. If the issue continues, run DISM:
   - Open Command Prompt as administrator
   - Run: `DISM.exe /Online /Cleanup-Image /RestoreHealth`
   - Wait for it to finish, then restart

Items 1 & 2 were not needed, as I have the latest build (else why would I be complaining in the first place?) and I don't have any other AV software installed. Items 3 & 4 are Windows tools, and they pretty much ran long and didn't help. Interestingly enough, I trust the AI even less, as it noted that the current production build of my product was older than the one actually installed on my system. I'm sure someone's LLM needs updating.

I received a follow up email from "Simona" (no last name) asking if I had further issues. I replied that the AI suggestions didn't help, and would be happy to help debug, but no response back yet. I may just do what JAFFrisco has done and rename my installed DiscoverySrv.exe file so that it never starts after a reboot, and wait to see what happens when BitDefender Agent 27.1.1.46 (or higher) is installed.

DIVERSE

Similar for me.

"DiscoverySrv (32 bit)" is consistently sitting at a CPU usage of about 10% (9.6–9.8% currently) in Task Manager on Windows 10. My laptop has an 8-core CPU, so 10% corresponds roughly to full usage of one core. For people with quadcore machines, it might thus use about 25% of the CPU.

I initiated an update of Bitdefender Total Security maybe a week or more ago [edit: the record shows that it was on 2026-08-03 20:44], and only just rebooted the laptop today. I noticed the high CPU usage occurring today both before and after the reboot, however.

My current version is shown as 27.0.61.344.

Perhaps the version number of the update "agent" is different, as the troublesome file is located at
C:\Program Files\Bitdefender Agent\27.1.1.45\DiscoverySrv.exe
on my laptop's internal SSD.

The onus should not be on me, as a customer, to debug or even diagnose faults in commercial software :-(

RoMo5

Is this a Windows 10 problem as it is not causing any problems on my Windows 11 system.

bjrazumich

In my opinion, maybe, but not for all Windows 10 systems. While my laptop is on 10, as noted in my original post, I have access to another Windows 10 system which is a desktop with the same version of the Bitdefender agent and the problem is not showing there. I also own a laptop with Windows 11, and that system is a happy camper.

For the record, my Windows 10 laptop is as current as possible with patches, including extended security patches. (In case anyone asks)

bjrazumich

I don't disagree with your opinion regarding debugging the issue. For me, it's a matter of choice, so I didn't have any issues with generating debug info for Support.

My versions of Bitdefender and the agent match yours. On my laptop the current versions were installed on August 14. The update date for the file itself shows August 11. I'd almost wonder if something was recompiled without updating a version number. I've seen stranger things.

Helix

It's not a Windows 10 problem, because my all-in-one PC has the latest version of Windows 11, and I experiment the same problem.

hodgie303

I have a Windows 10 desktop computer and it is doing the same thing,DiscoverySvr.exe uses about 15% cpu and makes my fan go fast,I have the latest version of Bitdefender TS.

I go to task manager and end task ,but it is a pain in the butt.

I wish they would fix it!!!

Hodgie303

bjrazumich

I have a new update. I have received an update on my support case, and have been advised that "…the situation is caused by an issue that has already been acknowledged by our development team. We are currently working on a fix that will be done by means of an automatic update…"

Naturally, I wasn't given an ETA on the timing; any good developer, once coding the fix, would want to test it thoroughly before it was released (and no comments about why the current one wasn't tested - some issues don't occur until after a release). I was advised I would get an update regarding the fix as soon at Bitdefender had one.

bjrazumich

Another update: Auto Update updated the version of DiscoverySrv.exe to 27.1.1.46 for me today. As the fix is not in place yet, it is no surprise that the high CPU and hot fan use still persists. I did update the tech working my support ticket about my noticing this.

hodgie303

My Bitdefender updated and it is the same, 15%+ cpu usage fan in high revs, this 27.1.1.46 update does not work.

I am going to get support on to it.

Cheers.

Alexandru_BD

UPDATE: the issue has been fixed through Bitdefender Agent version 27.1.1.48, available to 1k users at the moment + fresh install. An automated update is rolling out.

bjrazumich

Thanks for the update. I received a similar email from the support engineer handling my case about 20 minutes after you made your post here. Ideally the version of Bitdefender Agent will update straight to 27.1.1.48 from the version 46 that is currently on my laptop.

RoMo5

Hopefully this works and thanks to all who have spent time liaising with Bitdefender Support.

Alexandru_BD

Keep us posted here, let's get some feedback after everyone receives the update so we can make sure this has been fixed.

Thanks! 🤜🤛

Helix

Today Bitdefender Agent was updated to 27.1.1.48 on my computer, and the problem is
gone!
DiscoverySrv.exe now uses 0% of my CPU. 🙂

Alexandru_BD

Happy to hear this, and thank you for the feedback!

bjrazumich

I'm happy to note that apparently this evening was my turn for the 27.1.1.48 update, and the fix works on my laptop, too. Once again the universe is safe for exploration, and other stuff like that.

My thanks for the nice turnaround for the code fix. I'd love to know what the root cause was, but I imagine that like my past employers, that actual info won't be for public consumption. That's fine, I'll take the fix for the win.

Alexandru_BD

Thank you for the feedback, much appreciated. To be honest I'm not even sure what it was, but like you said, it's good to know they fixed it.