@Enthousiast 19043.962 update (which installs fine) has serious bug causing BSOD with Bad Pool Caller error on my system. Lucky I've uninstalled it and reverted to 19043.928 which works fine. Is there anyone experiencing same issues ?
Right. After applying this to my chopped Education, .928 installed perfectly fine. I ran disk cleanup and deleted the Windows Updates category(about 4GB). Now I tried dism /add-package-ing the .962.cab and it threw the same error I had previously fixed. I'm gonna test installing .962.cab on a chopped Pro in VM, see if it makes any difference(removed components via msmg toolkit). Edit: The chopped Pro .928(w10ui cleanup+resetbase) in a virtualbox updated to .962 just fine.
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?
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
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.