valinet / ExplorerPatcher

This project aims to enhance the working environment on Windows
GNU General Public License v2.0
24.82k stars 1.05k forks source link

ExplorerPatcher crashes when I open a folder #2041

Closed igroglaz closed 1 year ago

igroglaz commented 1 year ago

funchook create 1 Running on Windows 11, OS Build 10.0.22621.2134. Loaded symbols Setup ntdll functions done Setup user32 functions done Patched taskbar transparency in newer OS builds Setup explorer functions done Setup uxtheme functions done Setup twinui.pcshell functions done Setup combase functions done Setup twinui functions done Setup stobject functions done Setup bthprops functions done Setup pnidui functions done Setup shell32 functions done Setup explorerframe functions done Setup windows.storage functions done [IME] Context menu patch status: 1 Setup inputswitch functions done Setup windowsudk.shellcommon functions done Setup peopleband functions done Installed hooks. Play startup sound thread... Signal shell ready... Started "Signal shell ready" thread. Started "Open Start on current monitor" thread. Open Start on monitor thread EP Service Window thread Initialized taskbar centering module. [Positioning] Added settings for monitor 0000000000010001 : 0 Progman: 918120 Progman hook: 148767653 Signal shell ready. Setup sndvolsso functions done Ended "Signal shell ready" thread. 0 0 [sws] Wallpaper RECT 0 0 1920 1080 [sws] Refreshing theme: 0 [sws] Refreshing theme: 0 [sws] Refreshing theme: 0 Started "Play startup sound" thread. Ended "Play startup sound" thread. [Updates] Starting daemon. 10000 46000000 0 46000000 Error in sub_1800135EC on RoGetActivationFactory.

Previously (before past 2-3 updates of ExplorerPatcher) I didn't had such problem.

pyrates999 commented 1 year ago

duplicate of: https://github.com/valinet/ExplorerPatcher/issues/1942

Please close this

work around: In ExplorerPatcher Properties, Go to File Explorer > and set Management Interface to Windows 10 instead of Windows 11.

Amrsatrio commented 1 year ago

Please download the newest version and see if this issue still persists. If it's gone, please close this issue.