[SOLVED] Windows 10 - Updates since KB4512508 (Aug CU) end up with 0xe0000100

[krzemien]

Morning All,

As per the subject line: Updates since KB4512508 (Aug CU) end up with 0xe0000100 on my PC. All other updates (Defender updates, .NET udates, updated service stack [KB4515530]) install fine.

See my rather unexpected journey evidenced in couple of posts in this thread here:

Cumulative Update KB4512508 Windows 10 v1903 build 18362.295 - Aug. 13

And now exercised for KB4512941 released only yesterday as well here:

Cumulative Update KB4512941 Windows 10 v1903 build 18362.329 - Aug. 30

To be clear: both CUs seem installing fine - whether via WU or manually - and then system starts working through them upon restart. But then progress does not go beyond 0% (normally reaches 30% or so and PC restarts to complete the rest of activities just prior to the next login screen), and after PC restarts there's a message saying that updates need to be rolled back.

DISM and SFC checks provide healthy results.

According to this:

Topic: Patch Lady – 1903 Error 0x80073701 @ AskWoody

This mechanism got broken with non-security CU late Jul - and I agree as I casually run component clean up after each CU installation and started seeing this problem mid-Aug.

One suggested solution is in-place upgrade, but this is not something I'm willing to do as I find such approach rather lazy...

So, any helpful takers?

I can happily live with this for few more weeks - I understand that Microsoft is aware - but this situation annoys me slightly now and I would like to get it fixed.

 

[Sysnative Windows Update]

Hello and welcome!

Let's see what we can do, please attempt the update again and attach CBS.log after it fails.

 

[krzemien]

Many thanks for your prompt response - and voilá! Please let me know what you find there.

The attempt starts from this line onwards:

2019-08-31 13:34:35, Info CBS TI: --- Initializing Trusted Installer ---

I was trying to debug it myself two weeks ago but gave up thinking that MS would fix it in the meantime. But I digress...

Also, I can see that Microsoft's telemetry is working hard on my PC - the contents and size of various snippets in /TEMP after each attempt is quite significant.

 

[Sysnative Windows Update]

Thank you. Please attach C:\Windows\Inf\setupapi.dev.log. It looks like a driver is giving you grief.

 

[krzemien]

Oh, really? Interesting? Which one is this?

And: Voilá (yet again)!

(I did see some dubious - in my eyes - references to XBox within CBS.log before but decided not to pursue these myself)

 

[Sysnative Windows Update]

Apparently a ton of them...

Please open Command Prompt as Admin and copy paste the following command into the window:

Dism /online /Get-Drivers

 

[krzemien]

Yes, I'm looking at this now myself as well - and obviously it's not right. And as far as I can say all of these references seem to be Microsoft's ones. Interesting.

In either case, please see attached.

 

[krzemien]

For what it's worth - and am not jumping to any premature conclusions here - this is how it pans out on my PC:

 

[krzemien]

And looking at it closer now it seems that xboxgip.inf is empty - how's that?

Attached for posterity.

So: anybody has the latest xboxgip.inf (i.e from CU Aug '19 onwards) that they could share? I can see that the one within original Windows 10 release 1903 install.esd resides in different folder (xboxgip.inf_amd64_72135572843ef193 then, as opposed to xboxgip.inf_amd64_4d1ee4a1e5fb471e now)

 

[Sysnative Windows Update]

Is it just that one or everything? If everything, you are going to have to do a Repair Install.

 

[krzemien]

Well, according to setupapi.dev.log buck stops @ xboxgip.inf file:

(...)
sto: {Stage Driver Package: C:\WINDOWS\WinSxS\amd64_dual_dc1-controller.inf_31bf3856ad364e35_10.0.18362.1_none_a1a98497a30a3d39\dc1-controller.inf} 18:39:56.983
! inf: Unable to load INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf'(e0000100)
! inf: Error 0xe0000100: The style of the INF is different than what was requested.
!!! inf: Failed to include INF file "xboxgip.inf" with error on line 0. Error = 0xE0000100
!!! sto: Failed to retrieve driver package copy files. Error = 0xE0000100
!!! sto: Failed to get driver package copy files. Error = 0xE0000100, Filename = C:\WINDOWS\WinSxS\amd64_dual_dc1-controller.inf_31bf3856ad364e35_10.0.18362.1_none_a1a98497a30a3d39\dc1-controller.inf
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000100
sto: {Stage Driver Package: exit(0xe0000100)} 18:39:56.999
!!! sto: Failed to stage all driver updates. Error = 0xE0000100
(...)

And 0xE0000100 is what I witness in Windows Update.

Definitely worth trying to replace it with the correct, valid one. So, anybody can send me one please before I am forced to try to unpack it from latest CU MSU files?

 

[Sysnative Windows Update]

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.

 

[krzemien]

Most kind of you, there we are:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-31 18:11:30.994
Microsoft Windows 10 Build 18362 - amd64
Using .zip script file at C:\Users\xxxxxx\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\devauthe.sys
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.sys

Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\devauthe.sys to C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\devauthe.sys.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf to C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.sys to C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.sys.

Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\devauthe.sys
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\devauthe.sys
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.sys
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.sys
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2019-08-31 18:11:31.713
Script hash: 72Oe7wz5c5Shk7ZrQpwA8abWG4M6Ws2oiw2VBmU7WTA=
----------------------EOF-----------------------

The funny thing is that there's literally no difference between old and new xboxgip.inf file, except its date / driver version:




I shall retry the CU now and will keep you posted.

 

[krzemien]

Would have been too easy, eh?

This has worked - progress moved to 1% - but we have another one:

(...)
sto: {Stage Driver Package: C:\WINDOWS\WinSxS\amd64_product-onecore__du..etooth_a2dp_src.inf_31bf3856ad364e35_10.0.18362.1_none_e3d7870f1597636f\microsoft_bluetooth_a2dp_src.inf} 18:26:20.329
! inf: Unable to load INF: 'C:\WINDOWS\System32\DriverStore\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf'(e0000100)
! inf: Error 0xe0000100: The style of the INF is different than what was requested.
!!! inf: Failed to include INF file "microsoft_bluetooth_a2dp.inf" with error on line 0. Error = 0xE0000100
!!! sto: Failed to retrieve driver package copy files. Error = 0xE0000100
!!! sto: Failed to get driver package copy files. Error = 0xE0000100, Filename = C:\WINDOWS\WinSxS\amd64_product-onecore__du..etooth_a2dp_src.inf_31bf3856ad364e35_10.0.18362.1_none_e3d7870f1597636f\microsoft_bluetooth_a2dp_src.inf
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000100
sto: {Stage Driver Package: exit(0xe0000100)} 18:26:20.345
!!! sto: Failed to stage all driver updates. Error = 0xE0000100
(...)

And microsoft_bluetooth_a2dp.inf is empty as well, of course. Doh!

Care to supply this one as well?

Just checked other folders from the same CU and all appropriate INF files for them are empty!




Talk about quality work at Microsoft!

So, care to supply the whole lot?

 

[Sysnative Windows Update]

Like I said, due to the amount of files, I think the only plausible way to fix this is to perform an in-place upgrade. You may want to test the HDD while you are at it, becuase something must have caused this in the first place.

 

[krzemien]

I'm not a rookie and I know my PC. It's faulty KB4505903 with the above empty files and subsequent component cleanup that got rid of the original ones - that messed it all up.

It's literally these 5 INF files that I need here from the above folders - I don't need device drivers etc.. as they are fine.

hidspi_km.inf
wvid.inf
acpi.inf
cpu.inf
microsoft_bluetooth_a2dp.inf

I have found them all compressed within Windows10.0-KB4512941-x64_PSFX.cab in the meantime but have not discovered how to unscramble them yet.

I'm really not willing doing in-place upgrade and would like avoid doing it whenever possible...

Naturally there's a good chance that something else got broken as well elsewhere because of KB4505903 - but then I would probably give up and consider my options carefully.

So, are you willing to supply them?

 

[Sysnative Windows Update]

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.

 

[krzemien]

Merci beaucoup!

This time I decided to play it safe and modified SFCFix.zip contents to only include above-mentioned INF files - and corrected the drop-folder for ACPI either (it's changed since mid-Aug to acpi.inf_amd64_2e424f0a6091af4a).

The result is as follows:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-31 19:53:59.372
Microsoft Windows 10 Build 18362 - amd64
Using .zip script file at C:\Users\tadeu\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\wvid.inf_amd64_4bcb2d3f596b0da9\wvid.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\hidspi_km.inf_amd64_d3c2f8bba0f1f458\hidspi_km.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\cpu.inf_amd64_fd11a8393f2b7eca\cpu.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository\acpi.inf_amd64_07ffb14eec474691\acpi.inf
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository



Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\wvid.inf_amd64_4bcb2d3f596b0da9\wvid.inf to C:\WINDOWS\System32\DriverStore\FileRepository\wvid.inf_amd64_4bcb2d3f596b0da9\wvid.inf.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf to C:\WINDOWS\System32\DriverStore\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\hidspi_km.inf_amd64_d3c2f8bba0f1f458\hidspi_km.inf to C:\WINDOWS\System32\DriverStore\FileRepository\hidspi_km.inf_amd64_d3c2f8bba0f1f458\hidspi_km.inf.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\cpu.inf_amd64_fd11a8393f2b7eca\cpu.inf to C:\WINDOWS\System32\DriverStore\FileRepository\cpu.inf_amd64_fd11a8393f2b7eca\cpu.inf.
Successfully copied file C:\Users\tadeu\AppData\Local\niemiro\Archive\FileRepository\acpi.inf_amd64_07ffb14eec474691\acpi.inf to C:\WINDOWS\System32\DriverStore\FileRepository\acpi.inf_amd64_07ffb14eec474691\acpi.inf.

Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\wvid.inf_amd64_4bcb2d3f596b0da9\wvid.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\wvid.inf_amd64_4bcb2d3f596b0da9\wvid.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\microsoft_bluetooth_a2dp.inf_amd64_cfc63958702d730f\microsoft_bluetooth_a2dp.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\hidspi_km.inf_amd64_d3c2f8bba0f1f458\hidspi_km.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\hidspi_km.inf_amd64_d3c2f8bba0f1f458\hidspi_km.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\cpu.inf_amd64_fd11a8393f2b7eca\cpu.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\cpu.inf_amd64_fd11a8393f2b7eca\cpu.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository\acpi.inf_amd64_07ffb14eec474691\acpi.inf
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository\acpi.inf_amd64_07ffb14eec474691\acpi.inf
Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2019-08-31 19:55:25.738
Script hash: bK7Pjs7joNCSu+mVysWYzs7yNuV+GuZSgQCOVzG4o+c=
----------------------EOF-----------------------

As before/always, I just ran DISM/SFC suite now:

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.267

No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>

C:\WINDOWS\system32>sfc /verifyonly

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.267

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>

And subsequently will re-attempt to install KB4512508 (KB4512941 seems messy apparently from what I read) - after restart. I hopefully will be back soon ;-)

 

[krzemien]

Apologies for rather lengthy hiatus.

I'm back and all is well - and now did manage to get KB4512508 installed either:

C:\WINDOWS\system32>sfc /verifyonly

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.295

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>

Alas! Just before I ran the installer, I thought it prudent to check once again C:\WINDOWS\System32\DriverStore\FileRepository\ folders just in case something else is amiss - and there was. What I have not spotted before were two additional folders whose INF files exhibited the same issue (i.e. were empty despite their size suggesting otherwise):



Their dates were changed though to yesterday/today as they have been modified by my re-installation attempts.

I decided to take a risk and got these files off original Windows 10 release 1903 install.esd file this time - bearing in mind that their file version had to be manually upped to 10.0.18362.267 as well (in line with the very first xboxgip.inf file).

So all is definitely well and I thank you very much for your help and understanding.

As to the reasons why there was a problem: I am fairly confident that my PC is absolutely fine hardware- and software-wise. It's definitely not a coincidence that only core Microsoft's INFs were impacted - as I wrote earlier the culprit is faulty KB4505903 (released end of Jul '19) and subsequent my casual but otherwise non-threatning component clean-up that unexpectedly messed it all up.

One really wonders what's the use of DISM/SFC combo if they report that all is well - when it's clearly not.

One also wonders if there's another tool that allows finding such discrepancies somehow? Or perhaps there's no cure for Microsoft's very random but more and more frequent quality shortcomings?

One thinks about the joys going forward where two simultaneous releases (H1 & H2) are to be serviced by the same CU (or so I hear?).

One lastly wonders how may users, once they become aware that there is an issue that prevents their PC from being updated (and kept secure), will have to resort to either manual tweaks and modifications as per the above or - more likely - to complete OS reinstallation, conveniently known as in-place upgrade.


Therefore based on that experience I strongly recommend deferring from installation of any non-security CUs that Microsoft is pushing in haste, and without any comprehensive tests. Testament to this are numerous threads describing latest bunch of issues experienced by those who agreed to have it installed on their PCs.

Thanks again for your support, most appreciated.

 

[Sysnative Windows Update]

SFC and DISM do an excellent job at scanning their respective areas. And driver issues are reported in separate logs. While it is true that updates did have their fair share of issues lately, I would strongly disagree with you that one should not install them as they patch severe vulnerabilities against exploits that can use them to their malicious purposes.

The new system of servicing updates has been introduced in Fall last year and things have definitely improved since. Unfortunately, some people have to resort to OS reinstalls due to their issue being too extensive to fix, but we can resolve most of the issues.

I'm glad to hear that your issu seems to have been resolved.