[BUG] After the installation of the Magisk module is completed and subsequent reboot of WSA, the Magisk Module Disappears.

[coocv]

Describe the bug | 描述一下这个错误

magisk模块安装完成后重启丢失

Steps to reproduce the issue | 重现该问题的步骤

在magisk中安装模块，安装成功点击重启按钮后magisk APP显示未安装任何模块

Expected behaviour | 预期的行为

正常情况重启后模块应该保留且生效

Downloaded Build Of WSA | 已下载的WSA版本

WSA_2307.40000.5.0_x64_Release-Nightly-with-magisk-ee34f775.26105.-canary-MindTheGapps-13.0-RemovedAmazon

Windows build number | Windows构建号

22621.2134

PC Specification | 个人电脑规格

设备名称 CVCO-PC
处理器 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz
机带 RAM 32.0 GB (31.8 GB 可用)
设备 ID 5932F970-5BDE-4553-B574-26D62591D61E
产品 ID 00330-80000-00000-AA395
系统类型 64 位操作系统, 基于 x64 的处理器
笔和触控 笔支持

Additional context | 额外的背景

已尝试magiskAPP 中本地安装模块和shell安装，模块均显示安装成功，重启WSA模块消失，magisk中显示未安装任何模块

[MustardChef]

@coocv 你好 感谢您提出问题。这是一个已知问题，我正在尝试诊断和修复。请帮我测试一些东西。

首先，请检查卸载当前版本并安装此版本后问题是否仍然存在 --> https://github.com/YT-Advanced/WSA-Script/releases/download/WSA-Insider-Version/WSA_2307.40000.5.0_x64_Release-Nightly-with-Magisk-26.1-stable-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon.7z

[coocv]

@coocv 你好 感谢您提出问题。这是一个已知问题，我正在尝试诊断和修复。请帮我测试一些东西。

首先，请检查卸载当前版本并安装此版本后问题是否仍然存在 --> https://github.com/YT-Advanced/WSA-Script/releases/download/WSA-Insider-Version/WSA_2307.40000.5.0_x64_Release-Nightly-with-Magisk-26.1-stable-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon.7z

@MustardChef
我卸载之前的版本并全新安装此版本后，它同样丢失了

[s1204IT]

After installing the module, does the directory with module ID exist in /data/adb/modules_update?

[coocv]

After installing the module, does the directory with module ID exist in /data/adb/modules_update?

@s1204IT

我没有找到modules_update文件夹，这里有一个截图，截图中我看到了magisk和lspd文件夹
I can't find the modules_update folder. Here is a screenshot where I see the magisk and lspd folders

The modules folder is empty

但是LSPosed是未生效的
But LSPosed is not in effect

[coocv]

@MustardChef

嘿，管理员，我有了新的问题，在重新安装前，我打开MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe文件夹，里面的用户数据文件名为userdata.2.vhdx而不是手册中的userdata.vhdx，我备份了它。

在重新安装后，我将userdata.2.vhdx重新恢复到源文件夹内并替换了新生成的，但是我之前安装过的app并没有出现。

当我打开GooglePlay，我看到了我的头像，我想它保留了我的登录信息，其他APP好像都丢失了，只剩下系统自带的APP。
我尝试重新安装以前的APP，它的用户数据同样回来了。是因为userdata.2.vhdx只备份了用户数据而不包含APP本身吗？

通过应用管理器，我看到了它们并且能正常打开，但是开始菜单没有出现它们的图标，WSA也没有显示它们

查阅手册，我开始尝试恢复应用图标。以管理员身份删除了install.ps1中的所有启动项目，并执行了全新安装。

在安装完后，WSA会弹出窗口，不要对它作出反应，否则依然会自启动，所有步骤都将失败。在这期间把备份文件放回新生成的MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe文件夹（此时它还是空的），点击窗口，启动WSA，所有应用和图标都会回归。

当我尝试把userdata.2.vhdx改名为userdata.vhdx时，应用无法再打开，我想它只能是叫userdata.2.vhdx

[Abyvn]

Just wanted to mention I had the same issue. couldnt even install Lsposed or any other magisk modules. clean installed 2306 and everything worked.

[coocv]

只是想提一下我有同样的问题。甚至无法安装 Lspose 或任何其他 magisk 模块。干净安装2306，一切正常。

Thanks for the tips from my good friend

[3b9LkG5XgwjS9BSs9OdXZAOmkp6KqrLx]

https://www.bilibili.com/video/BV1GV4y1v7ys/

I found a video that might be useful for temporarily solving this problem.

[coocv]

https://www.bilibili.com/video/BV1GV4y1v7ys/

I found a video that might be useful for temporarily solving this problem.

@3b9LkG5XgwjS9BSs9OdXZAOmkp6KqrLx
Wow, thank you! Before that, I also tried to search for related videos on Bilibili, but did not find them. It seems that this video is very useful, I will try it right away, thank you very much!

According to the video, I made it, it worked, thanks 😊

[MustardChef]

https://www.bilibili.com/video/BV1GV4y1v7ys/

I found a video that might be useful for temporarily solving this problem.

Thank you for sharing!

[AndnixSH]

Here is the quick steps for those who don't understand chinese

Use any file manager of your choice. I'm using X-plore

First pane: Go to /data/adb/modules/(your installed module)
Second pane: Go to /data/adb/modules_update/(your installed module)

Copy all files and overwrite from /data/adb/modules_update/(your installed module) to /data/adb/modules/(your installed module)

DELETE the file called "update" from /data/adb/modules/(your installed module)

Repeat the same steps on other modules

When you are done, DELETE the modules_update folder

Reboot WSA via Magisk app. The modules should be working now

[MustardChef]

@s1204IT
Should I open an issue at: https://github.com/topjohnwu/Magisk?

[s1204IT]

@s1204IT Should I open an issue at: https://github.com/topjohnwu/Magisk?

No, please wait a little longer.
It may not be reproducible in all environments, and the issue does not occur with KernelSU.

At least with a clean install, the problem does not occur, so you need to look for problems with specific versions.

[s1204IT]

And does this problem still occur in v26.3?

[MustardChef]

And does this problem still occur in v26.3?

• Yes, it still occurs in v26.3.
• Users with clean installations of WSA are now known to face this issue and the known number of people facing this issue is increasing
• KernelSU and Magisk Alpha do not have this issue so it might be related to the official Magisk builds.

[rainman74]

• KernelSU

KernelSU is fully sufficient for WSA. In my opinion, we no longer need builds with Magisk.

[MustardChef]

• KernelSU

KernelSU is fully sufficient for WSA. In my opinion, we no longer need builds with Magisk.

Agreed, but people still want builds with Magisk and KernelSU has some quirks that break some Magisk Modules, which work well on Magisk.
I don't think it will do much good by dropping Magisk builds due to the module installation issues.

[s1204IT]

And does this problem still occur in v26.3?

• Yes, it still occurs in v26.3.
• Users with clean installations of WSA are now known to face this issue and the known number of people facing this issue is increasing
• KernelSU and Magisk Alpha do not have this issue so it might be related to the official Magisk builds.

Oh, seriously...

It may be close by the maintainers, but you may want to open an issue.

[AndnixSH]

• KernelSU

KernelSU is fully sufficient for WSA. In my opinion, we no longer need builds with Magisk.

Agreed, but people still want builds with Magisk and KernelSU has some quirks that break some Magisk Modules, which work well on Magisk. I don't think it will do much good by dropping Magisk builds due to the module installation issues.

Yep, I'm still using Magisk as long as it is available to use, and I'm well familar with it

[rainman74]

• KernelSU

KernelSU is fully sufficient for WSA. In my opinion, we no longer need builds with Magisk.

Agreed, but people still want builds with Magisk and KernelSU has some quirks that break some Magisk Modules, which work well on Magisk. I don't think it will do much good by dropping Magisk builds due to the module installation issues.

Yep, I'm still using Magisk as long as it is available to use, and I'm well familar with it

Then you should just take a look at KernelSU. I've also enjoyed using Magisk for years, but I installed KernelSU as a test and was very impressed by it. So I don't use Magisk any more.

[RingingVolcano]

Hmm, does this still occur after restarting WSA? Also, try clearing the data and cache of the LSPosed app.

Yes, I tried these ,but it still doesn't work.I even update my WSA to the latest version and it still occurs.

[RingingVolcano]

Look like same when I usd WSA

Have you solved the problem? I still can't get it to work.

[BlueSkyXN]

Look like same when I usd WSA

Have you solved the problem? I still can't get it to work.

I have the same issue as you. The LSP framework is the latest version from the official GitHub repository, the LSP app is from the Google Play Store, and WSA is a pre-built Windows 11 package available at https://github.com/MustardChef/WSABuilds.

[coocv]

当我 usd WSA 时看起来一样

你解决了问题吗？我仍然无法让它工作。

I switched to the WSA with KernelSU and now it works fine

[RingingVolcano]

I switched to the WSA with KernelSU and now it works fine

So there are still some issues with Magisk on WSA....?

[coocv]

I switched to the WSA with KernelSU and now it works fine

So there are still some issues with Magisk on WSA....?

When I found this problem, you can try the solution in the comments section, it worked on my machine, I switched versions for convenience, so I don't know if later versions solved it (I guess not), kernelsu was enough for me

[AkirahikoGhub]

I'm in adb
There is no lspd in it, and I can’t even install the lspd apk.

[BlueSkyXN]

So there are still some issues with Magisk on WSA....?

Even if I have used the latest version https://github.com/MustardChef/WSABuilds/releases/download/Windows_11_2309.40000.2.0/WSA_2309.40000.2.0_x64_Release-Nightly-with-magisk-d4e552d0.26301.-canary-MindTheGapps-13.0-RemovedAmazon.7z, the problem still exists, and there is no viable solution available.

[BlueSkyXN]

当我 usd WSA 时看起来一样

你解决了问题吗？我仍然无法让它工作。

I switched to the WSA with KernelSU and now it works fine

Still same issues

[sn-o-w]

I just found out about this issue.

The module disappearing issue still happens on a clean instance of WSA. It just happened today for me on WSA 2310.40000.2.0.

Using an older version of Magisk seems to be another workaround. At the time I'm writing this, Magisk 25210 seems to be unaffected by this.

So... somewhere between versions 25210 and 26105 (since 26105 is mentioned by OP) of Magisk seems to cause this. 🤔

[BlueSkyXN]

我刚发现这个问题。

模块消失问题仍然发生在干净的WSA实例上。今天我在WSA 2310.40000.2.0上遇到了这个问题。

使用旧版本的Magisk似乎是另一种解决方法。在我写这篇文章的时候，Magisk 25210似乎没有受到影响。

所以... Magisk的版本25210和26105之间的某个地方（因为OP提到了26105）似乎导致了这一点。🤔

I also believe it has something to do with compatibility with certain versions. Currently, I am using a special version, and everything is working fine. You can check it out here: https://www.blueskyxn.com/202311/6882.html

[MustardChef]

我刚发现这个问题。
模块消失问题仍然发生在干净的WSA实例上。今天我在WSA 2310.40000.2.0上遇到了这个问题。
使用旧版本的Magisk似乎是另一种解决方法。在我写这篇文章的时候，Magisk 25210似乎没有受到影响。
所以... Magisk的版本25210和26105之间的某个地方（因为OP提到了26105）似乎导致了这一点。🤔

I also believe it has something to do with compatibility with certain versions. Currently, I am using a special version, and everything is working fine. You can check it out here: https://www.blueskyxn.com/202311/6882.html

You are referring to Magisk Alpha, I assume?

[aawwsslll]

https://www.blueskyxn.com/202311/6882.html
参考这个兄弟的链接，我一次就安装成功了，需要安装面具alpha版。
这个兄弟提供的链接过期了，但是那个构建的action还在更新，我安装的新版也没问题，或者你也可以用链接里提供的
阿里云的版本应该没问题。

[BlueSkyXN]

https://www.blueskyxn.com/202311/6882.html 参考这个兄弟的链接，我一次就安装成功了，需要安装面具alpha版。 这个兄弟提供的链接过期了，但是那个构建的action还在更新，我安装的新版也没问题，或者你也可以用链接里提供的 阿里云的版本应该没问题。

直接用我分享的打包就行了，其他构建我无法验证，只能自己测试了，最佳选择是和我保持同款构建源

[AronnaxM]

Here is the quick steps for those who don't understand chinese

Use any file manager of your choice. I'm using X-plore

First pane: Go to /data/adb/modules/(your installed module) Second pane: Go to /data/adb/modules_update/(your installed module)

Copy all files and overwrite from /data/adb/modules_update/(your installed module) to /data/adb/modules/(your installed module)

DELETE the file called "update" from /data/adb/modules/(your installed module)

Repeat the same steps on other modules

When you are done, DELETE the modules_update folder

Reboot WSA via Magisk app. The modules should be working now

Thanks a lot bro, I finally overcome this proble after 3hrs😅

[landall]

I trigger the same issue.

[landall]

---Magisk Logs---
26.3 (26300)

03-06 03:18:26.943   119   119 I : Magisk 26.3(26300) daemon started
 03-06 03:18:26.944   119   119 I : * Device API level: 33
 03-06 03:18:26.954   119   121 I : ** post-fs-data mode running
 03-06 03:18:26.955   119   121 I : * Mounting mirrors
 03-06 03:18:26.964   119   121 I : * Initializing Magisk environment
 03-06 03:18:26.972   119   121 I : * Running post-fs-data.d scripts
 03-06 03:18:26.973   119   121 I : Upgrade / New module: trustusercerts
 03-06 03:18:26.974   119   121 I : * Running module post-fs-data scripts
 03-06 03:18:26.974   119   121 I : * Loading modules
 03-06 03:18:27.574   119   121 I : ** late_start service mode running
 03-06 03:18:27.574   119   121 I : * Running service.d scripts
 03-06 03:18:27.575   119   121 I : * Running module service scripts
 03-06 03:18:29.734   119   121 I : ** boot-complete triggered

but the module is lost as usual.

[landall]

---Magisk Logs---
26.3 (26300)

03-06 03:18:26.943   119   119 I : Magisk 26.3(26300) daemon started
 03-06 03:18:26.944   119   119 I : * Device API level: 33
 03-06 03:18:26.954   119   121 I : ** post-fs-data mode running
 03-06 03:18:26.955   119   121 I : * Mounting mirrors
 03-06 03:18:26.964   119   121 I : * Initializing Magisk environment
 03-06 03:18:26.972   119   121 I : * Running post-fs-data.d scripts
 03-06 03:18:26.973   119   121 I : Upgrade / New module: trustusercerts
 03-06 03:18:26.974   119   121 I : * Running module post-fs-data scripts
 03-06 03:18:26.974   119   121 I : * Loading modules
 03-06 03:18:27.574   119   121 I : ** late_start service mode running
 03-06 03:18:27.574   119   121 I : * Running service.d scripts
 03-06 03:18:27.575   119   121 I : * Running module service scripts
 03-06 03:18:29.734   119   121 I : ** boot-complete triggered

but the module is lost as usual.

It may be a bad hint issue.
The install process of this module after reboot is failed, but there is no log to tell us it is failed.

[s1204IT]

Please retry with Magisk v27.0

[Schefflin]

@MustardChef Even KernelSU is no problem with modules, but MTmanager can't use root from KernelSU. So it cannot read-write system partition by magiskOverlayFS（sigh

[uihp]

I just tried Magisk 26103 and succeeded.
https://github.com/MustardChef/WSABuilds/releases/download/Windows_11_2306.40000.3.0/WSA_2306.40000.3.0_x64_Release-Nightly-with-magisk-a8c4a33e.26103.-canary-MindTheGapps-13.0-RemovedAmazon.zip
Magisk 26104 failed so I think releases with Magisk 26104+ may all have this issue.

[MustardChef]

2311.40000.5.0_LTS_1 builds should fix this issue.

[SonMaxime]

2311.40000.5.0_LTS_1 builds should fix this issue.

Hi ! Unfortunatly for my case this build didn't solved the issue.
Still experimenting it in the same way as previous ones.