🐛 Fail to initialize plugins: Everything

[rayedriasat]

Flight Check

• I'm sure existing (open and closed) don't have duplicates
• I've tried reinstalling PT, Everything, EverythingPT

Describe the bug
After installing the update of 0.87, everything plugin seems to be not working, when starting the powertoys, it pops up a message box saying "Fail to initialize plugins: Eerything
Please report the bug to ......."

To Reproduce
Steps to reproduce the behavior:

1. close powertoys
2. open powertoys
3. See error
4. ` activation command does nothing

Expected behavior
` should be able to show me search results

Screenshots

Logs (please upload or provide link to you log):
PowerToysReport_2024-12-18-11-58-45.zip

Version:

• PowerToy: 0.87.0
• Everything: Everything 1.4.1.1026
• EverythingPT: 0.87.0
• Windows: 11

Installation method (How did you install the following softwares):

• PowerToys: Manually using the exe file
• Everything: using the "Everything-1.4.1.1026.x64-Setup.exe"
• EverythingPT: initially it was installed using chocolatey, but chocolatey doesn't have the lates 0.87.0 version, it say i have the latest 0.86.0 version. but in powertoys it pops up to update. After installing the update, the plugin seems to not work.
  "Everthing" software is working fine btw.

[lin-ycv]

Are you on arm or x64? (if you don't know it's most likely x64)
Not sure why the updater downloaded the wrong version, but if you download and install the correct version (x64 or arm), it should load fine

Message: Couldn't load assembly for Everything in C:\Users\ASUS\AppData\Local\Microsoft\PowerToys\PowerToys Run\Plugins\Everything\Community.PowerToys.Run.Plugin.Everything.dll

Exception full name  : System.IO.FileLoadException
Exception message    : Could not load file or assembly 'C:\Users\ASUS\AppData\Local\Microsoft\PowerToys\PowerToys Run\Plugins\Everything\Community.PowerToys.Run.Plugin.Everything.dll'. The assembly architecture is not compatible with the current process architecture.
Exception stack trace:
   at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath)
   at Wox.Plugin.PluginPair.CreatePluginInstance()
Exception source     : System.Private.CoreLib
Exception target site: System.Reflection.Assembly LoadFromAssemblyPath(System.String)
Exception HResult    : -2146230266

side note: chocolatey is currently in review process, that's why it's not showing up

[rayedriasat]

64-bit operating system, x64-based processor
Edition Windows 11 Home Single Language
Version 23H2
Installed on ‎12/‎28/‎2023
OS build 22631.4602
Experience Windows Feature Experience Pack 1000.22700.1055.0

Did I install the wrong version of the plugin? i installed : EverythingPT-0.87.0-ARM64.exe
Probably installed the wrong version

[rayedriasat]

Yup, Solved. installed x64 now it's working fine.
I mistakenly installed arm64.
Thanks a lot

[lin-ycv]

so that's the wrong version, you want
EverythingPT-0.87.0-x64.exe

[selfdocumentingcode]

I also got this error twice today (two different Windows PCs) after upgrading to v0.87.
In both cases it was likely because I upgraded EverythingPowerToys to v0.87 while PowerToys itself was still on v0.86.

It would be nice if the EverythingPowerToys installer/update checker would warn against this scenario.

[AJolly]

Also it wiped out all of my settings by installing the upgrade.
ps - Would love it if the installer would automatically exit power toys run and then reload it. I've got I manually exit and restart right now

[lin-ycv]

The installer is intentionally dumb so that it doesn't trip antivirus false positives. Previously the installer would do checks and close PT, but it'd trip a quarter to half of the antivirus, so it was made dumb.

[AJolly]

Does av get flagged if you prompt the user to terminate the process and try again?

Or use HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations and just tell the user it'll be upgraded next time they reboot.

Also try adding setup to the installer file name, I vaguely remember Windows having special compatibility settings it'll use in that case but I could be mistaken.

[lin-ycv]

The issue is that AV does't report how exact they're being triggered, especially with ML and AI.

So I might build version A, minimal trigger, make changes and build version B, but it triggers like everything; remove all the changes to build version C, and C would still trigger, even tho A would be minimal.

I think you're referring to .msi instead of .exe.
building msi is a bit complex since it's just a wrapper around an exe file, I still need to build an exe first.

Side note: this is all off topic, so move to discussions if you want to discuss more.