Windows 10: What else can I do to fix the corrupt files?

I ran "sfc /scannow", and it said "Windows Resource Protection found corrupt files but was unable to fix some of them".
I ran "DISM /Online /Cleanup-image /Scanhealth", and it said "No component store corruption detected".
I ran "CHKDSK C:", and it said "Windows has scanned the file system and found no problems".

What else can I do to fix the corrupt files?







:)

 

What else can I do?

Does your device have an ID? Check in Start > Settings > About > Device ID.

Pocket PC Mauritius omnia i900 avnya henriett

 

What else can I do?

Lets try disabling Advanced Network Functionality.

Go to Start - Settings - Connection - USB to PC.

Check/Uncheck Advanced network functionality and connect your device.

http://www.experiencemobility.net

 

Suggest you post the log (zipped) or examine it yourself to see what's reported.

Also post your current build
Windows key + R, winver

Have you modified any dll's - e.g. icons?

 

You could try running sfc /scannow offline at boot, Option One in the tutorial...

Run SFC Command in Windows 10

 

Click here to download the log.
OS Build 16299.248
I don't know how to modify DLL files, so I think I have never done so.

 

Hi, that seems very short. Please try zipping it and attaching it to your post

 

Which one is the partition/volume where my system boot files are stored?

Done as you said.

 

This is all there is... extremely short- seems incomplete?

Go with @Bree's idea of running it when offline (not booted into Windows)

2018-02-23 18:20:54, Info CBS TI: --- Initializing Trusted Installer ---
2018-02-23 18:20:54, Info CBS TI: Last boot time: 2018-02-23 17:48:55.495
2018-02-23 18:20:54, Info CBS Starting TrustedInstaller initialization.
2018-02-23 18:20:54, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2018-02-23 18:20:54, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2018-02-23 18:20:54, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2018-02-23 18:20:54, Info CBS Ending TrustedInstaller initialization.
2018-02-23 18:20:54, Info CBS Starting the TrustedInstaller main loop.
2018-02-23 18:20:54, Info CBS TrustedInstaller service starts successfully.
2018-02-23 18:20:54, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2018-02-23 18:20:54, Info CBS Startup processing thread terminated normally
2018-02-23 18:20:54, Info CBS TI: Startup Processing completes, release startup processing lock.
2018-02-23 18:20:54, Info CBS Starting TiWorker initialization.
2018-02-23 18:20:54, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2018-02-23 18:20:54, Info CBS Ending TiWorker initialization.
2018-02-23 18:20:54, Info CBS Starting the TiWorker main loop.
2018-02-23 18:20:54, Info CBS TiWorker starts successfully.
2018-02-23 18:20:54, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3
2018-02-23 18:20:54, Info CBS Universal Time is: 2018-02-23 10:20:54.379
2018-02-23 18:20:54, Info CBS Loaded Servicing Stack v10.0.16299.15 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.15_none_2c4b8d3b386eed8e\cbscore.dll
2018-02-23 18:20:54, Info CSI 00000001@2018/2/23:10:20:54.379 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffcd9624519 @0x7ffcd9a2b8b6 @0x7ffcd9a2bd78 @0x7ff7f7c22c32 @0x7ff7f7c235b8 @0x7ffd14196d23)
2018-02-23 18:20:54, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
2018-02-23 18:20:54, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
2018-02-23 18:20:54, Info CBS NonStart: Set pending store consistency check.
2018-02-23 18:20:54, Info CBS Session: 30649487_4239773314 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-02-23 18:20:54, Info CBS Client specifies manual store corruption detect or repair.
2018-02-23 18:20:54, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30649487_4239773314
2018-02-23 18:20:54, Info CBS Reboot mark set
2018-02-23 18:20:54, Info CBS Winlogon: Registering for CreateSession notifications
2018-02-23 18:20:54, Info CBS Winlogon: Loading SysNotify DLL
2018-02-23 18:20:54, Info CBS Winlogon: Starting notify server
2018-02-23 18:20:54, Info CBS FLOW: Entering stage: CheckCbs

 

Looks to be Volume 1.

 

Okay. I am now running it again, and I will post it again when it has finished. Please wait.

Volume 1 is my Windows 10 partition, so which is the partition/volume where my system boot files are stored?

 

From Option One of the sfc tutorial...

If that diskpart command was run from a command prompt at boot, looks like it's C:.

 

The command was run via PowerShell. Volume 3 is the recovery partition because the two Chinese characters mean "recovery". Is it the partition/volume where my system boot files are stored?

 

Click here to download the much longer, complete one.

 

You need to boot to advanced options and the Command prompt at boot, then run diskpart. The drives may well be assigned different letters when you are not running from the windows system. Then run sfc from the same command prompt to do an offline repair.

Open Command Prompt at Boot in Windows 10