Windows 10: SFC and DafPrintProvider recurring error

Win10 22H2Every time SFC is run it repairs DafPrintProvider.dll.2024-12-10 22:39:47, Info CSI 00002761 [SR] Beginning Verify and Repair transaction2024-12-10 22:39:47, Info CSI 00002763 [SR] Repairing file \??\C:\WINDOWS\System32\en-US\\DafPrintProvider.dll.mui from store2024-12-10 22:39:48, Info CSI 00002764 [SR] Verify completeYet, as stated the issue is found 'every' time so appears to NOT actually be repaired.I've run DISM RestoreHealth as well but it does not detect this issue.

:)

 

Recurring Explorer error that I cannot trace

I'd consider myself a fairly advanced home user, even daring to call myself a superuser but I've recently experienced a recurring error dialog that I cannot trace that is driving me mad.

My workstation is a Windows 10 64Bit Version 1809 (Build 17763.316) and I get the recurring dialog:

"This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the Default Apps Settings page."

What's weird is that there is no corresponding log in the event viewer under the "Application" or the "System" event logs. Is there anything I can do to trace this issue further?

Applications running at the time of error:

• Visual Studio 2015
  
• SQL Server Management Studio
  
• Google Chrome (only my web app is open and there's nothing that calls for an app to open)
  
• Eset NOD32 Antivirus (12.1.31.0)
  
• Sticky Notes
  

Is there a way to enable advanced debugging or trace what process is trying to open a file? There are no scheduled tasks that would suggest they're the cause of this issue either..

 

SFC fixes problems (but only temporarily...)

Hi, Lothar Krepke

Welcome to the Microsoft Community



Thank you for reaching out to us regarding the recurring issue you’re experiencing on Windows 11 23H2. We appreciate your efforts in trying multiple troubleshooting steps, including running the System File Checker (SFC), which seems to have provided a temporary resolution.

The issues you’re encountering could stem from various factors, such as outdated drivers, software conflicts, or corrupted system files. The temporary resolution provided by running SFC /Scannow suggests potential underlying issues with system files, drivers, or even hardware components. Let’s delve into some additional troubleshooting steps to identify and address the root cause:

1. Update Windows and Drivers: Ensure all your device drivers are up-to-date, particularly those for your graphics card, chipset, and input devices (mouse and keyboard). Outdated or incompatible drivers can often lead to erratic system behavior.
   
2. Event Viewer Logs: Review the Event Viewer logs for any error messages or warnings that might shed light on the root cause of the issues. Look for recurring patterns or specific error codes.
   
3. Clean Boot: Consider performing a clean boot to start Windows with a minimal set of startup programs and services. This can help identify if a third-party application or service is causing conflicts with the system.
   
   • Press , type , and press Enter.Win + Rmsconfig
     
   • In the System Configuration window, go to the tab.Services
     
   • Check and then click .Hide all Microsoft servicesDisable all
     
   • Go to the tab and click .StartupOpen Task Manager
     
   • Disable all startup items, then close Task Manager and click in the System Configuration window.OK
     
   • Restart your computer.
     
   These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track. 
   
    
   
4. Run DISM Tool: If the issues persist even after running SFC /Scannow, consider using the Deployment Image Servicing and Management (DISM) tool. This tool can address Windows corruption errors that SFC /Scannow might not be able to fix. Here’s how to use it:
   
   • Search for ‘cmd’ in the start menu and open the command prompt as an administrator.
     
   • Enter the following command and press Enter: DISM /Online /Cleanup-Image /RestoreHealth
     
5. Hardware Check: If none of the above solutions work, the issue might be hardware-related. Try using different peripherals to see if the problem persists.
   

Please keep us updated on your progress. If you have any further questions or concerns, don’t hesitate to ask. We’re here to support you!



Best Regards,

Martin | Microsoft Community Support Specialist

 

sfc /scannow error repair

Hi,



Thank you for writing to Microsoft Community Forums.



We appreciate the efforts you have taken in trying to resolve this issue. I have analyzed the error logs that you have shared and I would suggest you follow the steps mentioned below:

1. Type Command Prompt in the
   search bar on the Taskbar.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, paste the following command and hit Enter:
   DISM.exe /Online /Cleanup-image /Restorehealth
   
4. Once the DISM command is executed, we would suggest you to run sfc /scannow again.
   

If the integrity violations are not repaired after running sfc scan, the best option will be performing a repair installation. A repair installation will repair all the corrupted files.



Refer the steps mentioned below:



Download the Windows 10 Media Creation Tool (MCT) and use it to perform a repair installation
of Windows 10. We have a video that can show you how if you aren’t sure



Let us know the results.



Regards,

Nikhar Khare

Microsoft Community - Moderator