[SOLVED] Cannot update from 1803 to 1903

S

suprteacher

Member
Joined
Nov 8, 2019
Posts
14
Hi all-
I've been looking through all kinds of posts and cannot figure out how to update my Windows 10 from 1803 to 1903. I wouldn't have even noticed, but according to Windows Update, 1803 is not going to be supported. When Windows Update checks for updates, I get that everything is up to date. I've tried every solution I've found on the web. I cannot even reset without getting an error.
I tried updating using the Windows Creation disk iso, but again didn't work.
I cannot run dism scan health without getting error 4448: The WOF driver encountered a corruption in the compressed file's Resource Table.
Sfc /scannow stops in the Verification phase with error- Windows Resource Protection could not perform the requested operation.

Any help will be greatly appreciated.
 
Hello and welcome!

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.
    info_failing.png
 
Thank you for the help. Here are the results and attributes.
 

Attachments

  • self-test.png
    self-test.png
    70.9 KB · Views: 9
  • attributes.png
    attributes.png
    71.7 KB · Views: 9
I did notice that my SSD system drive says Automatic Offline Data Collection status: DISABLED, whereas my other hard drive has this enabled. Not sure if that's a big deal or not.

One other note, when I originally went to update it showed my C drive as compressed and wouldn't let me update until the drive was uncompressed. This is when I started having the troubles.
 
I've been backing up using Macrium Reflect.

I have nothing else that is showing me that this drive is failing. The drive isn't that old.
 
I appreciate your help. Is there anything else I can do at the moment to be able to update? If I do a wipe of the drive and a clean install of Windows, how would I reinstall the programs using my Macrium backup?
 
I can, but I would genuinely advise against it.

If the image is stored on a different drive, you can recover it via Macrium Boot CD.

Rescue a system with the Windows PE environment


If you are adamant to try and fix this, please do the following:

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
I would like to fix this. I realize the drive may be on its way to failing, but think there is also some file errors that hopefully I can fix.

The one worry I have about my current backup through Macrium is if there are file errors, those will be pushed to the new drive when recovering. I'd like to be able to fix these and when the drive does fail, I know my backup is going to be error free.

Again I do appreciate all the help you're giving me.

Once again, my sfc /scannow verification got to 98% before giving me the Windows Resource Protection could not perform the requested operation.
I have attached the cbs.txt file
cbs.txt
 
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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Thank you.

Here is the sfcfix.txt. I'm running sfc /scannow right now. I'll post when it completes.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-11-08 13:47:18.237
Microsoft Windows 10 Build 17134 - amd64
Using .zip script file at C:\Users\Eaton\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll

Failed to backup file C:\WINDOWS\Winsxs\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll with error code 0x1160.

Successfully copied file C:\Users\Eaton\AppData\Local\niemiro\Archive\WinSxS\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll to C:\WINDOWS\Winsxs\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll.

Successfully restored ownership for C:\WINDOWS\Winsxs\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_netfx35linq-system.addin.contract_31bf3856ad364e35_10.0.17134.1_none_b15d0e12ee104fda\System.AddIn.Contract.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2019-11-08 13:47:18.706
Script hash: fae8ErVSBa6d0cHej8xKgk8JkiGkNqbyW41ZZe9JqxE=
----------------------EOF-----------------------
 
Here is my new cbs file. I received the message after sfc /scannow verification 100% complete.
Windows resource protection found corrupt files but was unable to fix some of them.

cbs.txt
 
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.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. 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


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

The sfcfix file is as follows

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-11-08 15:51:51.601
Microsoft Windows 10 Build 17134 - amd64
Using .zip script file at C:\Users\Eaton\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_microsoft-windows-cdosys.resources_31bf3856ad364e35_10.0.17134.1_es-es_e97818a372e3ef5d
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-v..lient-wmiv2provider_31bf3856ad364e35_10.0.17134.1_none_e66fccc7f1db9f1b\vpnclientpsprovider.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.1067_none_cbcc59c5923b214e\browsermdl.ttf

Failed to copy file C:\Users\Eaton\AppData\Local\niemiro\Archive\WinSxS\x86_microsoft-windows-cdosys.resources_31bf3856ad364e35_10.0.17134.1_es-es_e97818a372e3ef5d\cdosys.dll.mui to C:\WINDOWS\Winsxs\x86_microsoft-windows-cdosys.resources_31bf3856ad364e35_10.0.17134.1_es-es_e97818a372e3ef5d\cdosys.dll.mui with error code ERROR_ACCESS_DENIED.
Successfully copied file C:\Users\Eaton\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-v..lient-wmiv2provider_31bf3856ad364e35_10.0.17134.1_none_e66fccc7f1db9f1b\vpnclientpsprovider.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-v..lient-wmiv2provider_31bf3856ad364e35_10.0.17134.1_none_e66fccc7f1db9f1b\vpnclientpsprovider.dll.
Successfully copied file C:\Users\Eaton\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.1067_none_cbcc59c5923b214e\browsermdl.ttf to C:\WINDOWS\Winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.1067_none_cbcc59c5923b214e\browsermdl.ttf.

Successfully restored ownership for C:\WINDOWS\Winsxs\x86_microsoft-windows-cdosys.resources_31bf3856ad364e35_10.0.17134.1_es-es_e97818a372e3ef5d
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_microsoft-windows-cdosys.resources_31bf3856ad364e35_10.0.17134.1_es-es_e97818a372e3ef5d
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-v..lient-wmiv2provider_31bf3856ad364e35_10.0.17134.1_none_e66fccc7f1db9f1b\vpnclientpsprovider.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-v..lient-wmiv2provider_31bf3856ad364e35_10.0.17134.1_none_e66fccc7f1db9f1b\vpnclientpsprovider.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.1067_none_cbcc59c5923b214e\browsermdl.ttf
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.17134.1067_none_cbcc59c5923b214e\browsermdl.ttf
PowerCopy:: directive failed to complete successfully.




Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2019-11-08 15:51:52.468
Script hash: vI2aWPn66LReHFch23hYzVQdaHk8bNgZsTw8ibPxwDQ=
----------------------EOF-----------------------
 
Here's my new cbs.txt file. Again sfc /scannow verification 100%, but Windows Resource Protection found corrupt files but was unable to fix some of them

cbs1.txt
 
You must log in or register to reply here.

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

Back
Top