Recently Browsing 0 members
No registered users viewing this page.
By Rich Woods
Windows 10 build 19624 is now available as an ARM64 VHDX
by Rich Woods
Back in February, Microsoft introduced Hyper-V support for ARM64 PCs, something that was one of the key limitations at the time of Windows on ARM's launch. The only problem was that there was no way to actually spin up a Windows 10 virtual machine, because Microsoft doesn't make ARM64 images available.
Now, that's changing, at least for virtual machines. The firm released Windows 10 Insider Preview build 19624 as a VHDX for ARM64 PCs today, as the Windows Insider team teased yesterday. It probably goes without saying, but you cannot use this with x64 hardware.
There are also some prerequisites. Obviously, the use of Hyper-V means that you'll need to be running Windows 10 Pro or Enterprise. This is worth noting since pretty much every Windows on ARM PC has shipped with Home, other than the old Snapdragon 835 PCs, and the Surface Pro X for Business. That brings us to the next limitation, which is that Snapdragon 835 PCs are not supported. According to the download page, you need a Snapdragon 850, Snapdragon 8cx, or Microsoft SQ1. Presumably, the Snapdragon 8c will be added to this list whenever it comes to market.
Once you've got that done, you can download the VHDX here. If you upgrade your PC from Windows 10 Home to Pro in order to do this, make sure to activate Hyper-V in Settings.
By Rich Woods
Microsoft might release a Windows 10 VHDX for Hyper-V on ARM64 PCs
by Rich Woods
Microsoft has been dealing with some limitations with Windows on ARM since the platform was introduced a few years ago. One of those limitations was the lack of Hyper-V support, something that was recently added in Windows Insider Preview builds, although likely won't ship until about a year from now. There's only one problem though, which is that you actually can't use Hyper-V to create a Windows 10 VM, because there's no ARM64 installation media.
That might be changing though, as was confirmed during the Windows Insider team's webcast today. Microsoft might end up releasing a VHDX that can be used for virtual machines. Of course, the team would only say that it "might" do it, since things that aren't announced rarely get confirmed. But if it happens, it will happen soon.
According to WZor, it's going to be build 19624, which is the Fast ring build from two weeks ago.
If you're looking for a plain-old ISO, that's not as simple of a task as it sounds. Due to the SoC nature of ARM processors, it makes it harder to have built-in drivers in the installation process. If you have something like a Surface Pro X or another ARM64, you'll still need to get installation media from the hardware vendor.
I am new to QNAP devices and not needed to use a NAS device in this manner so this is quite new to me. We recently purchased a TS-883XU-RP to use as our mass storage for our company. The plan is for our Hyper-V server (HP DL385p Gen8) to be the host and connect to the NAS via iSCSI. I have done this and during testing, had no issues at all including being able to copy mass data (~4TB) with no issues at all. However, now it is connected to the live system, I have teamed the NICs and configured the switch for 802.3ad dynamic as per https://kb.netgear.com/000053559/How-do-I-set-up-an-LACP-LAG-between-a-Smart-Managed-Plus-switch-and-a-QNAP-NAS and this seems to work fine.
My issues arise when I try to copy the data from the existing servers to the new VM (although this could be a coincidence). The iSCSI connector drops and cant reconnect due to the Hyper-V host not being able to access servers outside of the vSwitch. Once I regain the connection, I will leave the servers to run with no data transfer to see if the connection drops. To add a little extra info, the other VM's that are held on the Hyper-V server can be connected without issue when I have the problem.
My question is that are there steps that I have missed that can be causing this issue? Is there a best practice that I need to follow and where can i find it?
Edit: Also, the NAS is accessible through the WEB GUI when I have the issue. I am investigating the server to see if htere is a setting I have missed or is incorrect for its NIC teaming/switch config.
By The Dark Knight
New home server build! Low power, whisper quiet and powered on 24/7.
AMD Athlon 200GE based system, 8GB DDR4 RAM, 60GB SSD, 1.65TB HDD storage (1TB + 650GB), Corsair 450W power supply. Onboard LAN plus additional TP-Link NIC, both Realtek chipsets.
Running Windows 10 Pro. Didn't want Linux as a base as I'm just a beginner in Linux. Windows, I know. If anything goes wrong, I can deal with it easily.
Hyper-V configured with 3 VM's as of now - OPNsense for my router, OpenMediaVault for file access and sharing across network and Ubuntu Server. Still figuring out what to run on Ubuntu. Might start with migrating Pi-hole over to this VM from my RPi so that I can use that Pi for something else. Also serving music to my RPi based music player in the living room and any other device via Samba shares. I had initially planned to also host my personal website from home, but after reading about the risks (DDoS especially) I've decided not to and continue paying for professional hosting.
Shout out to @BudMan through whom I got to know about pfSense. Otherwise I would have never known that it was even possible to basically make your own router! I finally went with OPNsense though (fork of pfSense) as I simply love the GUI. Mouth opened and fell to the floor looking at the feature set of these router operating systems! Correctly configured, they can seriously blow the pants off any commercially available home router!
In all my research on the router OS I did see practically everyone recommending Intel network cards as they work very well with FreeBSD (the base OS of pfSense and OPNsense). But so far, I have had zero issues with my Realtek based NIC's. I've yet to stress test the network though, so will then see how these NIC's fare compared to Intel. But currently, only me and my wife are pushing gig on the LAN, other family members usage is very low.
Microsoft updates the Windows 10 SDK with support for WinUI, XAML Islands, and more
by João Carrasqueira
Microsoft announced a series of new features and capabilities for Windows developers at Build 2018, some of which are specifically related to Fluent Design and UWP. Now, those features are finally making their way to developers with the latest update to the Windows 10 SDK. The latest version comes as part of Visual Studio 15.9.1, and it includes a host of new capabilities.
One of those is the Windows UI Library (WinUI), which means developers can access XAML controls and elements through NuGet packages. This means that apps can use modern controls and Fluent Design elements in versions of Windows that didn't originally support them, all the way back to the Windows 10 Anniversary Update. WinUI was made available in preview back in the summer, but it's now out of the testing phase.
UWP XAML Islands are also now available for apps that aren't built on the Universal Windows Platform (UWP), including WinForms, Win32, and C/C++, albeit in preview stage. The feature was announced back in April during Build, and it essentially allows developers to use UI elements from UWP in apps built on older technologies, giving them a more modern look without changing the underlying technology significantly.
This release of the Windows 10 SDK also includes support for Adaptive Cards 1.1, bringing new features such as Media Element and Action Icons, as well as a new visual designer. Adaptive Cards are meant to present dynamic and interactive content in messages, and they were added to Outlook and Teams back in May.
Hyper-V also now allows developers to run an Android emulator with all the latest APIs right inside Windows, though it requires the April 2018 Update (version 1803) or later. Graph Notifications are also now available in preview, offering a cross-platform system for notifications powered by Microsoft Graph. Developers can also now use Project Ink Analysis to create apps that are capable of recognizing ink and making it "more productive".
Lastly, the Windows Machine Learning API is now easier to use because it's the same for both Win32 and UWP apps. It also now has new capabilities including support for ONNX v.1.2.2 models, the ability to convert FP32 datatypes in ONNX models to use FP16, support for Windows Server 2019, and more.