Windows 10 Hotfix Repository

You need to login to view this posts content.

 

It should, but i can't find it on uup (there is no feature update for .962 available atm)

 

Naturally

 

Can someone who tested this before please answer this.
When installing a new image via ISO created from UUP, winre.wim installed in the system which is the Recovery image gets updated by SSU and Safe OS Dynamic Update.
However, following installation, winre.wim never gets updated using Windows Update.
Is this an issue in the sense that the Recovery image somehow gets out of date in time following successive LCUs and SSUs?

 

On MVS ISOs too:

 

You need to login to view this posts content.

 

Even if you updated winre.wim with LCU, after OS is installed and winre.wim is registered, it will not be updated further
it's just how Recovery Environment works, i.e. emergency

although, if winre.wim is accessable (e.g. "C:\Recovery\WindowsRE\winre.wim"), you can use Reagentc to disable it, update winre.wim, then re-enable it

 

Just for fun i've updated the winre.wim from that path (with the new du for safeos and ssu) and put it back in when using DaRT explorer from boot and it seems to work.

And now i really have to go offline

 

Why their version never match with the one inside LCU (

ELI5 Please

 

This means that there is not much point in installing Safe OS DU after installation and any other DU on an online image.
Is this correct?

 

Code:

Reagentc /info
Reagentc /disable

copy or move winre.wim to another location
mount it, add updates, unmount, export to new wim file (to reduce size)
move it back to registered location


Reagentc /enable

i actually never used it

Correct

 

I think the method presented by @abbodi1406 which involves reagentc off and on is cleaner in the sense that it resets the entry after winre.wim was updated.
However chances are that simple copy of the updated winre.wim in the old location overwriting the existing one would work as well.
In fact this seems to be what Microsoft suggests in the article for Windows 7 provided earlier.
The issue is now completely resolved.
Thank you @abbodi1406 and @Enthousiast for your participation and very useful input.

 

19042/3.962 Feature Update is available, including the new du for sources.

 

+1 Vote

 

You need to login to view this posts content.

 

The patch fixes the integration on official supported SKUs, not advised to run no longer supported SKUs, or you have to create an uptodate ISO and inplace/repair upgrade each time MSFT releases an update.

 

You need to login to view this posts content.

 

Maybe they rely on you to publish it.

 

You need to login to view this posts content.