Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

explorer crash #5

Open
Moonnique opened this issue Jul 14, 2019 · 7 comments
Open

explorer crash #5

Moonnique opened this issue Jul 14, 2019 · 7 comments

Comments

@Moonnique
Copy link

I had an issue with using this, it made explorer crash when you right click an item in the start menu all programs menu.

@PhantomNimbi
Copy link

Same it happens when using StartIsBack++ without the XP Flyout style enabled.

@rikka0w0
Copy link
Owner

Hi all,

This is a known problem, and I have noticed this during the development of the pre-alpha version. It is not a compatibility problem with other software, the crashing is caused by thread-unsafe code injection (To change context menu appearance), but unfortunately, for now, I could not offer a better solution.

To achieve a crash-less solution (with thread-safe injection), we need to know how explorer.exe and other shell stuff works so that we can decide when and where to inject our code. But it is so hard find useful information about the internal of windows explorer and shell beyond shell extensions. So, if you guys know someone who is familiar with shell programming, please introduce him/her to me! I really need help.

Besides waiting for a fix, I think you can try out third-party themes (requires uxtheme) which includes a customized context menu appearance. There's also a vote on Reddit to ask Microsoft bring back this feature, the best outcome would be Microsoft adding back this option so we don't need to make tricky patches again.

@PhantomNimbi
Copy link

PhantomNimbi commented Jul 16, 2019

Thanks for the reply, tbh I am using it with custom themes. This is what brought back the custom context menu in Windows 10 1903 for me, lol.

As for shell programming, I believe there are a fair few people in http://virtualcustoms.net/ who might be able to help you.

@rikka0w0
Copy link
Owner

rikka0w0 commented Nov 14, 2019

Hey guys,

I found a alternative solution to this problem, it does not give you a real classic context menu, but a very similar one:
image

I did this on Win10 1903, and this should also work on 1909, 1809, previous and future versions of Win10. __You need to install uxtheme patcher to make it work!__Download is here:
aerolite.zip
Switch to the Win10 default theme and replace the aerolite.msstyles in %windir%\Resources\Themes\aero. Ajdust the permission of %windir%\Resources\Themes\aero\VSCache, make Administrator own it and take full control of it, then delete whatever inside that folder. Finally, switch to aerolite theme and your explorer context menu should look like the system context menu. Adding my TaskbarContextMenuTweaker and the aeroglass8+ makes Win10 look even better!

This solution only gives you a similar look, it is still immersive menu. If you trying to add a menu background, this will not work!

Checkout:
https://gist.github.com/rikka0w0/971e247871154427d5e62c7b3a7ac1d4

@SyntheticDawn
Copy link

explorer tweaker becomes active on rightclicking a file or folder neither inside C: or inside a folder on the desktop rikka0w0 could you please make one for win32 too?

@Yaron10
Copy link

Yaron10 commented Mar 15, 2021

@rikka0w0,

Thank you for your work. 👍

I found a alternative solution to this problem, it does not give you a real classic context menu, but a very similar one

I'd like to make sure I understand it correctly.
If I install all the components in https://docs.google.com/document/d/1wsu2tkdB2TIR1fy7lp2HuQ9JeuVG713syzz9RGl2cV0/edit, should the alternative context-menu work properly?

@SyntheticDawn
Copy link

SyntheticDawn commented Nov 28, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants