在Win10 20H2上不起作用

[liangyi9812]

试过很多加载方式，但是都不起作用，笔记本，hp ,光影精灵5
版本：

[papricasix]

So I think you are (also) having issues with MacType and Windows 10 20H2.

For me installing the newest (beta) version AND setting the launch mode to service seem to have helped. Other modes doesn't seem to be working completely.
The desktop is rendered correctly, but other programs (Firefox, Jetbrains CLion, etc.) don't. Only after using service mode, it seems to be fine for now.

[sammilucia]

yes Service Mode is recommended. or you can try Tray Mode with Admin privileges.

Registry mode requires Secure Boot to be disabled on the hardware which is not recommended.

[papricasix]

Registry mode didn't do the trick for me (and I don't have secure boot enabled), unfortunately.

[liangyi9812]

I'm looking forward to a stable version!

[sammilucia]

@papricasix please re-read my comment. Service Mode is recommended, not Registry Mode. Or try Tray Mode as Administrator

@Connon- it's been stable for a long time, what problems are you experiencing?

[snowie2000]

Tray mode with admin privileges gives you the highest privilege on Windows 10 (I know it's weird) but it's more notable than service mode. I'm continually working on the service mode right now.

[CaiAcmer]

1.要么使用服务模式，然后任务管理器中重启资源管理器。
2.进入bois关闭Secure Boot，然后使用注册表模式

[rpzone]

Registry mode becomes a risk in 20H2 and above. Once I used this mode, if program related cmd.exe will popup ERROR window. It is really a frustrated thing in using the 2019 beta 6. Why doesn't Mactype update itself anymore?

[snowie2000]

What the error window of CMD says?
Plus, registry mode is being abandoned by Microsoft and will eventually become unusable. Since this is a highly OS-oriented behavior, we can't change it.

[Outi-s]

I think I can confirm this. I got a new laptop, on 20H2, installed Mactype and right clicking the CMD or Powershell window was closing it down. Ignoring those processing were still creating an issue with VS Code for some reason, it refused to open the terminal.

I got to know it was Mactype doing it because I clean installed Windows and everything worked fine till I installed Mactype. Same issue reoccurred. Uninstalled Mactype and everything seems to work alright again.

Edit: Did few more tests. CMD and Powershell seem to remain open after right clicking the tab bar thingy after excluding the processes. Also had to exclude VS Code and for some reason Edge Canary i.e. 91.0.824.0.

[sammilucia]

interesting. I use VS Code and PowerShell and CMD and they all work fine on 20H2 (running in Service Mode) 🤔

…

On Fri, Mar 12, 2021, 02:10 Subi54 ***@***.***> wrote: I think I can confirm this. I got a new laptop, on 20H2, installed Mactype and right clicking the CMD or Powershell window was closing it down. Ignoring those processing were still creating an issue with VS Code for some reason. It refused to open the Terminal. I got to know it was Mactype doing it because I clean installed it and everything worked fine till I installed Mactype. Same issue reoccurred. Uninstalled it and everything seems to work alright again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#717 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZEQNWXC3Q6H2X3SCBJBZTTDHD5XANCNFSM4V2AR53Q> .

[rpzone]

interesting. I use VS Code and PowerShell and CMD and they all work fine on 20H2 (running in Service Mode) 🤔
…
On Fri, Mar 12, 2021, 02:10 Subi54 @.***> wrote: I think I can confirm this. I got a new laptop, on 20H2, installed Mactype and right clicking the CMD or Powershell window was closing it down. Ignoring those processing were still creating an issue with VS Code for some reason. It refused to open the Terminal. I got to know it was Mactype doing it because I clean installed it and everything worked fine till I installed Mactype. Same issue reoccurred. Uninstalled it and everything seems to work alright again. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#717 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZEQNWXC3Q6H2X3SCBJBZTTDHD5XANCNFSM4V2AR53Q .

what version of your 20H2. As I know, 19042.630 is the last version compatible with Mactype registry mode.

[sammilucia]

any of them, I've never had a problem. however it is worth noting some antivirus products will cause MacType to not function properly.

we don't recommend Registry Mode. @snowie2000 perhaps it's time to retire it?

[Outi-s]

On 19042.867. Load with Mactray (Run as admin enabled) Standalone mode.

Chrome beta, Edge Chromium Dev and Canary, none of them open up unless they are excluded from Mactype process manage.

VS Code, CMD & Powershell are working fine too after being excluded from Mactype.

[dzdydx]

I think I can confirm this. I got a new laptop, on 20H2, installed Mactype and right clicking the CMD or Powershell window was closing it down. Ignoring those processing were still creating an issue with VS Code for some reason, it refused to open the terminal.

I got to know it was Mactype doing it because I clean installed Windows and everything worked fine till I installed Mactype. Same issue reoccurred. Uninstalled Mactype and everything seems to work alright again.

Edit: Did few more tests. CMD and Powershell seem to remain open after right clicking the tab bar thingy after excluding the processes. Also had to exclude VS Code and for some reason Edge Canary i.e. 91.0.824.0.

Same thing happened on my new laptop, and I've tried MacTray with admin privileges. Right clicking the title bar of CMD and Powershell window closes them, and VS Code cannot open any terminal (CMD/Powershell/git bash) with an exit code of 3221225794.

According to https://www.reddit.com/r/techsupport/comments/lpyndb/help_please_vs_code_terminal_wont_open_cmdexe/, it seems that gdi32full.dll is the faulting module.

System info: Windows 10 20H2, 19042.964

[snowie2000]

@lin-lang This is a known problem that Mactype isn't compatible with CET (shadow stack more specifically).
I'm working on a new release right now.