-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
[Bug] I can't start vrcx after the update #1127
Comments
Dupe of #1112 |
umm....I can't find the security center service in my system, but I have tinder security software, so I can't restore it through this method. Can only Tinder security software be repaired? If there is no way, I have to choose not to update it |
Press "Win + R" and paste in |
Yes, I tried everything to wake up my Security Center app, but he kept showing me that there was no app, I don't know when it disappeared, I remember a long time ago the Security Center app was on the computer, but I have always used Tinder Security Center and left it alone Anyway, I am now back to version 2024.12.30, vrcx can be started, it seems that I can not update again Thank you very much for your patience *heart 总之我现在回退至2024.12.30的版本,vrcx可以被启动了,看来我没办法再进行更新了 非常感谢您的耐心解答 ❤ |
Try update Windows if you can, I'm assuming it's very out of date. |
I'm a windows 10 21H1 version, and I just finished updating it a while ago |
I've disabled CET on latest nightly, if you switch to nightly the issue should be gone. |
Hi
Because the online update failed, I entered github to download and update version 20250131, but my vrcx could not be started, exe file flashed back before the end of the installation and upgrade, I used zip to extract and overwrite it, but it still could not be started, the task manager process showed vrcx started but disappeared immediately
————————————————————————————————————————————————————
In case of translation, please refer to Chinese
因为在线更新失败于是我进入github下载并更新了20250131版本但是我的vrcx无法启动,exe文件在安装升级结束前闪退,我又改用zip解压并覆盖,还是无法启动,任务管理器进程显示vrcx启动了但是马上就消失了
The text was updated successfully, but these errors were encountered: