Announcing Windows 10 Insider Preview Build 15060 for PC Insider

Page 3 of 11 FirstFirst 12345 ... LastLast

  1. wen
    Posts : 273
    WINDOWS 10 PRO INSIDER PREVIEW
       #20

    Downloaded and almost fully installed !!
      My Computer


  2. Posts : 659
    10 preview 64bit
       #21

    fastest D/L for me ever 1.30.

    Roy
      My Computer


  3. Posts : 56,824
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #22

    martyfelker said:
    Attachment 125423


    These VMs (VMware and Virtualbox) had just been updated to build 15058!. Need to update Virtualbox to 3.18 on Windows Server 2016. Then copy all VMs to Linux. Last deal with my physical Windows 10 which is still at Build 15055. I'll probably do a clean install of 15060 which I should get as a ESD on the VMware VM.
    Marty...already been posted by @Kari that ESD not available. ESD to ISO - Create Bootable ISO from Windows 10 ESD File
      My Computers


  4. Posts : 5,478
    2004
       #23

    Hyper-V is really annoying... No memory, no memory... Don't you know what dynamic memory means?

    Announcing Windows 10 Insider Preview Build 15060 for PC-nope.png
      My Computer


  5. Posts : 17,661
    Windows 10 Pro
       #24

    lx07 said:
    Hyper-V is really annoying... No memory, no memory....
    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.
      My Computer


  6. Posts : 1,937
    win 10 Insider
       #25

    Smooth update once again. I like boring!
      My Computers


  7. Posts : 936
    xp
       #26

    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
      My Computer


  8. Posts : 5,478
    2004
       #27

    Kari said:
    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 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.

    Announcing Windows 10 Insider Preview Build 15060 for PC-capture.png

    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).
      My Computer


  9. Posts : 17,661
    Windows 10 Pro
       #28

    lx07 said:
    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.
    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.
      My Computer


  10. Posts : 633
    Win 10 Pro x64 1607 (Build 14393.953)
       #29

    Announcing Windows 10 Insider Preview Build 15060 for PC


    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.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:02.
Find Us




Windows 10 Forums