E2B v1.92f has a slightly different and easier implementation of the UtilMan hack now.
Steps 3 and 4 have been reversed and there is much less typing for the hacker!
Basically the process is now:
1. Boot to E2B Win 10 ISO and choose Hack Windows (UtilMan.exe).xml to patch the .exe files.
2. At Windows login screen press WIN+U and type 2 [ENTER] to make the ADMIN account.
Now play around as you like!
3. At Windows login screen, press WIN+U and type 3 [ENTER] to delete the ADMIN account.
4. Boot to E2B Win 10 ISO and choose UnHack Windows (restore UtilMan.exe).xml to unpatch the .exe files.
I have updated the previous blog post to describe the steps in more detail.
P.S. It seems MS have broken SFC now so it is unable to repair utilman.exe and sethc.exe! For the last 4 weeks or so, SFC has not been able to repair some files and complains about corrupt source files, i.e. it does not recognise the files in its own WinSXS folders - probably because they were not updated by the recent Windows updates - but hey, it only affects millions of people all over the world and Microsoft cannot possibly afford to validate it's own software or respond to bug reports!
Steps 3 and 4 have been reversed and there is much less typing for the hacker!
Basically the process is now:
1. Boot to E2B Win 10 ISO and choose Hack Windows (UtilMan.exe).xml to patch the .exe files.
2. At Windows login screen press WIN+U and type 2 [ENTER] to make the ADMIN account.
Now play around as you like!
3. At Windows login screen, press WIN+U and type 3 [ENTER] to delete the ADMIN account.
4. Boot to E2B Win 10 ISO and choose UnHack Windows (restore UtilMan.exe).xml to unpatch the .exe files.
I have updated the previous blog post to describe the steps in more detail.
P.S. It seems MS have broken SFC now so it is unable to repair utilman.exe and sethc.exe! For the last 4 weeks or so, SFC has not been able to repair some files and complains about corrupt source files, i.e. it does not recognise the files in its own WinSXS folders - probably because they were not updated by the recent Windows updates - but hey, it only affects millions of people all over the world and Microsoft cannot possibly afford to validate it's own software or respond to bug reports!
No comments:
Post a Comment