[SOLVED] [10v1703b15063 x64] WU fails and sfc doesn't work dism gives Error:582

Here is the result

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-28 17:17:02.012
Microsoft Windows 10 Build 15063 - amd64
Using .txt script file at C:\Users\Owner\Desktop\SFCScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_10.0.15063.0_tr-tr_a5e84df14d3e554b.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_10.0.15063.0_tr-tr_a5e84df14d3e554b.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comctl32-v5.resources_31bf3856ad364e35_10.0.15063.0_tr-tr_a5e84df14d3e554b.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2018-01-28 17:17:04.035
Script hash: VvtJG/cweTzM/HaI5WqdKkOu5xCkf5HwgcYSo2Ck13s=
----------------------EOF-----------------------
 
Good. Please repeat the following. I'll only need the Logfile.pml if you get another Error: 582


Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor as soon as sfc fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log.
 
We have another corruption to fix as shown below.
Capture.JPG

Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

Sorry for the delay, here is the result.

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-31 22:40:56.700
Microsoft Windows 10 Build 15063 - amd64
Using .txt script file at C:\Users\Owner\Desktop\SFCScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comdlg32.resources_31bf3856ad364e¾5_10.0.15063.0_bg-bg_b18ba9fa1bdcf885.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comdlg32.resources_31bf3856ad364e¾5_10.0.15063.0_bg-bg_b18ba9fa1bdcf885.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comdlg32.resources_31bf3856ad364e35_10.0.15063.0_bg-bg_b18ba9fa1bdcf885.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comdlg32.resources_31bf3856ad364e¾5_10.0.15063.0_bg-bg_b18ba9fa1bdcf885 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-comdlg32.resources_31bf3856ad364e35_10.0.15063.0_bg-bg_b18ba9fa1bdcf885.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2018-01-31 22:40:57.608
Script hash: dLoCqjjMwJ+Qjpv6+34PWGU0Tr2mlgAQF9petJwTc9I=
----------------------EOF-----------------------
 
I did a sfc /scannow
and here is the result and CBS.log. Do you want me to do the Process Monitor log file as well?

View attachment CBS.zip

Code: 
C:\WINDOWS\system32>sfc /scannow


Beginning system scan.  This process will take some time.


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


Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


C:\WINDOWS\system32>
 
No need for Procmon yet. We're making good progress. Please do the following now.

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
BrianDrab said:
No need for Procmon yet. We're making good progress. Please do the following now.

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...

Zip file is only 280kb. Attaching here itself

View attachment CBS.zip
 
I burned the MemTest86 into a DVD and running that now. I didn't see a setup where I can set how many pass thru. It is going on several passes, except Test 0 all are having several errors. Errors are showing 65535+.
If I exit using Escape, it is going to stop. I don't htink I will be able to save the report if any as I am using DVD. By looking at this do you think a Memory replacement is required and a re-installation of Windows? Or please let me know the next steps.

20180207_120838 - 1.jpg
 
Unfortunately that's what I suspected and this confirms it. At least one of the sticks of RAM (if you have more than one) is faulty. The priority is replacing the bad RAM. Make sure you run the test and have it come out clean before proceeding.

Once you have good RAM you can either wipe and reload or you may try to do a Windows 10 repair by using the Media Creation Tool (instructions below). Your choice.

1. Download the Media Creation Tool to your desktop. Go ahead and run this. Note: Click the Download tool now button when you are at this link.
2. Accept the license agreement
3. Keep the default which is to Upgrade your PC and click Next.
4. Go ahead and run this through and let me know when complete.

Doing it this way will keep all your data and programs intact. As always though, make sure you have a backup of any critical data in case something unexpected happens.
 
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