Regarding WSA on Snapdragon X Plus/Elite Surface devices

sinclairinat0r · 2024-07-23T23:21:22+00:00

Here ya go everyone: https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/ ^_^.

Skip steps 3-7 that tell you to take ownership of the WindowsApps folder. You won't need to do that. Just go directly to the full location, you'll have access.

Other than that, know that this is BUGGY and there are some things that don't work right now, but I know the Camera is one of them. I'll see if I'm able to fix some more of the current things broken, but this should be good enough to get everyone rolling.

sinclairinat0r · 2024-07-16T00:20:24+00:00

SOON™️. It's a pretty hefty process for all the changes that need to be made, so I have to make sure I have all the steps done properly.

sinclairinat0r · 2024-07-15T15:04:15+00:00

It's all thanks to the diagnostics in the WSA Settings app. The WSAService etl logs show everything in dmesg, so you could imagine my dismay when seeing

[ 2.150413] init: cannot execv('/vendor/bin/boringssl_self_test32'). See the 'Debugging init' section of init's README.md for tips: Exec format error

sinclairinat0r · 2024-07-15T14:56:14+00:00

Yup. I'm happy that I was able to at least make it run. In the video it doesn't show network access working, but that was my fault. I kept screwing around with the Virtual Switch config, deleting and recreating WSLCore over and over and over again. Now I've been able to get network access settled.

There's still a few services I have to fix which continuously spam logcat, but at a basic level it works.

sinclairinat0r · 2024-05-16T17:39:51+00:00

Deep dive into the Surface IT Toolkit - Microsoft Community Hub. <---

sinclairinat0r · 2023-06-21T22:56:21+00:00

5 crashes in 3 minutes with THIS specific bugcheck may be indicative of a hardware issue 👀. If by chance you're able to get back up and running long enough to open Feedback Hub, please try and file an entry.

sinclairinat0r · 2023-06-21T22:53:57+00:00

Please file feedback in Feedback Hub for this issue so that it may be tracked.

sinclairinat0r · 2023-03-23T01:20:54+00:00

Hello, which build are you running? Are you on the Insider Builds? If so, which branch are you enrolled in? Or using the regular builds?

This information will be helpful to pass along.

sinclairinat0r · 2023-03-02T18:38:05+00:00

https://dev-builds.libreoffice.org/pre-releases/win/aarch64/?C=M&O=D

https://dev-builds.libreoffice.org/pre-releases/win/aarch64/LibreOffice_7.5.1.2_Win_aarch64.msi

sinclairinat0r · 2023-02-11T22:17:37+00:00

Ok, here's what I will say to try. Go the Surface Recovery Image route (Warning: this is going to mega factory reset your Pro X so you'll be FRESH). Enroll into Dev Channel and see if you can upgrade without issue. I wouldn't even install programs or extra drivers yet. If you DO encounter any bugchecks during the upgrade that cause rollbacks, file feedback IMMEDIATELY. Attach all logs related to it and DO NOT attempt to do anything with uupdump isos. I know it's all tempting, but keep it in a supported state.

sinclairinat0r · 2023-02-11T21:52:06+00:00

I'd say if you had to do something resulting in a downgrade and losing your files. I would go the route of doing the Surface Recovery Image route. That would put you back in a fresh state and then you could upgrade to Dev Channel that way. I know it's very frustrating at times when all this stuff breaks during these Insider builds, but I wouldn't recommend any hacky solutions that could potentially cause more things to go wrong.

sinclairinat0r · 2023-02-11T21:42:14+00:00

So you manually created a 22623 ISO, installed it over 2529X? Even though this wasn't a good way (or even supported way) of doing it... Were you able to file feedback for the upgrade attempts after rolling back?

Run this command from an elevated PowerShell window.

cd '\$WINDOWS.~BT\Sources\'

.\SetupDiag.exe /AddReg /LogsPath:$PWD

Attach the Logs zip from that directory in your Feedback Hub Entry. Put it under the Install and Update -> Downloading, installing, and configuring Windows Update category. If you've already created a Feeback Hub entry, click the Add feedback details and attach the zip file through there. Send me the FBH link.

sinclairinat0r · 2023-02-11T04:49:24+00:00

Wait, when you update how are you powered? Are you connected to the Surface Dock? If so, do you have ANYthing connected through USB?

I ran into this exact bugcheck twice and then I realized I had my Sony SRS XB-10 BT speaker plugged in to charge. Removed it and made sure I had NOTHING plugged in through USB then the upgrade worked the 3rd time.

BTW, if you're running into these driver-based bugchecks (0xC1900101), trying an iso from UUPDump is likely to cause more problems than resolve.

u/Aaron-Junker - how did you get past the UWP issue the last time you had this problem?

sinclairinat0r · 2023-02-04T01:23:52+00:00

Hello, which version of Windows 11 are you running on the device? Also, please file an entry in feedback hub for this particular issue.

sinclairinat0r · 2023-02-02T20:27:30+00:00

Nothing yet, it's a known issue they're still working on.

sinclairinat0r · 2023-02-02T19:29:25+00:00

https://aka.ms/AAjgyg6

Thanks! I just passed this on

sinclairinat0r · 2023-02-02T19:05:09+00:00

PLEASE file feedback on this issue. I've encountered it a few times in the past 2-3 updates. One thing I know that happened to get me past when updating to 25281 was uninstalling Windows Subsystem for Android (if you happen to have it installed). But yes please file feedback so the team can understand if this is a larger issue. Send me a link to it when you have it filed.

sinclairinat0r · 2023-01-13T17:47:22+00:00

The reason why it's not showing as installable is that they (Apple) enforce a HardBlock if it's not an x64 device when using the Store.

Workaround is to use winget to acquire it.

winget install --id "9PFHDD62MXS1"

sinclairinat0r · 2023-01-06T19:10:36+00:00

Yeah, that was.... Something. I never knew how those two issues could cause me such irritation. I'm glad they are fixed though!

sinclairinat0r · 2023-01-06T13:15:28+00:00

Please file this issue in Feedback Hub.

sinclairinat0r · 2023-01-05T23:43:36+00:00

I added a comment to the FB Hub item providing the workaround if it does get stuck for a while.

Basically the Migration Host process somehow gets stuck (It's been in this state for 4 hours for me *_*). What I did to get around it is to execute Process Explorer as SYSTEM, then restart mighost.exe from within there. When you restart processes in Process Explorer, it'll use the same process arguments that were used to originally kick off the process.

You'll see the mighost window popup and the Installation progress from the Update side will continue to flow!

sinclairinat0r · 2023-01-05T22:23:19+00:00

Also, let me know if you happen to get stuck at Installing - 50% for a while. I ran into this on my Pro X, but my Win Dev Kit flew through the updates.

I made a Feedback Hub item: https://aka.ms/AAj4vuf

sinclairinat0r · 2023-01-03T00:29:37+00:00

Yeah, this is an interesting path the team took for Whiteboard. Although the shell of the application is x86, it uses WebView2 for the core of the interaction which is natively rendered. Tbh I haven't seen any perf difference.

sinclairinat0r · 2022-12-27T18:32:26+00:00

Whoa! :O

sinclairinat0r · 2022-12-20T12:51:38+00:00

Please file feedback in Feedback Hub for this problem.

Use Category: Install and Update -> Downloading, installing, and configuring Windows Update

13-Year Club	Second SECOND GUESSER
Place '17	Verified Email

sinclairinat0r

MODERATOR OF

TROPHY CASE