search

hfiref0x / UACME

Defeating Windows User Account Control
BSD 2-Clause "Simplified" License
6.09k stars 1.3k forks source link

63,65-68 may have been fixed? #145

Closed Mosney closed 1 year ago

Mosney commented 1 year ago 
Windows 11 Pro
22H2 22621.1848

I just try every method still cotained in 3.6.4, found some methods look unwork as expected(pop up a CMD window).

  1. uac request by msschedexe.exe then a terminal-liked windows titled C:\WINDOWS\system32\SecureBootEncodeUEFI.exe flash in&out, but no administrator CMD show.

65,66,67,68 have no request at all, Maybe they've been fixed?

hfiref0x commented 1 year ago

65-68 are protocol hijacks, more possible that code responsible for UserAssocSet is not compatible with win11 changes since this code wasn't updated from nov 2021.

hfiref0x commented 1 year ago

I have:

1) installed this pack of crap -> 22621.1848.230608-1957.NI_RELEASE_SVC_PROD1_CLIENTMULTI_X64FRE_EN-US.ISO; 2) updated shell32.dll signature scan for UserAssocSet for 22621 (as signature was indeed incompatible with this OS version); 3) removed WinDefend to avoid system heavy load and possible interactions through it schizophrenic behavior rules; 4) run 63, 65, 66, 67, 68, screenshots below (each run with reverting OS state to fresh installed, forgot to mention). 63 65 66 67 68

As you see conceptually nothing changed, all of them works perfectly.

The reason why 63 maybe failing for you is that it is very resource consuming as it involves cleaning native image cache which may trigger multiple other things we can't predict.

Mosney commented 1 year ago

Thanks for test