x64 emulation on ARM64 device not working correctly

[pb5050]

Microsoft PowerToys version

.35

Running as admin

Yes

Area(s) with issue?

Image Resizer, MD Preview, PowerRename, PowerToys Run, SVG Thumbnail

Steps to reproduce

try to use apps

✔️ Expected Behavior

supposed to work

❌ Actual Behavior

nothing zero zui

Other Software

No response

using surface pro x, before shortcuts window was not working but is now.

x64 emulation on surface pro x the following areas i selected do not work at all SVG preview works but not thumbnails.

i was able to get powertoys run to work by manually opening PowerLauncher.exe in the directory when i enable the powertoys run it will automaticallyt disable it when opening window. also the plugins stick on loading untill i manually open PowerLauncher.exe

i have had no luck on others. power rename and resizer not showing up in context menu at all.

i can manually open resizer and use the app like that....
. its almost like the hotkeys arnt loading somthing or something prevents context menu actions from being created
PowerToysReport_2021-04-08-11-18-18.zip

[pb5050]

also the powertoys run hotkey would not open app untill i used this command, and i used this command after creating that powertoys report.

ran the following comand in admin mode CMD
takeown /f "C:\Program Files\PowerToys" /r

if you need another report or anything let me know please. yes i was running powertoys as admin and installed it as admin i tried every option i could think of before making this report

[crutkas]

As of now, our team hasn't spent any time validating the x64 emulation on the Insider builds.

Logs show Windows BuildNumber: 21354 which is the build released a few days ago.

[crutkas]

@pb5050. This is a quirk of actually .NET Core and the fact stuff is mix mode it seems like. Chatting with @snickler, he figured out a work around:

workaround

If you include/copy the hostfxr.dll from the specific runtime to the folder of the app, it'll "work"

more background from @snickler

It's a common piece of weirdness when installing x64 .NET Core when ARM64 .NET Core exists. Everything gets installed in the same Program Files directory

When running the exes by itself, it tries to run under the latest SDK/runtime installed. When running dotnet PowerLauncher.exe or dotnet PowerLauncher.dll, it respects the runtimeconfig and attempts to run it as the 3.1.3 runtime.

The BIG ISSUE is that if a newer runtime/SDK was installed before this, it doesn't replace the dotnet.exe.

x64 and ARM64 dotnet.exe's don't co-exist, unfortunately.

[crutkas]

Ultimately, i don't think this is something the PT team will fix, we'd rather do the correct fix with #490 and get ARM64 online properly which needs WinUI3 unpackaged support to come in

[crutkas]

@pb5050 did that workaround work for you?

[pb5050]

im sorry i have been really busy thank you for checking back! what exactly do i need to do lol im kinda computert savy but not to your guys levell lol

you had said
workaround
If you include/copy the hostfxr.dll from the specific runtime to the folder of the app, it'll "work"

what do you mean by runtime and where is this located?

[pb5050]

are u refering to this file?

C:\Program Files\dotnet\host\fxr\3.1.13

i copied it into
C:\Program Files\PowerToys

and nothing should i have added a different file or into a diff spot?

[crutkas]

Each tool inside the module folder. PT is a suite of apps.

[pb5050]

okay so i coppied the following

and placed it in everyone of these folders.

you can see here colorpicker is starting when i toggle the settlings switch, but it always has worked. you can see its using the .dll in the directory and you can see its using the right dotnet folders.

My question is im still getting this.
[2021-04-10 08:53:58.825981] [p-7368] [t-7244] [trace] Starting PowerToys Run from elevated process
[2021-04-10 08:53:58.863981] [p-7368] [t-7244] [error] Failed to start PowerToys Run

is there a build that will give very detailed debug logs? im trying to debug this with process mon and exts, but it would be so nice to have a very thorough log file so i can see whats that [error] ???

[crutkas]

@snickler may have some quick insights here as it was workaround.

Sadly right now we're focused on getting ARM support fully functional versus a workaround. #490 is our tracked issue for that support

[pb5050]

Absolutely that would
Be ideal, but I was just trying to get it half ass going in the meantime my head hurts
Lol

[snickler]

@pb5050 try this dotnet/sdk#16896 (comment)

[pb5050]

I will when I get home shouldn't be too long

[crutkas]

Please keep us updated!

[snickler]

:)

[snickler]

dotnet/sdk#16896 (comment)

@pb5050 read COMPLETELY through the steps I gave on the comment. I explain where it's installed and how that path is set.

[pb5050]

This the only error i can see now ...... Does this mean anything to you?

i did the install like you said, and yes everything is way quicker and way better tbh. that helped everything i think i have tinkered with stuff so much...... It may be somthing i have changed or installed thats the issue now lol..... because it is running way smoother than it ever has. your install method helped big time with the performance, and other apps i had work now lol

i opened the powerlauncher manually and it works and boy is it way snappier than it was before, but its not automatically loading thats the only issue.

im still getting this
[p-12900] [t-11192] [info] Launcher is enabling
[p-12900] [t-11192] [trace] Starting PowerToys Run from elevated process
[p-12900] [t-11192] [error] Failed to start PowerToys Run
[p-12900] [t-11192] [info] Launcher object is destroying

this is the only file i could find with errors. let me know if anything pops up in youe head im going to go grab somthing to eat lol and take a break.
2021-04-18.txt

[crutkas]

see if you can directly launch PT Run via the exe, not through the runner.

[pb5050]

i can! the way snickers had ,me edit the registry for that dotnet install has me thinking why nbot check my registry ive done everything else. so i installed a older version of PT and it worked. but everytime i install a newer version it does not work.

HKEY_CURRENT_USER\SOFTWARE\Classes\AppUserModelId\PowerToysRun
ERROR 2

i came up with this in the registry report. which ive added. ive been doing some digging and it looks like maybe its my arm64 it confusing PT and leaving keys out. i need to figure out all the keys im missing or whatnot. i think this is the issue im trying to extract the registry data and install them manually if needed but im having trouble finding a list.

i added the registry report.
registry-report-info.txt

[pb5050]

i installed the new Dev build of windows arm everthing is working now, excpet the powerrun on new versions, and svg thumbnails. (which has never worked for me)

the MD and SVG previewpane work but not SVG thumnails. i can manually load the PTRun , but its not as smooth and has glitches (which native arm will fix)

any ideas on the thumbnails im still tinkering lol

[crutkas]

thumbnails could be a few things. this is something we'd put more debugging into for #490.

sorry :(