-
I know that work is being done to lessen EP's reliance on symbols. So, what is EP's current reliance on symbols? The reason I am asking is because I updated one of my Windows 11 computers today to build 22621.2428, and EP seems to be working just fine even though the console reports |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Symbol files seems to be used only during the initial installation of the EP. But after updated EP may not work properly due to missing Symbols for some functions. |
Beta Was this translation helpful? Give feedback.
-
Probably this update is still really fresh out of the oven so it'll take a while for the symbols to be available. Anyways the start menu DLLs are the same as 22621.2361, so in the latest prerelease I've made EP to be able to process symbols for the start menu DLLs even though it couldn't for twinui.pcshell.dll. Right now EP relies on symbols for working Win+X and Win10 alt tab on Canary builds, "open start menu to all apps" on all builds (I haven't made patterns for this), and "maximum number of frequent apps to show" or something (I haven't too). I have a lot to say about Valinet's code tbh............. |
Beta Was this translation helpful? Give feedback.
-
This morning I was able to download symbols for 22621.2428. |
Beta Was this translation helpful? Give feedback.
Probably this update is still really fresh out of the oven so it'll take a while for the symbols to be available. Anyways the start menu DLLs are the same as 22621.2361, so in the latest prerelease I've made EP to be able to process symbols for the start menu DLLs even though it couldn't for twinui.pcshell.dll.
Right now EP relies on symbols for working Win+X and Win10 alt tab on Canary builds, "open start menu to all apps" on all builds (I haven't made patterns for this), and "maximum number of frequent apps to show" or something (I haven't too).
I have a lot to say about Valinet's code tbh.............