You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 16, 2025. It is now read-only.
Images generated by UUPMC will strangely boot up with conversion date though virtual machine's date is locked. Old flight-signed builds will be completely uninstallable. Other UUP conversion programs do not have this behavior.
I guess this is related to some image manipulation process.
Edit: only WinRE is affected
The text was updated successfully, but these errors were encountered:
This sounds very odd given winre.wim is the one thing that does not get touched by the conversion process. Are you sure this is an issue with the tool? Do official isos available from microsoft reproduce such behavior?
Edit: also how does WinRE prevent installation of old flight signed compiles?
Sorry for bad wording, I mean the setup RE (boot.wim).
I noticed some packages were removed during boot.wim generation and I guess that would be a problem. Other tools (like abbodi1406's uup-converter) use a relatively dumb method to generate boot.wim so free of this issue.
Setup will boot up with the modification date, ignoring BIOS date lock. If not setting date with command prompt in setup RE manually the timebomb will be triggered.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Images generated by UUPMC will strangely boot up with conversion date though virtual machine's date is locked. Old flight-signed builds will be completely uninstallable. Other UUP conversion programs do not have this behavior.
I guess this is related to some image manipulation process.
Edit: only WinRE is affected
The text was updated successfully, but these errors were encountered: