PD-Runner-Revived
PD-Runner-Revived copied to clipboard
Content mismatch: Not compatible with macOS Ventura / 未兼容 macOS Ventura
me too
Hello, I need more detailed information to check this issue.
Could you tell me which version of PD and macOS you are using? MacBook / iMac model, System language, Apple Silicon or Intel?
Hello, I need more detailed information to check this issue.
Could you tell me which version of PD and macOS you are using? MacBook / iMac model, System language, Apple Silicon or Intel?
Hi, my macOS version is Ventura 13.0, and PD version is 18.0.2. MacBook model : MacBook air m1 (Apple Silicon). System language : English
Sorry PD Patcher is untested under macOS Ventura currently, I'm still in Monterey. The new macOS may have added new security policies that cause PD Patcher to fail :(
I just found out that macOS Ventura added a new permission “App Management”. In System Preferences > Privacy & Security > App Management, click "+" button, add "PDPatcher.app". Then try it again? Also don't forget to give it "Full Disk Access" :)
I just found out that macOS Ventura added a new permission “App Management”. In System Preferences > Privacy & Security > App Management, click "+" button, add "PDPatcher.app". Then try it again? Also don't forget to give it "Full Disk Access" :)
Thanks for the suggestion, but I just tried it and the problem wasn't solved.
Thanks for the suggestion, but I just tried it and the problem wasn't solved.
The main script is at “Show Package Contents”,Contents/Resources/script.sh
You can run it manually via typing sudo bash script.sh
in Terminal.app and see what happens on error.
Thanks for the suggestion, but I just tried it and the problem wasn't solved.
The main script is at “Show Package Contents”,
Contents/Resources/script.sh
You can run it manually via typingsudo bash script.sh
in Terminal.app and see what happens on error.
Very thanks for your solution, I solved this issue. For me, I add PDPatcher to App Management first, then open Parallels Desktop, finally, open PDPatcher, input password, then works fine!
Thanks for the suggestion, but I just tried it and the problem wasn't solved.
The main script is at “Show Package Contents”,
Contents/Resources/script.sh
You can run it manually via typingsudo bash script.sh
in Terminal.app and see what happens on error.
I add Terminal.app to App Management first, and run the script.sh
successfully, Thanks.
Thanks for the suggestion, but I just tried it and the problem wasn't solved.
The main script is at “Show Package Contents”,
Contents/Resources/script.sh
You can run it manually via typingsudo bash script.sh
in Terminal.app and see what happens on error.
终端运行后显示查找不到相关路径(终端已授权访问所有磁盘文件)
设备:MacBook Pro(M1)
macOS版本:Ventura 13.0, 以及 PD版本是18.0.2
系统语言是中文
终端运行后显示查找不到相关路径(终端已授权访问所有磁盘文件) 设备:MacBook Pro(M1) macOS版本:Ventura 13.0, 以及 PD版本是18.0.2 系统语言是中文
输入sudo bash
空格,然后将script.sh
文件拖进命令行窗口,然后回车。这个文件在“显示包内容” -> Contents -> Resources 文件夹下。
输入你的密码(屏幕上什么都不会显示),回车,即执行。
终端运行后显示查找不到相关路径(终端已授权访问所有磁盘文件) 设备:MacBook Pro(M1) macOS版本:Ventura 13.0, 以及 PD版本是18.0.2 系统语言是中文
输入
sudo bash
空格,然后将script.sh
文件拖进命令行窗口,然后回车。这个文件在“显示包内容” -> Contents -> Resources 文件夹下。 输入你的密码(屏幕上什么都不会显示),回车,即执行。
问题已解决,非常感谢🙏
终端运行后显示查找不到相关路径(终端已授权访问所有磁盘文件) 设备:MacBook Pro(M1) macOS版本:Ventura 13.0, 以及 PD版本是18.0.2 系统语言是中文
输入
sudo bash
空格,然后将script.sh
文件拖进命令行窗口,然后回车。这个文件在“显示包内容” -> Contents -> Resources 文件夹下。 输入你的密码(屏幕上什么都不会显示),回车,即执行。
我悟了,非常感谢你提供的解决方案!!!
sudo bash
Thanks, the problem has been solved.
There was an error in prl_disp_service
after about an hour of running . It seg faulted, complaining that it couldn't talk to service and killed both parallels and running windows.
"Unable to connect to Parallels Service." "Make sure that the prl_disp_service process is active and it is not blocked by Firewall. For details, please refer to this knowledgebase article"
Give this patches said file, is this just an expected issue?
我的报这个
我的报这个
然后我把iTerm也加到了 App Management 里面,重新执行,就好了
现在为了解决兼容性问题,将 app 更改为了 pkg 安装器,应该能通用于各个操作系统了。 我将关闭这个 issue ,如果问题仍存在,我会重新打开它。
To solve the compatibility problem, the app has now been changed to a pkg installer, which should be compatible with all macOS. I'm going to close this issue and will reopen it if the problem still persists.