New
#20
Downloaded and almost fully installed !!
Marty...already been posted by @Kari that ESD not available. ESD to ISO - Create Bootable ISO from Windows 10 ESD File
Maybe I am misunderstanding something but that's hardly Hyper-V's fault if you have assigned a vm too little RAM. With same logic VMware is annoying, VirtualBox is annoying, Parallels is annoying and so on; a vm running on any virtualisation platform would give that same message if trying to install Windows 10 on a vm with less than 2 GB of RAM.
You get the same message if trying to upgrade a Windows 7 physical machine with 1 GB RAM to Windows 10.
I only have 40GB of unused space on the SSD to give to My VM. After cleanup the last build 15058 took up 14.6Gbs of it. The download was a little over 2.8GB. When I tried to upgrade I ran out of Disk Space ? Cleaned out the download and tried a second time with the same result. Think I'll sit this one out
I know, I just rebooted and it worked. I didn't assign anything in particular. It had wound itself down to 780MB as I wasn't using it.
I like dynamic memory - it is convenient - but a bit slow to respond to demands sometimes. I don't really know how other hypervisors do dynamic memory. Presumably they do it but I don't use them much so I wasn't making a comparison.
Just funny MS should ask me to talk to my PC manufacturer (which is MS of course).
Upgrade install is one of those rare occasions Hyper-V dynamic RAM cannot cope (or any other virtualisation program using dynamic RAM). If minimum RAM is set below 2 GB (default = 512 MB) and at the moment when WU checks if there is enough RAM for upgrade the available RAM has fallen below that 2 GB, there's no way WU is able to send a message to Hyper-V to increase dynamic memory and recheck.
Updated very smoothly to the new VM-WIN10-15060u with UUP. I took me ~ 60 mins to complete this update sequence:
- copying VM to newer build number -> VM-WIN10-15060u
- changed drive-name -> VM-WIN10-15060u C:
- changed network adapter ip-address - 192.168.2.60
- changed computer name and rebooted - VM-WIN10-15060u
- started the update and download
- created an ISO with the UUPtoISO tool
- copied the ISO to my NAS
- finished the update by using the update and restart in startmenu > restart/shut down option
Getting more and more used to the above created workflow - to keep better track of builds in VM's by changing some names/digits in accordance with the last 2/3-digits for the new build e.g. /060 - for each update.
Up-and-running. Playtime!
Cheers
Last edited by M4v3r1ck; 16 Mar 2017 at 20:07.