Sfc and corrupt bluetooth files

Anonymous
2024-07-26T14:43:11+00:00

Windows 11 24H2 26100.1297 Release Preview Channel

After installing Windows, one of the first things I do is to turn off Bluetooth.

Yesterday morning I had run SFC /scannow and it was alright.

Yesterday afternoon there was the update to .1297 and I installed it.

A few moments ago I ran SFC again and it found and repaired corrupt bluetooth files.

So question is before the update sfc was ok. After the update corrupt files.

Question is why is MICROSOFT sending updates with corrupt files? Is this just a lack of quality control on their end?

This has happened quite a few times and it is always the bluetooth files that are corrupt, seems to happen after Windows Updates.....

Windows Insider program | Windows Insider preview | Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-26T15:29:44+00:00

    You stated you had the Bluetooth turned off on that system. Is there some reason for not using the onboard Bluetooth?

    If you are using an external Bluetooth, maybe the files are conflicting.

    Have you checked the log to see which Bluetooth files are being corrupted?

    Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    Try running the command in an Admin command prompt. The command needs to be changed for it to work in PowerShell.

    0 comments No comments
  2. Anonymous
    2024-07-31T18:15:35+00:00

    Hey there Saltgrass

    After you responded several days ago, I went and downloaded the latest Intel Bluetooth drivers for my system, installed them and enabled Bluetooth. Ran a sfc /scannow after enabling it and no problems were found.

    Now, today just upgraded to the latest Insider Release Preview 26100.1301 and guess what:

    2024-07-31 12:54:17, Info CSI 00000224 [SR] Beginning Verify and Repair transaction

    2024-07-31 12:54:17, Info CSI 00000225 [SR] Repair complete

    2024-07-31 12:54:17, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

    2024-07-31 12:54:17, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

    So with Bluetooth on, and the latest drivers installed I got the same corrupt files as usual.

    Do you think this is a problem on Microsofts end....since it's the same files, if Bluetooth is not enabled///Enabled?

    0 comments No comments
  3. Anonymous
    2024-07-31T18:38:57+00:00

    Hey there Saltgrass

    After you responded several days ago, I went and downloaded the latest Intel Bluetooth drivers for my system, installed them and enabled Bluetooth. Ran a sfc /scannow after enabling it and no problems were found.

    Now, today just upgraded to the latest Insider Release Preview 26100.1301 and guess what:

    2024-07-31 12:54:17, Info CSI 00000224 [SR] Beginning Verify and Repair transaction

    2024-07-31 12:54:17, Info CSI 00000225 [SR] Repair complete

    2024-07-31 12:54:17, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

    2024-07-31 12:54:17, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

    So with Bluetooth on, and the latest drivers installed I got the same corrupt files as usual.

    Do you think this is a problem on Microsofts end....since it's the same files, if Bluetooth is not enabled///Enabled?

    This problem has been going on for over a year and never found any solution for it. It fails almost every time after an update.

    Strange enough for me, not this time. šŸ˜‚šŸ¤·ā€ā™‚ļø

    Image

    Here is another one just seen today after an update/repair in place of current public build 22631.3958. šŸ˜µā€šŸ’«šŸ¤¬šŸ˜

    0 comments No comments
  4. Anonymous
    2024-07-31T19:37:49+00:00

    I checked that file on my advanced build. The attachment is below so you can compare. I have seen some files are bad and don't get replaced.

    I did not see any device using that driver. The SFC scan completed but it did take a really long time to finish.

    0 comments No comments
  5. Anonymous
    2024-08-02T20:58:01+00:00

    Here is a fresh one with Build 22635.4005, it is a common problem that MS has been ignoring for a long time. 😜

    2 people found this answer helpful.
    0 comments No comments