[EX-100 - v2.1.0.0] [RS5 Build 17763.134] Update not working

Hey,
after using this configuration

[You must be registered and logged in to see this link.]

with Windows 10 Build 17763.134 and WinReducer EX-100 - v2.1.0.0,
I noticed that neither update KB4469342 (error 0x800f0982) nor update KB4467708 (error 0x800736b3) can be installed, neither by Windows Update Service in the settings nor manually by using the *.msu file released by Microsoft.
The updates can be installed though if using the image that has not been modified by WinReducer yet.
The Eventmanager gives the fopllowing log:


Let me know if you need any additional informations,
everything else works perfectly.
Greetings,
Phil

Hi I tested your .wccf removing all ModernUI disabling and it works for me
Cheers

I have the same problem, posted in another thread.. Let's hope @winterstorm2050 can sort it out!

@Jpm
First of all thank you for testing.
I am really curious to know which Windows version you did use, because I just testet it with exactly the *.wccf I have loaded up (mainly to make sure that I have not uploaded the wrong file because I was really tired that time, which is the reason why I did not find the thread of @carlese, sorry for that), and the result was exactly the same, not only with one but with multiple VMs.
To give some more information, I use the German Business *.iso and testet especially Pro, Enterprise and Enterprise for Remotesessions, build version is 17763.134, and I can definitely confirm that this problem does not appear with the unmodified *.iso.
Again, the system itself works, but the update does not in terms of not installing some kind of updates, as far I can tell the cumulative ones.

If there is anything I can do to provide additional helpful information I am happy to do so.

Hi,
My test was starting 17763.1  and using Winreducer to integrate .134 update with a Win10 Pro
If I keep the moderUI removal the integration fails winreducer does not say anything but the integration is not done (still 17763.1)
using this failed .iso leads Failure to Windows Update. I was thinking it was the same problem as yours.

I will assume in tour cas the MoernUI removal produce the error

Cheers

Hello guys

I've worked on sysprep bugs ... so now I'm investigating this updates troubles.

Could you please confirm if that only happens in RS5 ? Thanks.

I wish you to have a great day !

I used latest 1809 for my tests.. Never had problems with 1803 I think..

I justredid with RS4 and I confirm no problem modernUI removal is OK

Hey Jpm

OK, thanks ... I confirm the bug with RS5 ... and I was able to reproduce this RS5 updates bug !

Unless it is due to the bug
it would be good to have a log when DISM integration failed
Cheers

@winterstorm2050
I can confirm that this bug appears only with RS5 (at least it does not appear when applying my config to RS4).
The build I used was 17134.1 and it updated without problems to 17134.407.

winterstorm2050 wrote:

Hey Jpm

OK, thanks ... I confirm the bug with RS5 ... and I was able to reproduce this RS5 updates bug !

Please if you find a fix don't wait till next week.. My PC needs a forma, I'm waiting for your release to do it

Hello guys

Just to inform you that I'm close to find a solution as MS changed the updates integration system .... so since RS5, they are using a worst solution in term of Windows size ... but I solved the problem with all the errors that "Dr Phil Perlmutter" described ... for the moment I'm able to deployed a WinReduced ISO with a fully functional Windows Updates, in "Settings". Unfortunately, this will have a size impact (due to MS changes) and I'm not sure that will be ready tomorrow (I need to do many more tests to confirm this current solution as a working fix) ... but as usual, I will let you know soon

I wish you to have great day !

if you can make it it will be very good because this error holds me (and other people i believe) from updating to RS5 build. if not we will wait the next build. Thanks winter

Hello guys,

I confirm that I need to cancel the build which should be released today, so instead it will be released on Sunday 16 December [All Users]

So, in RS5 MS changed completely the updates integration ... so it needs many files in the winsxs folder, at least for the moment (which were not needed in previous version) ... this is why I mentioned earlier that the final size will be impacted !

Of course, I need to modify the removing engine to support this new cumulative update system ... I made several tests to verify and the cumulative updates has been integrating using "Settings" (Immersive CPL) with a WinReduced ISO.

I will keep you up to date on Sunday

Thanks guys.

Cant wait for the new build

@winterstorm2050
Thank you for keeping us informed.
Seems that Microsoft changed a lot this build, for example language interface only being available as .appx.
Also, language features on demand are somehow impossible to install for me and to be honest I have given up.
Let me know if you need any help in terms of testing, I am busy with test VMs this week anyway so having a few more simultaneously is not a big thing for me.

Hello all,

I have the same problem like Phil, but with Windows RS4 Build 17134. Everytime when try to I install cumulative update (currently KB4480979) it fails with error 0x800736b3. The updates can be installed though if using the Image that has not been modified by WinReducer yet.
I als tried it with WinReducer v2.0.9.0 but with the same result.

I don't know if the cause of the problem is the same as described here in the thread or if it has another cause.

Here's the wccf file which i used [You must be registered and logged in to see this link.]

Hello guys

I will release very soon an update with a fix, but it's not stable enough yet (few components are still breaking CU) ... the fix should be valid for all Windows 10 RSx builds (I'm still testing them)

I wish you to have great day !

Hello guys

I finally successfully fixed the Windows Updates slipstreaming process (with EX-100 v2.1.1.0 [ALL]), I made various tests with various Windows Versions (from RS1 to RS5) and I didn't have issues before or after installation with Windows Updates integration.

Of course, this fix changes a lot of things, especially the "Removing Engine" (updated to v4.00) which needed to be partially reworked to ensure a better Windows Updates integration (before or after installation), and it's the reason why this newest version has been so long to be released !

As I mentioned, in a previous post in this thread, MS changed the updates files detection, which means that more files, in the "WinSxS", needs to be kept (compared to the previous MS updates detection system) ... and there is an huge impact in the final size ... but in the other hand, Windows Updates integration will work (before and after installation).

This fix also changes the procedure to create a fully functional ISO with Windows Updates :
1 - You must use : "Protect Windows Updates" component (put its status to "ON")
2 - Select all the components you want to remove
3 - You can use "System - Integrate Windows Updates" component ... ONLY if you will not remove more components in this ISO !
4 - Apply your changes

P.S. 1 : For point 3, the explanation is : if you remove a component from an already updated ISO, Windows Updates will be broken (in other words, you must integrate the cumulative update after you are sure you removed all the components you do not need) ... I'm investigating this issue, but it will take time ... and I really hope that MS will not change the detection system with every Major Windows 10 upgrades

P.S. 2 : Of course, this procedure is only valid if you need Windows Updates (I mean after installation using "Settings" app functionalities) ... in all other cases (no need to use "Settings" app or you remove "Windows Updates" completely) you can continue like you always used to !

P.S. 3 : "EX-100 - v2.1.1.0 [ALL]" will be released on Friday 17 January 2019

Thank you winterstorm2050 for this detailed support and information.
Can you confirm in terms of Windows 10 RS5 update, I should start with build 17763.1 and then go with the following procedure:
Windows 10 17763.1 --> WinReducer process --> applying Language Packs --> Applying updates ?

I really hope that Microsoft will more stick to a line in the future with Windows 10, it is actually the only thing I do dislike a bit about it.

Hello

You are much welcome

Yes, I confirm your procedure will work (I haven't tested language packs integration, but there is no reason to do not work like this).

I wish you to have a great day !

Hi guys. Winter can you tell us in how many hours you will release the new build;

Hello

It will be released as usual : 20H00 (Paris Time) ... so for me in 1H15

I just finalized also the EX-100 January 2019 Updates Catalog ... which will be released at the same time ... so now I'm going to eat a little and I will release everything as mentioned

Cheers.

I cant wait to make new isos and try the new build. Any news for the laptop presets;

The laptop preset will be available next week with VIP builds (Friday 25 January 2019) ... and it will be available the following Monday for all users

Will the process that Dr Phil Perlmutter described work if you start with 17763.107 or i need to download 17763.1;

For sure with 17763.1, it will work ... if you follow the procedure I described in this post :
[You must be registered and logged in to see this link.]

For 17763.107, I just tried and it worked correctly, with the same procedure ... so for the moment, all clean and official Windows ISO from MS are supported as a basis for all your tests

I'm investigating the possibility to solve the windows update issue with an ISO updated with EX-100 ... the issue is : update an official iso -> save changes -> re-open it -> modify it + updates slipstreaming -> save changes = windows updates error after installation.

winterstorm2050 wrote:

Hello guys

As I mentioned, in a previous post in this thread, MS changed the updates files detection, which means that more files, in the "WinSxS", needs to be kept (compared to the previous MS updates detection system) ... and there is an huge impact in the final size ... but in the other hand, Windows Updates integration will work (before and after installation).

Updates files detection changed only to RS5 or also to older builds? Has the new removal engine also been changed to older builds? In RS4 for example will I have an increase in image size with the new removal engine?

Hello AeonX

Yes, the fix, for the updates detection, is for all Windows 10 Versions (TH1 and RSx) ... so you have two choices, at least for the moment :
- Enable "Presets - Protect Windows Updates" to keep Windows Updates functionality = increased ISO size (compared to previous period)
- Disable "Presets - Protect Windows Updates" = Windows Updates functionality will not be protected and may not work due to MS changes ... but you can slipstream all updates before installation = same ISO size (compared to previous period)

I wish you to have a great day !