Separate names with a comma.
Discussion in 'Parallels Desktop for M Series Mac' started by kundanno, Jun 23, 2021.
Thanks, will give that a go. My search skills clearly aren't what they used to be!
Thanks, but there aren't such drivers ...
Yeah, unfortunately driver support for Windows on ARM is lacking. Not many device manufacturers offer them.
Hi, I use Parallel on my MacBook Pro M1 (16GB) with Windows 11 Insider, but everything is very very slow since 1 month, especially with x64 applications. I use only 2 x64 applications, sometimes can take 15 minutes to open an x64 application ! Win CPU always at 100% when MacOS CPU is at 15/30%.
Win11 high usage is many time : System, Explorer...
The build is Win11 Pro Insider Preview 22543 / 220122-2315.
Parallel settings are CPU/RAM : Auto, Graphics : Scaled.
Did you encounter same problem?
Go to System Preferences > Spotlight > Privacy and press the + sign and add the folder where your VMs are stored.
This helped a lot for me.
Does anybody have issues with interference/crackling from the speakers in Windows 11 on ARM? Its not happening in macOS, just in Windows, even when there's nothing playing, just random crackles!
I do hear. it occasionally - usually when certain games are playing sound effects - but not constant or often enough to be really annoying.
I've had to start using Teams for some work I'm doing and the audio was a bit crackly on there compared to the Mac version so I'm wondering if its related.
I was about to return Parallels Desktop - very slow. This fixed it. Thanks!
I keep my VMs on a separate Volume that I can easily exclude from snapshots etc. I periodically back them to my NAS with ChronoSync and to a disk with CarbonCopyCloner.
Hello all, I have been reading through everything I could find about installing Parallels 17 on my M1 iMac. I think I'm ready to take the plunge, but have one question that I couldn't find an answer to. It looks like Parallels is updated about once a year. If I purchase Parallels 17 now, would a new version be out in about 5 months from now that may require me to purchase an upgrade to continue running Win 11 on my M1 iMac? Sorry if this has been answered before, I'm a total newbie to this.
[QUOTE="CG_7, post: 901404, member: 6778924"It looks like Parallels is updated about once a year. If I purchase Parallels 17 now, would a new version be out in about 5 months from now that may require me to purchase an upgrade to continue running Win 11 on my M1 iMac? Sorry if this has been answered before, I'm a total newbie to this.[/QUOTE]No. If you buy outright, version upgrades are only available for about two months after the sale using their typical Tech Guarantee - at least that's what it was last year. You will qualify for upgrades, which were $49.99 last year.
My three Pro licenses are subscriptions. I use them a lot including for work, so it is worth it. For more than a decade I used VMware products with more liberal license policies, but Parallels has left them in the dust.
A new major version gets released once a year sometime before the new macOS gets released. I think Parallels 17 was released last August, so you can expect Parallels 18 around that time this year.
Parallels 17 will still be supported after that, but it probably won't be fully compatible with the next macOS.
If you buy Parallels Standard, you can't upgrade to Parallels 18 for free, but you will get updates for Parallels 17and can use it for as long as it works. You're also limited in the amount of RAM and CPU cores you can assign to a VM. This is not a problem for Macs with M1, but could limit your options with M1 Pro/Max/Ultra.
Parallels Pro is a a yearly subscription that allows you to upgrade to the newest major release. It's probably the best option if you plan to upgrade to the next macOS.
I had a similar problem with networking on Windows 11 ARM edition running under Parallels 17. The culprit for me was that IPV6 needed to be disabled somewhere in the Windows Settings for Network connections. Hope this helps.
I recently purchased an Epson WF4830 Inkjet Multi Function Printer. Bad Mistake - the drivers for the Mac are cut down versions compared to the Windows version. The drivers WILL NOT INSTALL in Windows 11 ARM edition and upon contacting Epson Support, they said they HAVE NO PLANS TO SUPPORT WINDOWS 11 ARM edition.
I also purchased Logitech MX Keys Keyboard for Mac and Logitech MX Master 3 Wireless Mouse for Mac recently - drivers (or what Logitech call their Logi Options +) software installed and runs ok on the macOS side, but once again WILL NOT INSTALL on Windows 11 ARM edition - meaning that all the bells and whistles of these products WILL NOT WORK IN WINDOWS 11 ARM edition. I see this as a huge step backwards in Windows usability and compatibility on the Parallels platform. But who do we blame? Both Epson and Logitech seem to take the easy way out and state: "Our products are not meant to work in VM's". Ah yeah....bullsh*t! They should work. Do we blame Apple for arming their new machines with "M" series processors that no longer support X86/X64 versions of Windows? Or do we blame the peripheral manufacturers for being too lazy to produce Windows 11 ARM drivers/software.
To me, this whole problem doesn't seem like an easy one to solve. I wanted all the benefits of the new "M" series processors when I purchased my 2021 16 inch MBP (with M1 Pro Processor) *boy that's getting a mouthful*, but as for Windows compatibility, these new "M" Series Macs are problematic from a Windows driver point of view. So many devices simply won't work to their full capability because of the lack of suitable Windows 11 ARM drivers. It reminds me of the early 90's when I had to beg different printer/device manufacturers to build drivers for the Commodore Amiga computer. You basically had Buckleys and None chance of them doing it. Lots of manufacturers just
won't invest the money required to create drivers for Windows 11 ARM because they think it will not be popular enough or used widely. A sad state of affairs indeed.
There has been a problem between Comcast as the ISP and Netgear routers, at least the Orbi mesh ones - IPv6 connectivity would drop - the Netgear router showed it had an IP for v6, yet the online IPv6 tests would show no IP address. I suspect the system would start to fail in networking activities because it seems v6 may be the default if both v4 and v6 are operational - and Windows thought both were running ok. For me, Windows laptops on our network stopped working on the network, yet for some reason Macs seemed ok. It could drop network connectivity anywhere from several hours to 3-5 days after getting a new IP address. Once this happened, IPv6 would stay down until a manual intervention re-established the IP connection - on a Netgear router, setting it on "Auto Detect" or DHCP for Comcast, apply, and a new IP address was established and things ran again. This was not really a Parallels issue, as people saw this in a number of forums that were not running Parallels VMs (reddit, netgear, DSL reports being a few of them where the problem was reported).
IMHO the problem happened on lease renewal between Netgear and Comcast - the Netgear router thought it had a good renewed IP address, Comcast did not. That's just a hunch though.
In my case I have the Orbi RBR850 mesh router, and its latest firmware update, 188.8.131.52, which came out around June 22, appears to have fixed this. I have been running IPv6 since June 23, almost 13 days now, with no interrupts in IPv6. Maybe this situation is what you are facing?
This needs to be a sticky! Thanks for this!!
I also have a NetGear Orbi setup, however it's the RBR750 with the same firmware. I also enabled email logging (see Netgear forum), appears to fix a bizarre bug as this apparently clears logs that fail to clear otherwise and cause occasional dropouts/reboots of the WiFi service.
Between the new firmware and the email logging being enabled, I've had solid networking experience in Windows 11 under Parallels.
Totally agree! However, I don't blame Apple nor Parallels. I do blame Microsoft/Qualcomm for their exclusivity agreement for the Surface Pro X ARM edition being the only OEM source of Windows 11 ARM for so long. I'm seeing a few other Windows 11 ARM systems now, so the exclusivity has expired. Not a compelling large enough market base for device developers. I remember how long it took to get new drivers for some of my devices during the Windows XP to Vista and newer Windows OS releases. Also many were likely put off by the much older Windows R/T way back.
However, I'm amazed with what does work with Windows 11 ARM and hopefully the market share will continue to increase. Until enough customers petition these device driver developers at the different vendors, likely it will continue to be an issue. If Metal 3 API (currently in beta with macOS 13) does a great job and brings the better ability to provide DirectX12 compatibility, I expect Parallels deployed versions of Windows 11 ARM will help that market base to grow. Especially considering how well the base M1 performed Windows 11 ARM via Parallels compared to Microsofts/Qualcomms own SQ1 and SQ2 SoC's. That's impressive and promising enough for me to stick with it despite device driver frustrations.