So many problems that have been around for months

I have seen these issues in posts since October 2021. It is now May 2022, and as near as I can tell, I have the most up-to-date possible computer and system currently:
M1 Max, 16" 2021
Monterey 12.3.1
Parallels 17.1.2
MacOS VM 12, just downloaded last night.
Parallels Tools installed on both the host and the virtual.
Everything is fresh install as of two days ago at the latest, as the computer is new.

I have the following issues that are obvious, and I am sure that there are more:
*No drag/drop capabilities
*Only resolution possible is 1440x900
*Right-click via two-fingered trackpad click does not work; control-click is okay, but annoying
*Non-obvious whether Parallels Tools is installed on the VM
*Cannot sign in with AppleID -- even tried to create a new AppleID and all I get is "This action cannot be completed"
*In previous versions of Parallels there was a VM "configuration" set of preferences, where one could change things like cores used, RAM limits, how to connect to networks, and more; I can't find that ANYWHERE I look within Parallels.

Not that these are bugs, but what with the new architecture, I can't even run my old Windows7, Snow Leopard, or even Big Sur VMs? Unfortunately, at the moment, the Monterey VM, Parallels istself is useless. It might be worse than useless, as it has taken up my time, and so far is just a waste of my money. My user satisfaction with Parallels on an M1 mac is EXTREMELY low. If they can't put out a product that works, they shouldn't put one out at all. Either that, or CLEARLY advertise that they ONLY way you can use Parallels 17 on an M1 Mac is to run Windows 10 or Windows 11. I NEVER would have purchased the upgrade had I known.

That said, here is me giving them the benefit of the doubt: does anyone have fixes for the things listed above? I have uninstalled, reinstalled, cleared caches, restarted Host and VM, all multiple times, but to no avail.

 

Thank you for your reply. I am glad to see at least some of those things at least partially addressed. But seriously, if all it takes for changing some of those things is editing a text file, then there is NO reason why Parallels cannot do that either within its own program or by creating a small secondary app to do it.

Also, I SUPPOSE I may have missed it, but with 16 previous versions that some of us have had, there should be HUGE, OBVIOUS, FLASHING warning signs that Parallels 17 is *barely* partially implemented on M1 machines with respect to MacOS virtualization. I mean really, why even allow it to be purchased at all... other than to fleece their users. It would be like selling a car, but oh yeah, the windows don't roll down, the brake lights only work if you're looking at them, and although air bags are included and we're aware of the issue, they're not actually operational at this time. But feel free to buy it, because we're not actually going to warn you about these major things, even though every car we've sold you in the past has had them work; we're just going to assume you will read the fine print.

Sigh. Catch me ever buying Parallels again. With sales like this, who needs enemies?

 

Hey man, please drop the BS "woe is me" and "I'm so disappointed with Parallels" routine. No one is "fleecing" anyone, and clearly you have some ulterior motive to this post.

I've been using Parallels on Intel for 10 years and on an M1 Mac for almost 2 years, and it works fine. Everything you're complaining about is basically wrong. The product works as advertised and all the settings are, in fact, easier to find and change than ever.

Are there still some bugs? Of course - it's software ...

Do I wish that a decision to license Windows 11 ARM on M1 processors would be made? Yes - the sooner the better since I plan to transition everyone in my company to M1 Macs running Parallels, and that's all I'm waiting for.

 

I'm confused as to what ulterior motive I could possibly have. If nothing else, I'm just an end-user who is not associated with any business related to technology, or that even uses technology beyond a TI-30x calculator.

But while we're at it, how does it make configuration "easier to find and change than ever" when we have to go through an entire process like creating a .config file in the Terminal and then editing it in Simple Text or BBEdit?? Have you seen https://kb.parallels.com/128867, where PARALLELS itself specifically says "There is currently no interface to adjust macOS ARM VM configuration?"

You know, when it comes to YOU telling me that it is easier than ever to set configurations, or when it comes from my own experience AND Parallels itself telling me that there is no easy way to do it... I think I'll trust me and Parallels.

Let's be honest: it is not *I* who have some sort of ulterior motive, but it is the one who is lying about "easy configuration" who has the clear ulterior motive. Duh. #SoStoopid

<benefit of the doubt revoked>You know, I could give you the benefit of the doubt that you didn't actually read my posts where I CLEARLY expressed that I am speaking as to the way Parallels handles a MacOS VM... but 1) I am only hypothesizing that you can, actually, read, and 2) with the amount of venom in your post, you must be worked up about SOMETHING... and if you didn't read my actual posts, how could you be that worked up?</benefit of the doubt revoked>

Get a grip, dude.

 

I'm with Nandor, Parallels is not fit for purpose, especially macOS virtualisation. Their advertising is duplicitous at best. No snapshots, late to the party and hidden configuration is just poor. And it's not like 'normal' software with some bugs, this is missing essential functionality. I'm not against Parallels coming out with the silicon version, I am against them pretending it's fit for purpose.

 

Your definition of 'works fine' seems to be somewhat different to mine:

Here is a list of key features that are either not supported or not fully supported in macOS ARM VMs.

1. macOS VM works only on Mac computers with APFS disks, and running more than two such VMs simultaneously is impossible.
2. Enable/disable SIP: supported for macOS Ventura virtual machines only starting with Parallels Desktop 18. You can start your virtual machine and press the Option key, or right-click the VM name in Control Center and select Start in Recovery Mode. Additional information can be found in KB 129232.
3. Suspend and Resume: Not supported yet.
4. Configuration: There is currently no interface to adjust macOS ARM VM configuration. However, the configuration can be adjusted manually, as described in KB 128842. Please note that available options are rather limited. I.e., it's not possible to change things like UUID, MAC address etc.
5. Snapshots: Not supported yet.
6. Shared folders: File sharing between the main system and a macOS ARM VM is not supported. This includes consequential features such as drag-and-drop. However, you can share files between the virtual machine and the Mac using the native macOS file sharing feature.
7. Virtual Wi-Fi adapter: Similarly to Windows virtual machines, there is no virtual Wi-Fi adapter in macOS ARM VMs. Your Mac internet connection (wired or wireless) is accessed by the virtual machine through a virtual Ethernet connection.
8. USB devices: It is currently not possible to connect any USB device to a macOS ARM VM yet.
9. Disk size: macOS ARM VM's disk size is 60 GB by default. It can be set to a different value during the manual installation process (see KB 125561), but once the virtual machine is created, disk size cannot be changed.
10. Mac built-in devices: A macOS ARM VM has only access to the main system's mouse and keyboard (or rather their inputs), and other devices such as DVD drives and webcams are not accessible to in macOS ARM VM.
11. Startup options/recovery mode: It is currently not possible to access startup options in a macOS ARM VM, and as a result -- access many options that it provide such as recovery mode, safe mode etc.
12. Command-line interface (CLI) and SDK (partially addressed in Parallels Desktop 18):
Note: Parallels Desktop 18 introduces partial support for CLI (prlctl start, stop, register, destroy, clone).
A macOS ARM VM cannot be accessed through Parallels' prlctl and prlsrvctl command-line tools or through Parallels SDK. And there is no Vagrant support yet.
13. Apple ID: It is currently impossible to sign in with your Apple ID in a macOS ARM VM.