Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Windows ARM64 Support #30

Closed
TGSAN opened this issue Nov 24, 2021 · 4 comments
Closed

Windows ARM64 Support #30

TGSAN opened this issue Nov 24, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@TGSAN
Copy link
Owner

TGSAN commented Nov 24, 2021

ARM64 support under development, related issues can be discussed here

@TGSAN TGSAN added the enhancement New feature or request label Nov 24, 2021
@TGSAN TGSAN mentioned this issue Nov 24, 2021
@NalCol
Copy link

NalCol commented Jul 2, 2022

软件没有任何直观的形式表明哪里卡住了,CPU占用一直很高(15%左右)。
另一款W10 Digital Activation Program也基本是同样情况。
但是 HEU KMS Activator成功以数字激活方式激活系统。
不知道是不是架构问题。

@TGSAN
Copy link
Owner Author

TGSAN commented Jul 2, 2022

软件没有任何直观的形式表明哪里卡住了,CPU占用一直很高(15%左右)。 另一款W10 Digital Activation Program也基本是同样情况。 但是 HEU KMS Activator成功以数字激活方式激活系统。 不知道是不是架构问题。

目前支持ARM64的版本已经基本开发完了,但是因为代码比较脏还没有提交到GitHub,之前的这个版本用的dll hook的形式去做状态欺骗,理论上是可以利用Windows指令集转换来兼容的,但是事实上跑起来不是很正常。新版本我通过调用未导出符号的方法来计算来避免使用dll hook,事实使用这种上在我的Surface Pro X(ARM64)上可以正常运行,但是主程序还是使用了不支持arm 的旧版本 .NET Framework,在不支持x64转义的Windows 10上面不知道能不能正常运行。目前还在解决这部分问题,解决之后应该就可以发布了。

@TGSAN TGSAN pinned this issue Jul 2, 2022
@TGSAN
Copy link
Owner Author

TGSAN commented Jul 2, 2022

如果急着激活的话可以临时尝试先从x86或amd64的设备上使用 CMWTAT 激活,然后在arm64设备上使用激活疑难解答,通过Microsoft账号的移进行许可迁移(走官方的正版许可自助证迁),然后在x86或amd64的设备上重新使用 CMWTAT 激活。需要注意的是两台设备的Windows SKU版本需要一致(可以使用 CMWTAT 的版本转换)。

@TGSAN
Copy link
Owner Author

TGSAN commented Sep 10, 2022

#42 更新增加适用于 ARM64 的实验性支持

Repository owner locked and limited conversation to collaborators Sep 10, 2022
@TGSAN TGSAN converted this issue into discussion #43 Sep 10, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants