I did it in a virtual box machine with windows 10. Keep in mind that to be able to get access to a USB device in the host you have to add your user to the vboxusers group. I also had to install the virtual box extension pack (available in the AUR for arch users https://aur.archlinux.org/packages/virt ... xt-oracle/) to enable support for usb 2.0 and 3.0. If everything goes well you should be able to select the nord USB device as shown in the following image.
After that I installed the driver and the sound manager. Being able to see all my programs in the sound manager gave me the confidence to proceed with the OS update. I opened the update OS utility, which recognized that my current version was 1.02, and then clicked updated. My nord stage rebooted and then everything went to black. After rebooting everything froze and the update utility din't show me the progress bar as it supposed to. I started crying and questioning all the decision I made in my life. After a minute lying in the ground thinking what to do with a 4 thousand dollars set of transistors I started to calm down. When I was deciding if I should disconnect my nord or keep waiting I realized that the USB device was disconnected from the virtual machine and when I connected it again the update utility started to show the progress bar. After the updated finished the USB disconnected again and I had to connect it for the update utility to say that everything was done.
After some though the behavior wasn't strange at all. When the update process starts and ends the nord reboots, meaning that the USB connection is lost. Because I haven't vbox configured to automatically connect the device to the VM the software kept waiting for the nord to reconnect. The same should happen connected directly to a machine. I assume if you add a filter to vbox to automatically connect the device everything should go smoothly.
That's my story
