New
#110
Reminder....... CU today for this build. See Shawn's post above:
New Windows 10 Insider Preview Fast+Skip Build 18965 (20H1) - Aug. 21
Reminder....... CU today for this build. See Shawn's post above:
New Windows 10 Insider Preview Fast+Skip Build 18965 (20H1) - Aug. 21
Nothing to be sorry mate as pointed out by @LEAOPEVA64 it is a change in the way feedback hub works.
Hi there
in addition to what others have posted :
I don't think either it matters what you use as as your Virtualisation software -- same type of result whether using HYPER-V, VMWare or KVM -- probably the same if you use VBOX but I've no experience of that. one though.
With Office Pro plus the Visio and Project applications, Photoshop, Kodi, VLC, an ISO from UUPDUMP and some downloaded data my Windows VM is around 18 GB in size (actual physical size on my Host machine) even though I specified an 85GB Virtual disk size -- Virtual disks can be allocated so that they grow when needed up to max size specified. If I discard the UUPDUMP iso and some downloaded data or move it from the VM to host the VM would be approx Kari's size of 11 GB --maybe a teeny weeny bit more (Photoshop and the entire office suite).
Cheers
jimbo
The best part of installing Windows to VHD and booting to it is that no virtualization software is required. Booting natively to VHD means it uses the real, physical hardware of the host. It is and behaves as any physical Windows installation, with only one difference: Windows cannot be upgraded on native boot VHD.
To upgrade my native boot VHDs, I boot to host main OS, create a Hyper-V VM using the native boot VHD as existing hard disk, and upgrade it using UUP Dump ISO. When upgraded, I can again boot natively to it.
When I no longer need a specific VHD, I simply delete the VHD file and remove its boot menu entry.
Kari