Announcing Windows 10 Insider Preview Build 15061 for PC Insider
-
In Linux. Copied Virtualbox and VMware VMs from Windows Server 2016. 3 Virtualbox VMs in the process of updating to 15058, 15060 and 15061. VMware is working now with Fedora and Kubuntu VMs. Only so much you can do with 32GB of memory :)
-
-
Wow--we--wow--wow--wow! Too much too soon. Should we need some time to evaluate each build?
-
Aren't we testing for upgrade problems?
Edge works better for me now but I see advertisements I don't get when I use the IE.
-
On desktop, took 3 attempts to finally get installed. On laptop, installed without problems. Both UUP installs.
-
-
Wasn't expecting a build today, so when my computer notified me that it was ready to restart and update, I had to stop everything I was doing and start preparing.
VM still won't update from 15058 so I'm killing it and making a new one. Laptop is downloading, and this desktop is ready to install, so I'm making .ISO and install.wim before letting it run overnight.
-
In Linux. Copied Virtualbox and VMware VMs from Windows Server 2016. 3 Virtualbox VMs in the process of updating to 15058, 15060 and 15061. VMware is working now with Fedora and Kubuntu VMs. Only so much you can do with 32GB of memory :)
Ha. I'm on 12 GB on my Windows Desktop - I just assign 4 GB to each VM and don't let more than 2 run at a time lol.
-
Actually having 5 or more VMs running is fairly unwieldy. My standard is to assign 2GB to each VM unless I;m running a VM which was created by virtualizing my physical hard drive in which case I assign at least 8GB and even 16GB for performance reasons. Hoping for a slowdown on Insider builds. 3 per week is too much.
-
Announcing Windows 10 Insider Preview Build 15061 for PC
My standard is to assign 2GB to each VM unless I;m running a VM which was created by virtualizing my physical hard drive in which case I assign at least 8GB and even 16GB for performance reasons.
Hi Marty,
Exactly the same protocol I'm using for my 'bare-metal' SSD-WIN10-14393u workflow drive.
- 8/24 GB RAM
- 6/12 CPU CORES
Standard test-VM's like all Windows 10 IP's get 4/12 CPU CORES and 4/24 GB RAM.
As I'm a hybride macOS and Windows user, I mostly fire up this 'VM' to do some light-weight PC/administrator work and of course the Windows 10 updates. While updating Windows I can stay on the macOS side working on my projects. After each update I use Winclone to make a fresh clone to my NAS.
When I'm in need of some serious hard-core-hardware - flight sim or video editing - I switch to reboot the 'bare-metal' SSD-WIN10-14393u.
EDIT: For those of you who might ask, why the heck is an Apple Mac Pro user doing his video editing in Windows 10?! [emoji15]
I've set-up an alternative Windows 10 video-editing workflow with Cyberlink Power Director Suite 5. Just in case Apple goes nuts and kills the pro line-up for the Mac completely, at least I'll be ready by having created an already converted to Windows workflow. [emoji41]
Cheers
Last edited by M4v3r1ck; 18 Mar 2017 at 02:11.
-
With me, it's:
- 4 /12 GB RAM per VM
- 2/4 cores (technically it says I have 8 cores, but 4 are virtual thanks to hyperthreading, so I keep it at 2 instead of 3 or 4 per VM).
Of course, I'm also on a much older system. Core i7 965 EE (1st generation Core i7) and 12 GB of triple-channel RAM (3 * 4GB ea). I've toyed with matching that set with another identical set, boosting me to 24 GB, but at this point, I think the better investment is going to be a new CPU / mobo / RAM, although that is also a lot more costly.
I'm trying to get a reliable Android Marshmallow+ install in a VM as well, so I can relegate some of the game crunching tasks off my phone for one particular game that requires a lot of grinding, but I haven't found one that works well (yet) in Hyper-V and isn't completely choppy with mouse usage.
And, of course, none of my VMs are up when I am gaming.
-
-
with 15060 no problem.. when installed 15061 error memory management blue screen.. anyone? ..