Windows not updating, fails to repair C: drive on startup

OldSpice · May 28, 2020

Hello,

Im currently running on Microsoft Windows 10 Pro, version 10.0.17763 Build 17763. When starting up my computer, the scan and repair of drive C: doesn't seem to finish after it starts, and then continues to boot up my computer. Windows also seems to not want to update, saying there is some error and to restart my computer and try again. Restarting my computer does nothing to solve this problem. I have ran sfc and DISM commands at an attempt to fix the drive.

When running sfc /scannow the return is:
Verification 92% complete
Windows Resource Protection could not perform the requested operation

When running DISM /Online /Cleanup-image /Restorehealth the return is:
Version: 10.0.17763.771
Image Version: 10.0.17763.1098
100%
Error: 0x800f081f
The source files could not be found
Use the "Source" option...
The DISM log file can be found at C: \Windows \logs \DISM \dism.log

Also tried downloading ISO and running DISM /Online /Cleanup-image /Restorehealth /Source:wim:F \Soucres \Install.wim:1 /limitaccess with return:
72%
Error :0x800f081f
the source files could not be found.
The ISO downloaded was of the latest version (2004) of Microsoft and not the version that I am currently running.

OldSpice · May 28, 2020

Also ran SFCFix.exe and it crashed. Before it crashed step 1 did not complete, steps 2-5c completed and I saw that a couple files were not fixed by the program. The resulting text file popped up:
SFCFix version 3.0.2.1 by niemiro.:
Start time: 2020-05-28 16:51:22.075
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.

SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2020-05-28 16:57:56.206
----------------------EOF-----------------------

Currently cannot run the program again without it crashing. before any steps could even begin

OldSpice · May 28, 2020

CBS files

Sysnative Windows Update · May 28, 2020

Hi!

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

Download the portable version of GSmartControl and save it on your Desktop;
Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
Please note: If the SMART Status reads: Unsupported, stop and let me know.

OldSpice · May 29, 2020

The extended self-test completed twice without any errors, unfortunately there are no logs though. There are no pink or red entries in the attributes tab

Sysnative Windows Update · May 29, 2020

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

OldSpice · May 29, 2020

Ran SFCFix Script without any troubles. The following was in the SFCFix.txt file after the steps were completed:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-05-29 21:26:09.692
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\ndizo\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.psm1
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.schema.mof

Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.psm1 to C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.psm1.
Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.schema.mof to C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.schema.mof.

Successfully restored ownership for C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.psm1
Successfully restored permissions on C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.psm1
Successfully restored ownership for C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.schema.mof
Successfully restored permissions on C:\WINDOWS\Winsxs\wow64_microsoft.packagema..dscresource.package_31bf3856ad364e35_10.0.17763.1_none_71e9cdaa982d7c81\MSFT_PackageManagement.schema.mof
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2020-05-29 21:26:10.507
Script hash: 8Gqbppu19DFc+tPWaLVn4SzU6n9UE/oGYyDjCn96x5k=
----------------------EOF-----------------------

Proceeding to the second set of steps, during the attempt to run sfc /scannow the operation did not complete, the following was displayed in the command prompt:

Code:

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 97% complete.

Windows Resource Protection could not perform the requested operation.

Finally, attached is the cbs.txt file that was requested in a zip file because the txt file was too large to upload on its own.

Sysnative Windows Update · May 30, 2020

Apply same procedure.

OldSpice · May 30, 2020

SFCFix.txt:

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-05-30 11:40:48.952
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\ndizo\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\adduser.aspx
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\edituser.aspx
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\findusers.aspx
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\manageusers.aspx

Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\adduser.aspx to C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\adduser.aspx.
Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\edituser.aspx to C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\edituser.aspx.
Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\findusers.aspx to C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\findusers.aspx.
Successfully copied file C:\Users\ndizo\AppData\Local\niemiro\Archive\WinSxS\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\manageusers.aspx to C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\manageusers.aspx.

Successfully restored ownership for C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\adduser.aspx
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\adduser.aspx
Successfully restored ownership for C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\edituser.aspx
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\edituser.aspx
Successfully restored ownership for C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\findusers.aspx
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\findusers.aspx
Successfully restored ownership for C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\manageusers.aspx
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_netfx4-aspnet_webadmin_users_b03f5f7f11d50a3a_4.0.15744.161_none_09a745512fffe225\manageusers.aspx
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2020-05-30 11:40:49.754
Script hash: k8hQCkoXRn69YpYL4+XE8woGFYgUmntUaX1AaJ7cMoo=
----------------------EOF-----------------------

Once again sfc /scannow did not complete its operation:

Code:

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 97% complete.

Windows Resource Protection could not perform the requested operation.

attached is the new CBS.txt file

Sysnative Windows Update · May 30, 2020

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running SFC just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

OldSpice · May 30, 2020

To confirm you would like the LogFile.PML and CBS.Log files to be uploaded to one of the services mentioned, then a link be posted in this thread? Is it possible to just upload the zip file to this thread?

Sysnative Windows Update · May 30, 2020

The zip will be too large.

OldSpice · May 30, 2020

Here are the requested files:

Logfile_cbs.zip

Sysnative Windows Update · May 31, 2020

Do you have a spare system with the same build?

OldSpice · May 31, 2020

I do not

Sysnative Windows Update · May 31, 2020

Then I suggest a repair install.

OldSpice · May 31, 2020

I will try this tomorrow and let you know how it goes

Sysnative Windows Update · May 31, 2020

Okay.

OldSpice · May 31, 2020

Ran the repair install successfully, ran sfc /scannow twice.

The first operation did not complete, showing in the terminal:

Code:

Beginning verification phase of system scan.
Verification 36% complete.

Windows Resource Protection could not perform the requested operation.

The second operation completed, but in the terminal was this:

Code:

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.

I suspect this is due to the found numbered files that are on my Local disk (C:) drive. Would my assumption be correct? Is there also a way to get rid of these files?

OldSpice · May 31, 2020

Also ran the CheckHealth, ScanHealth and RestoreHealth DISM commands. The following showed on the terminal respectively:

Code:

No component store corruption detected.
The operation completed successfully.

Code:

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

Code:

[===========================84.9%=================         ] The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

Windows not updating, fails to repair C: drive on startup

Member

Attachments

Member

Member

Attachments

Inactive

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member

Member