Announcing Windows 10 Insider Preview Build 16237 PC for Fast ring Insider

Page 17 of 40 FirstFirst ... 7151617181927 ... LastLast

  1. Posts : 1,524
    Windows 10 Pro (32-bit) 16299.15
       #160

    f14tomcat said:
    @doubtingtom37

    If you're still on 16199, and trying to make the ISO from Kari's tut, there was a known issue in build 16199 that caused input problems. It would just beep. Look at this post from Kari, and get the little fix you will need to get past 16199 error making the ISO.

    TC

    UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 69 - Windows 10 Installation Upgrade Tutorials
    There was also this workaround later in that thread which doesn't require downloading anything:
    KyleStilkey said:
    Hey man, I saw your post on the quick fix you've made to make the CMD/Powershell beep bug work.

    Thought I would shoot this over to you incase there are people out there that don't trust downloading random things off the internet.

    Just right click the command window or powershell window top bar and select properties, then tick the USE LEGACY CONSOLE option and close CMD/Powershell and it will allow you to select options once again.


    Other than that thanks a whole bunch for your tutorials and fixes!
      My Computer


  2. Posts : 119
    Win10
       #161

    @magilla
    Was a bad choice of words, I'm on Creators Update(15063) and trying to update to this build.

    In the last 3 years 11GB of free space was enough to upgrade from build to build, this might not be the case anymore.
    Disk cleanup didn't work, neither the update troubleshooter. I'll try to make more room or make a ISO and go from there..
      My Computer


  3. Posts : 2,832
    Windows 10 Pro X64
       #162

    Hi,

    Jack07 said:
    I gave up, I can't update to this build from slow ring(15063).
    It prepared everything, I have the options to update and restart/update and shutdown. I tried both but it won't upgrade.

    Might be because i only have 11.5GB free space and this update is offloading some files to D: in a $WINDOWS.~TMP directory.. i don't know.
    No, that's not the reason. I was in the same situation because WU re-enabled hibernation again.
    It still upgraded just fine.

    If that second partition is on the same drive and you have a backup drive then image that partition, delete it and expand the system partition. Then you can recreate the other partition and restore your data to it.

    Cheers,
      My Computers


  4. Posts : 4,801
    Windows 10 preview 64-bit Home
       #163

    Took about 4 hours to complete. Showing 100% installed then WU went back to check for updates? Checking installed update history it said I need to reboot to install 16237. Rebooted but still on 16232. This time WU showed the restart tab and it updated OK. Super-fetch and hibernation had to be disabled again but system restore still on at 1%. Not sure if battery indication is working OK yet.
      My Computers


  5. Posts : 3,274
    Windows 10 and windows insider
       #164

    Jack07 said:
    @magilla
    Was a bad choice of words, I'm on Creators Update(15063) and trying to update to this build.

    In the last 3 years 11GB of free space was enough to upgrade from build to build, this might not be the case anymore.
    Disk cleanup didn't work, neither the update troubleshooter. I'll try to make more room or make a ISO and go from there..
    But are you on fast ring, not slow ring?
      My Computer


  6. Posts : 17,661
    Windows 10 Pro
       #165

    f14tomcat said:
    @doubtingtom37

    If you're still on 16199, and trying to make the ISO from Kari's tut, there was a known issue in build 16199 that caused input problems. It would just beep. Look at this post from Kari, and get the little fix you will need to get past 16199 error making the ISO.

    TC

    UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 69 - Windows 10 Installation Upgrade Tutorials
    This note is even in the tutorial itself (step 3.2) simply because I have forgotten to remove it :

    Note   Note
    There is a bug in builds 16193 and 16199 preventing user to select an option in a script like this tool. All that happens when you press 1, 2 or 3 as told above is a loud beep sound.

    If this happens to you, use the temporary fix posted in this post.

    I will remove this notice when Microsoft has fixed the bug in coming builds.
      My Computer


  7. Posts : 155
    Windows 10, Debian Devel, FreeNAS, Zentynal
       #166

    Well

    For the first time I got the boot issue and it was stuck going back into UEFI upon each reboot. I was able to get the GRUB rescue mode shell to come up if I held down the Win Key and F8, however, nothing more.

    The Fix (for myself):

    1. Enable CSM (Compatibility Support Module) in the UEFI.
    2. Select/Choose: 'Other Operating System' vs. Windows.

    It then booted okay & returned my system to the previous build and then it tried to update again and was successful.

    Tim
      My Computers


  8. Posts : 3,274
    Windows 10 and windows insider
       #167

    Fabler2 said:
    Took about 4 hours to complete. Showing 100% installed then WU went back to check for updates? Checking installed update history it said I need to reboot to install 16237. Rebooted but still on 16232. This time WU showed the restart tab and it updated OK. Super-fetch and hibernation had to be disabled again but system restore still on at 1%. Not sure if battery indication is working OK yet.
    So, no error message or anything during the install?
      My Computer


  9. Posts : 119
    Win10
       #168

    magilla said:
    But are you on fast ring, not slow ring?
    I'm on fast ring. I have everything ready to update but when i hit restart it goes through the restart and doesn't update anything..
      My Computer


  10. Posts : 3,274
    Windows 10 and windows insider
       #169

    N9NU said:
    Well

    For the first time I got the boot issue and it was stuck going back into UEFI upon each reboot. I was able to get the GRUB rescue mode shell to come up if I held down the Win Key and F8, however, nothing more.

    The Fix (for myself):

    1. Enable CSM (Compatibility Support Module) in the UEFI.
    2. Select/Choose: 'Other Operating System' vs. Windows.

    It then booted okay & returned my system to the previous build and then it tried to update again and was successful.

    Tim
    Glad you posted this. I had been told to turn off CSM but I left it on. So glad I did--maybe that's why I've successfully upgraded so many times. Thanks
      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 08:25.
Find Us




Windows 10 Forums