Guys and Gals,

Running into an issue with the in-place upgrade of windows 10.  My client
utilizes a custom WinRE image in their Windows 10 bare metal deployments.
Whenever they in-place upgrade windows 10, they lose their custom recovery
environment.  I get why this is happening, because Windows 10 stages a new
WinRE which is used for the upgrade itself, what I need to know, is if
there is anyway to avoid this behavior?

Anything to do about it other than use post install tasks to put back the
custom WinRE environment back?

Just wondering what others are doing about this behavior?

Please and thank you.


Reply via email to