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

BrianInEngland · 31 Aug 2019

HRPuffnstuff said:

Well now I'm resorting to performing an in place upgrade using the MCT in hopes that I can get around the update error that some many of us seem to be experiencing. If that doesn't work I'll probably just do the clean install thing like I did with my desktop and start over again.

The MCT in-place upgrade method worked for me, now on version 18362.329

HRPuffnstuff · 31 Aug 2019

RK1997 said:

Download the ISO using MCT and use it whenever you want.

Right now its just easier to allow the MCT to perform the action. Once the fall update comes out I'll update my ISO's to match.

krzemien · 31 Aug 2019

Right, I am ploughing through this 0xE0000100 nonsense on another forum (Sysnative Forums) and am seemingly getting somewhere.

It currently looks like late July non-security CU somehow managed to break xboxgip.inf file - the one I've got on my PC:

upon closer inspection is empty. Doh!

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'(e000 0100)
! 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
(...)

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?

It should be here and its date should be Aug '19:

C:\WINDOWS\System32\DriverStore\FileRepository\xboxgip.inf_amd64_4d1ee4a1e5fb471e\xboxgip.inf

UPDATE: Just got it.

HRPuffnstuff · 31 Aug 2019

Using the MCT put my laptop on 329 without issue.

Greythorne II · 31 Aug 2019

Update KB4512941: What’s the problem?
Everyone should read about Günter Born's full description and workaround here.

Born's Tech and Windows World

bugreporter · 31 Aug 2019

If you have problems installing this update, run cmd as admin and type:
1) DISM /Online /Cleanup-Image /CheckHealth
2) DISM /Online /Cleanup-Image /ScanHealth
3) DISM /Online /Cleanup-Image /RestoreHealth
4) SFC /scannow
5) SFC /scannow
Wait until each operation completes, then reboot your PC and install this update. It worked for me.

HRPuffnstuff · 31 Aug 2019

None of those worked for me hence resorting to the MCT.

BrianInEngland · 31 Aug 2019

bugreporter said:

If you have problems installing this update, run cmd as admin and type:
1) DISM /Online /Cleanup-Image /CheckHealth
2) DISM /Online /Cleanup-Image /ScanHealth
3) DISM /Online /Cleanup-Image /RestoreHealth
4) SFC /scannow
5) SFC /scannow
Wait until each operation completes, then reboot your PC and install this update. It worked for me.

That didn't work for me, only an install using the ISO image worked

goatty2 · 31 Aug 2019

installed on my desktop and so far no problems

krzemien · 31 Aug 2019

Righto, I did manage to sort this out.

It suffices to say that I found that core Microsoft's components held within C:\WINDOWS\System32\DriverStore\FileRepository\ folders were miraculously found empty despite their size suggesting otherwise. I'm talking about 8 INF files in these folders:

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

These very components were without exception re-written when KB4505903 (released end of Jul '19) was installed on my PC on 27/07 and/or component clean-up that I ran not very much later on the same day.

For those interested in details - this is the thread on another forum:

Windows 10 - Updates since KB4512508 (Aug CU) end up with 0xe0000100 | Sysnative Forums

Please note that things do not break on their own - so this particular situation does not really look good at all (and it's not me whom I blame for this situation).

Based on that and what I read in this thread (and elsewhere) I will most likely skip KB4512941 altogether and await tried and tested (ha ha ha!) Sep CU.