Parallels Macbook
Laila Berri
FWIW, the standard Windows 11 installer download will work for installing on an ARM platform like Parallels on an M1/M2 Mac. I have done it on my M1 MacBook Air. I have a few Intel apps in the VM and they seem to work fine, just don't expect to do any gaming which is pretty much true in any VM whether the machine is Intel or ARM.
Also, the standard installer does not have the Microsoft Store and the base apps but you will be prompted to download them after the install, unless updates to win11 have changed that since I installed.
"Will Parallels Run on 15" MacBook Air?: My daughter is considering a Mac that she'd need to also run Windows on for certain work-related tasks. Is the MacBook Air capable of running Parallels in order to run Windows applications on it? (Not sure if it has enough horsepower, but don't want to recommend a MacBook Pro if it's not needed)."
It would work, as long as system requirements are met. If you run items in the back ground, while using the Vritual Machine, then I recommend 12GB or more of RAM. Note that RAM (Random Access Member) is meant for multitasking. So, the more RAM the betters, when it comes to running lots of apps.
Running Windows in a virtual machine will chew up RAM. (There's the overhead of running two OSes at the same time.) If you go this route, you will probably want 16 GB or 24 GB of RAM on that 15" M2 MacBook Air.
The other issue is how well Windows for ARM will work. Most off-the-shelf WIndows applications are built for Intel and AMD CPUs (only), and if WIndows for ARM can run them, there will be emulation or translation overhead.
It runs windows and any app just perfect. I am a network engineer, from experience, I run parallels in transparency mode almost all the time when working on customer sites, and I suggest MORe than 16gb of RAM if you are regularly running both the MAC OS and windows side by side.
For instance, Windows for ARM can't run Intel-only device drivers. This is similar to how Rosetta 2 can't run Intel-only kernel extensions. Also, features that use nested virtualization (like the Windows subsystem for Android) are not available.
Hello, If this has been brought up already I apologize! New to the CNC world, ordered and elite Forman and my questions is am I better off buying a PC with windows to run Vcarve Pro or just use my current MacBook Pro with parallels to run it. Any advice would be greatly appreciated.
I run Vetric under Parallels and it works well (Intel based iMac). Some of the keyboard commands can be a little odd, but overall no problem. Since you can test drive Parallels for a couple of weeks, try both in trial mode and see how you like it.
I can install Ubuntu 13.10 in parallels ok and then log in. Problem is Ubuntu does an update and I get black screen / desktop such that I can't see any app windows that I open. I've tried a few of the other suggestions and they don't work for me.
Same problem here with a MacBook Pro. Here's what worked for me after I updated 13.10 and received a black screen, although the toolbar on the left was showing. It was simple, but I don't know why it worked.
This just happened to me, with Mavericks, Parallels 9.0.24172, Ubuntu 13.10 and updates installed on 1 Mar 2014. On reboot, I could see the login screen, then after logging in, I could see the Unity "Launcher" or whatever the call the row of icons on the left, but the rest of the screen was black. If I click to start any apps, like Firefox, the icon in the bottom of the Parallels screen indicate that the re is disk activity as the app starts, but the screen remains black.
Just before I installed the Ubuntu updates, Parallels Tools had reinstalled itself, due to a new version of the Tools since I last used the VM, but it seems that certain kinds of Linux updates break the video driver. As stated above, always make a Parallels snapshot before running Ubuntu update, just to be safe.
Shut down the Ubuntu VM (13.10)In Parallels 9 config for the VM, go to Hardware > Video, and disable 3D acceleration.Restart Ubuntu 13.10. You will now get a completely black screen.Shut down the Ubuntu VM once more.Again, in Parallels config for the VM, go to Hardware > Video and reenable 3D acceleration.Restart, and you're back in business (No black screen and everything properly updated).
I have have read numerous community posts and searched Victron information manuals, reinstalled the configure tools, rebooted, updated, set the USB drive, tried through VE Configure 3, tried numerous ports, tried through apple terminal, tried through windows many times and no luck.
Delete the Victron USB Files, they need to update them, the same files can be downloaded from the FTDI chip manufacturer, Don't forget to download this version (or later) of the FTDI, then it works, i.e. DO NOT click on the here link find the ARM64 signed distributable in the table, see below for link: website = -drivers/
Then go into device manager and update the drivers, remember where you download the 2 files in the zip, either update against the unknown MK3 device or use the 2nd to right menu icon in Device Manager to add drivers, then it works, but you must have the correct link above
When following the instructions above from Mathias - there are numerous folders and files in the folder USBDrivers ... do I select the whole folder or a specific file inside that folder?? I have tried both ways and reinstalled many times. The time wasted now is considerable.
Then I deleting mine from windows. (control panel devices and printers) Then replugged it. Just worked as expected. Guess you can't see it in the control panel or device list, mine came up on USB port COM3.
Unfortunately the new Mac M1 processors are ARM based and not intel, therefore it does not run standard windows 10 or windows 11 inside Parallels. What you are running is a version of Windows 11 compiled to run on the ARM processor, and I believe still beta/early adopter status. What Microsoft calls Insider Preview,
While 9 times out of 10 most users will not find any issues, there are corner case when things do not work as expected or at all. Especially when related too low level drivers. At this stage there are no released low level drivers for the serial interface inside the MK3 which will load and install on Windows 11 ARM.
I have managed to get hold of a beta set of drivers, which I shall be testing this weekend. I have been informed others have had success running the drivers inside Parallels, but they have not formally tested it.
However you will need to request them from the supplier (FTDI) direct, and agree to no onward distribution of the drivers. A search of the net will also find instructions, What has been supplied is about 2 or 3 release behind their released drivers so no idea what may or may not work. They are working on a formal release, but unlikely soon.
You need to go through the process of disabling driver signing. lots of examples on how to do this on the web. Then install the drivers, edit the registry, remove the USB adapter, re-insert the USB adapter and re-install the drivers.
Thanks @Bathnm for the detailed answer, that explains a lot. So I reinstalled everything on my old intel based macbook and it seems like its working, at least Windows is now recognising the MK3 device. Have yet to get back on site to confirm.
The work around is to open the Windows Device Manager then click the "Add Drivers" icon at the top of the window. Point it tto the ARM driver downloaded from -drivers/ and it will install the drivers and then it works.
Thanks for the information in this thread - I got really frustrated after trying stuff for hours before reading this and actually went and bought the cheapest Windows laptop I could at Wal-Mart to get the job done, which I'll now be returning. Many of those hours were spent with me not realizing that the MK3-USB adapter I had wasn't working because the mini-USB connector had broken loose from the circuit board inside...I had to open it up to realize this and then order a replacement, which now comes with a built-in USB-A cable. The *real* solution would be for Victron to add assistant support to VictronConnect, and/or to release a MacOS version of VE.Configure, and/or at a minimum update their USB Drivers included with VE.Configure to include a driver for Windows on ARM.
I am running Windows 11 for ARM using UTM (free) on MacOS 13 (Ventura) on an M1. It works surprisingly well - much faster than any native Windows laptop I've seen including ARM ones. When the virtual machine is running and you plug in the MK3-USB, it nicely just pops up and asks if you want to connect it to the virtual machine. You don't need Windows Insider Preview anymore - the regular released version now has everything. VE.Configure installs and works just fine, but as mentioned, ignore Victron's USB Drivers for now. The thing to realize about the Device Manager is that there are actually two different devices that need the driver updated. I think the second one only shows up after the first one is updated. This same thing happened on the Windows 11 laptop using the Victron drivers so may be a Windows 11 thing. I really don't use Windows at all in many years except when needed for very rare situations like this, so somebody else may know better, but if you've updated the driver once and it's still not working, know that there's a second device that also needs updated. Both will show up as MK3-USB Interfaces, though after updating to use the FTDI driver, it shows up simply as USB Serial Port. Doesn't matter to VE.Configure, it works after this is done.
Now that I've had the fun of buying two Victron-branded MK3-USB devices due to the first one failing, I have to wonder if I couldn't have saved money buying an FTDI device directly or from some other vendor using the same chip, and maybe even gotten a modern USB-C plug directly on the thing. Anyways, I digress...thank you for posting the FTDI driver link!