[SOLVED] [Win10v1703b15063 x64] Windows update problem

D

DKosower

Contributor
Joined
Sep 23, 2017
Posts
26
Hello,

I'm trying to do a Windows 10 update to repair a system which has suffered corruption (probably due to a mangled update of Windows & Dell drivers, but I'm not sure). After much effort (and interaction with Dell & Microsoft technicians), I've managed to get a Windows ISO from Media Creation Tool that matches my system, & extracted it to a folder on my hard drive. When I try to run it (setup that is), the "Making sure your system is ready to install" phase is slow & shows lots of errors (starting with Failed DismGetDrivers), but what I notice is that when the install proper begins, the first couple of corresponding lines in the log file are,

2017-09-23 15:42:27, Error SP Failed to get driver packages from the online system. Error: 0x8007007E[gle=0x0000007a]
2017-09-23 15:42:29, Error SP Operation failed: Process Drivers for Migration. Error: 0x8007007E[gle=0x000000b7]

(The install ultimately fails abruptly without an error message and just a pop-up window announcing failure, at about 33%. Both Windows and McAfee virus checking are turned off; DISM /RestoreHealth previously failed with Error 14098; it's Windows 10, v 1703 build 15063.540) A 2016 thread had a similar report, and suggested [06-04-2016, 08:42 PM] rebuilding/replacing the drivers file in C:\Windows\System32\Config, but I don't what to do (or how). Can someone enlighten me?

Thanks,

D
 
Re: Windows update problem

Hi and welcome to Sysnative. Please do the following.

Navigate to c:\windows\system32\config and copy the DRIVERS file to your desktop. Then zip/attach this file.
 
Re: Windows update problem

Please copy your entire c:\windows\logs\cbs folder to your desktop and zip up and upload to a filesharing service such as SendSpace and provide the link. Thanks.
 
Thank you and yes the logs show all install activity. Please do the following.

Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to SendSpace and just provide the link here.
 
Your COMPONENTS hive is corrupt beyond repair. I suggest you try the following.

Since it's already corrupt, delete the file c:\windows\system32\config\COMPONENTS

Then double-click the Windows.iso and attempt to install Windows 10 right over the top. Let me know how it goes.
 
Thanks, Brian. I renamed components to components.bad-cor (in safe mode), rebooted & then tried running setup again (from a folder extracted from the ISO). The last try went a bit longer ultimately failed abruptly (at 38% this time). I noticed a new COMPONENTS got created, presumably a stub (8 KB vs the old 44.7 MB). Any suggestions?

Thanks,

D
 
Sure. Let's take a look at some logs. Please zip/attach the following (if they exist).

C:\$Windows.~BT\Sources\Rollback\setupact.log
C:\$Windows.~BT\Sources\panther\setupact.log
C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
C:\Windows\setupapi.log
C:\Windows\inf\setupapi.dev.log
 
C:\$Windows.~BT\Sources\Rollback\setupact.log => absent
C:\$Windows.~BT\Sources\panther\setupact.log => included as 'panther-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 inf-setupapi.dev.log

I also included Windows\setupact.log and Windows\setuperr.log (as Windows-setupact.log and Windows-setuperr.log respectively), in case they're of any use.

Thanks,

D
 

Attachments

I just want to confirm that you are NOT booting to the media and trying the install. You are booting into Windows normally and then running the setup from the ISO file correct?

If that is correct then go ahead and delete the c:\windows\system32\config\DRIVERS file and then attempt it again. Let me know the results.
 
BrianDrab said:
I just want to confirm that you are NOT booting to the media and trying the install. You are booting into Windows normally and then running the setup from the ISO file correct?

If that is correct then go ahead and delete the c:\windows\system32\config\DRIVERS file and then attempt it again. Let me know the results.
Click to expand...

I had tried once to boot from the installation media (& once from a recovery USB), only to discover that it wouldn't allow an update install. The failure I reported previously (and the current failure) to complete came from booting into normal mode & running setup.exe from a copy of the mounted ISO or directly from the mounted ISO. (The last time, I also started with fresh $Windows.~BT and SoftwareDistribution for good measure.) This time around, a stub drivers file got created, and the install seemed to spend a bit more time around 38%, but ultimately failed again. 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'

Thanks,

D
 

Attachments

Please do the following.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Step#2 - Reset Software Distribution Folder
Apparanly you are already familiar with doing this so please do.

Step#3 - Attempt the Windows 10 setup from the mounted ISO again.
In the event of a failure please provide me with the same logs as before in addition to the c:\windows\logs\cbs\cbs.log


Thank you.
 

Attachments

Thanks. The install failed again, at 38%. The log file folder contains,

Desktop\Fixlog.txt => included as 'fixlog.txt'
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'

Thanks,

D
 

Attachments

Please do the following.

Step#1 - FRST Scan
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also paste that along with the FRST.txt into your reply.
 
BrianDrab said:
Please do the following.

Step#1 - FRST Scan
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also paste that along with the FRST.txt into your reply.
Click to expand...

Here they are.

Thanks,

D
 

Attachments

OK, I see two options here. First can you tell me if there are any other Windows 10 machines that are very similar in the programs/updates, etc. that are installed on this one?
 
BrianDrab said:
OK, I see two options here. First can you tell me if there are any other Windows 10 machines that are very similar in the programs/updates, etc. that are installed on this one?
Click to expand...

Unfortunately not; my machine is very custom...

Thanks,

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