[SOLVED] [Win10v1703b15063 x64] Windows update problem

BrianDrab said:
OK. Unfortunately because the hive is corrupt beyond repair there are only two options and one is a gamble.

1. Best and safest is to reload your machine from scratch. So this includes backing up all your critical information such as documents, pictures, etc. Ensuring you have all of your media to re-install programs, all your license keys, etc. Wiping and reloading your machine and installing everything back on.

2. I can provide you a COMPONENTS hive from another working machine and we can put it on yours, reboot and then try the Windows 10 repair over the top. I've never done this before and it's likely to fail but worth a shot if you are completely against doing a reload of your system.

If you happen to have a System Image backup of your machine stored somewhere, we can retrieve the hive from there and will have a much better chance of success.

Let me know what you decide.
Click to expand...

I do in fact have a WindowsImageBackup, which contains amongst other things a 224 GB .vhdx "Hard Disk Image" file; the same directory also contains a ***_Components.xml file, in case that's of any use (it's about 15 KB). Unfortunately the image isn't that recent (it's from Jan 31 of this year). I also have a Dell recovery USB, which contains DellEFI.wim and EFI.wim, both dating from Dec 2015. I have, of course, backups of my User account (the last incremental one with Comodo from this morning). If the image (or recovery USB) can be used to create a hive good enough to run the in-place Windows Update, that would be best; if not, I guess I'll bite the bullet & do a re-install (is it really better to wipe the disk & re-install as in #1 above as opposed to just re-installing the system?), & deal with whatever software license issues crop up later.

Thanks,

D
 
It's worth a shot for sure! This may work. Mount your .vhdx file and grab both the following files from the mounted file and put then in your directory of your current machine.
c:\windows\system32\config\COMPONENTS
c:\windows\system32\config\DRIVERS

is it really better to wipe the disk & re-install as in #1 above as opposed to just re-installing the system?),
Click to expand...
It's preference really. Either would work fine.
 
BrianDrab said:
Mount your .vhdx file and grab both the following files from the mounted file and put then in your directory of your current machine.
c:\windows\system32\config\COMPONENTS
c:\windows\system32\config\DRIVERS
Click to expand...

Thanks. I did that (though via DiskManagement & not directly), started with a fresh SoftwareDistribution and $Windows.~BT, and tried again; alas, the Windows Update Install still fails at 38%. As before, the log files are attached,

C:\$Windows.~BT\Sources\Rollback\setupact.log => absent
C:\$Windows.~BT\Sources\panther\setupact.log => included as 'setupact.log'
C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log => absent
C:\Windows\setupapi.log => absent
C:\Windows\inf\setupapi.dev.log => included as 'setupapi.dev.log' (though it doesn't seem to have changed)
C:\Windows\logs\cbs\cbs.log => included as 'cbs.log'

The Update (or repeated rebooting) does seem to have done something to COMPONENTS and DRIVERS, which can be inspected at Download System32 files.zip from Sendspace.com - send big files the easy way. Any suggestions?

Thanks,

D
 

Attachments

Can you tell me exactly the process that happened. This will tell me where to look for the issue.
1. Does the failure happen before the 1st reboot?
2. After the 1st reboot?
3. After the 2nd reboot?

Any details on the upgrade process will lead me to the correct log.
 
BrianDrab said:
Can you tell me exactly the process that happened. This will tell me where to look for the issue.
1. Does the failure happen before the 1st reboot?
2. After the 1st reboot?
3. After the 2nd reboot?

Any details on the upgrade process will lead me to the correct log.
Click to expand...

Yes, it's before the first reboot, at 38%.

Thanks,

D
 
Please do the following so I can get more info.

DISM
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 /Get-Drivers

  3. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  4. Paste (Ctrl+V) it into your next post please.
 
BrianDrab said:
Please do the following so I can get more info.

DISM
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 /Get-Drivers

  3. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  4. Paste (Ctrl+V) it into your next post please.
Click to expand...

The window:
----------------------------
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>Dism /Online /Get-Drivers


Deployment Image Servicing and Management tool
Version: 10.0.15063.0


Image Version: 10.0.15063.0


Obtaining list of 3rd party drivers from the driver store...




Error: 126


An error occurred. The driver store for the image could not be opened.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log


C:\WINDOWS\system32>
----------------------------
The dism.log file is attached.

Thanks,

D
 

Attachments

OK, please do the following.

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 Dism /Online /Get-Drivers just like you have in the past.
3. Stop Process Monitor as soon as DISM 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.
 
BrianDrab said:
OK, please do the following.

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 Dism /Online /Get-Drivers just like you have in the past.
3. Stop Process Monitor as soon as DISM 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.
Click to expand...

The files are a bit big, so here's a SendSpace link to a folder containing both:Download Process Logs.zip from Sendspace.com - send big files the easy way

Thanks,

D
 
Thanks. I see the issue.

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, 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
 

Attachments

BrianDrab said:
Thanks. I see the issue.

View attachment 29127

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, 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
Click to expand...

Thanks. Here's the contents of SFCFix.txt (after one reboot, which included the appearance of something called TrueKey on my login sceen),
-----------------------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-10-15 20:12:10.920
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Kosower\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsCore.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\dpx.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drupdate.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\msdelta.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smiengine.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smipi.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll
Successfully took permissions for file or folder C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wdscore.dll


Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\amd64_installed to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\amd64_installed.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsCore.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsMsg.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsMsg.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cmiadapter.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cmiadapter.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cmiaisupport.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\cmiaisupport.dll.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\dpx.dll is in use and must be replaced over a reboot.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drupdate.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drvstore.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drvstore.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\GlobalInstallOrder.xml to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\GlobalInstallOrder.xml.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\msdelta.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\mspatcha.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\mspatcha.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\poqexec.exe to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\poqexec.exe.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smiengine.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smiengine.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smipi.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smipi.dll.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiFileFetcher.exe to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiFileFetcher.exe.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\WcmTypes.xsd to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\WcmTypes.xsd.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll is in use and must be replaced over a reboot.
The file \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wdscore.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\Kosower\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wrpint.dll to C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wrpint.dll.


Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsCore.dll
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\dpx.dll
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drupdate.dll
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\msdelta.dll
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wdscore.dll


Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smiengine.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smiengine.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smipi.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\smipi.dll
PowerCopy:: directive completed successfully.








Reboot:: directive completed successfully.








PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.








PostRebootRestorePermissions::
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsCore.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\CbsCore.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\dpx.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\dpx.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drupdate.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\drupdate.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\msdelta.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\msdelta.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wcp.dll
Successfully restored ownership for C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wdscore.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\wdscore.dll
PostRebootRestorePermissions:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2017-10-15 20:19:50.668
----------------------EOF----------------------------------------------------------

Thanks,

D
 
OK, good. Double-click your Windows.iso from the Media Creation Tool and attempt to install Windows 10 right over the top again.
 
BrianDrab said:
OK, good. Double-click your Windows.iso from the Media Creation Tool and attempt to install Windows 10 right over the top again.
Click to expand...

This time it (finally) worked! Thanks for your help in this long process. Is there anything I should do to check that the installation is in fact corruption-free?

Thanks,

D
 
Excellent news and no problem at all. Please ensure all windows updates are installed and then do the following.

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:
Excellent news and no problem at all. Please ensure all windows updates are installed and then do the following.

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

Here it is.

Thanks,

D
 

Attachments

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