sfc/scannow : windows resource protection found corrupt files and unable to fix

nice_tk

Member
Joined
Sep 20, 2013
Posts
6
my problem is when windows starts, the message 'Server Busy : This action cannot be completed because the other program is busy.Choose 'Switch To' to activate the busy program and correct the problem.' comes up. Next, I try the command sfc/scannow(I can try in safe mode only) and this is my CBS log
https://www.dropbox.com/s/4azwuvym8shcs4b/CBS.zip

pls. download and check it
 
Here's the relevant entries from the SFC scan...
Code:
 Line 4410: 2013-09-20 13:18:08, Info                  CSI    0000030e [SR] Repairing 3 components
 Line 4411: 2013-09-20 13:18:08, Info                  CSI    0000030f [SR] Beginning Verify and Repair transaction
 Line 4414: 2013-09-20 13:18:08, Info                  CSI    00000311 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4417: 2013-09-20 13:18:08, Info                  CSI    00000313 [SR] Cannot repair member file [l:24{12}]"mingliub.ttc" of Microsoft-Windows-Font-TrueType-MingLiUB, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4420: 2013-09-20 13:18:08, Info                  CSI    00000315 [SR] Cannot repair member file [l:22{11}]"PINTLGB.IMD" of Microsoft-Windows-IME-Simplified-Chinese-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol in a few minutes
 
I've uploaded a file - ntkaa.zip- to my SkyDrive at Noel's SkyDrive

Please download and save it.



Right-click on the saved file and select Extract all...

Change the target to C:\ and click on Extract

Close all windows (it would be a good idea to print these
instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start
tapping F8 - this should bring up the Advanced Boot Menu, at the top of which
should be the option 'Repair my Computer'

Pick that

You'll have to log in with your username and password.



Pick the option to use a Command Prompt

At the prompt type

DIR C:\ntkaa

hit the enter key - if you get a 'Not
Found' error try

DIR D:\ntkaa

or

DIR E:\ntkaa






The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...





XCOPY <drive>:\ntkaa <drive>:\windows\winsxs /y /i /s /v /h





(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )





run the command (it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enter key to exit Command Prompt - reboot to Normal Mode Window s.



Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot and upload the new CBS.log file to your reply
 
I checked for malware and problem is still and I try a clean boot process and finally I find that Bluetooth Device Monitor causes my problem.

cause.png

So, what will I do next?
 
Your system clock appears to be way off date!
Please check your System Time settings - specifically, the year, as it seems to be 2556, currently.
This will throw many things off, including security certificates.
 
The usual cure is to remove the device from Device Manager in Safe Mode, and reboot - this should reinstall the driver.
If it still causes problems, go to the manufacturer's website and see if they have updated drivers for it.
 
Okay, I reinstalled the driver and the problem is solved.:smile9:
Thank you very much for your kindness.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top