Announcing Windows 10 Insider Preview Fast Build 16294 for PC Insider

Page 13 of 20 FirstFirst ... 31112131415 ... LastLast
  1. magilla's Avatar
    Posts : 3,118
    Windows 10 and windows insider
       #120

    blackroseMD1 said:
    Yeah, I had a failure to install message for the Nvidia driver while the new build was waiting for restart. Once I restarted and the new build installed, though, the new driver was there as well. No big deal, as I just ran DDU and returned to the older driver, but still a bit annoying.

    Happy birthday!



    Awesome. Thanks for the heads up!
    Thanks for birthday wishes @blackroseMD1
      My Computer

  2. cereberus's Avatar
    Posts : 12,013
    Windows10
       #121

    slicendice said:
    Interesting!

    How do you explain that I could successfully upgrade Windows x64 Pro EN-US Build 15063.0 on a 20GB drive (Windows minimum requirement for a 64-bit installation) to Build 16294.1?

    My Windows.old ended up on the additional 16GB drive, I plugged in, as a WIM-file.
    Never happened on my 32bit tablet - just gives up saying not enough memory and that is with 32GB usb stick fully empty plugged in.

    What use is windows.old on another drive anyway unless system is designed to rollback from that?

    Have you actually tried rolling back to see if that works?

    I have actually upgraded a 64 bit tablet by making macrium image, using viboot vm on pc to upgrade, use disk cleanup, create new image backup, and restoring.

    I could never get that to work with 32bit as Hyper-v does not seem to be able to handle 32bit UEFI.
      My Computer

  3. slicendice's Avatar
    Posts : 4,644
    Windows 10 Pro x64 20H2 Build 19042.906 (Branch: Release Preview)
       #122

    cereberus said:
    Never happened on my 32bit tablet - just gives up saying not enough memory and that is with 32GB usb stick fully empty plugged in.
    Are you sure it's referring to disk space? Was the 32GB stick formatted as NTFS? Sounds to me that the OS ran out of RAM if the error message used the word Memory​.
      My Computers

  4. slicendice's Avatar
    Posts : 4,644
    Windows 10 Pro x64 20H2 Build 19042.906 (Branch: Release Preview)
       #123

    cereberus said:
    Have you actually tried rolling back to see if that works?
    Nope, but I will try that tomorrow, as it's late here. I doubt there will be any issues though.
      My Computers

  5. slicendice's Avatar
    Posts : 4,644
    Windows 10 Pro x64 20H2 Build 19042.906 (Branch: Release Preview)
       #124

    cereberus said:
    Have you actually tried rolling back to see if that works?
    slicendice said:
    Nope, but I will try that tomorrow, as it's late here. I doubt there will be any issues though.
    What the heck, rolling back was just a few clicks away so tried it too.

    Worked like a charm, except I am on 15063.608 now :)
      My Computers

  6. cereberus's Avatar
    Posts : 12,013
    Windows10
       #125

    slicendice said:
    Are you sure it's referring to disk space? Was the 32GB stick formatted as NTFS? Sounds to me that the OS ran out of RAM if the error message used the word Memory​.
    Bad words - I meant disk space.
      My Computer

  7. slicendice's Avatar
    Posts : 4,644
    Windows 10 Pro x64 20H2 Build 19042.906 (Branch: Release Preview)
       #126

    cereberus said:
    Bad words - I meant disk space.
    OK, was just checking.

    Did you know that there is a minimum free disk space requirement for running Windows reliably? Also Windows supports upgrading when there is at least 8-9 GB free space (I don't remember the exact bytes).

    I guess I have to try 32-bit Windows next on an even smaller drive to see if it eats my carrot too. :)
      My Computers

  8. cereberus's Avatar
    Posts : 12,013
    Windows10
       #127

    slicendice said:
    What the heck, rolling back was just a few clicks away so tried it too.

    Worked like a charm, except I am on 15063.608 now :)
    Interesting. Now that is what I like - "proof of the pudding ".

    I suppose for this to work, usb drive would need same drive letter associated?

    I wonder if MS have updated rollback mechanism with CU. It certainly never worked on earlier versions but they did add ability to use usb for temporary storage back at 1511. I will try again when I get a spare moment and report back.

    I cannot imagine this would not work on 32bit.


    As a separate aside, my favourite tablet app, touchmousepointer fails on Insider versions which rather puts me off upgrading even though I want 'Onedrive Files on Demand'. I use junction links so my onedrive subfolders point to data folders on my sd card instead.
      My Computer


  9. Posts : 2,764
    Windows 10 Pro X64
       #128

    Hi,

    I suppose for this to work, usb drive would need same drive letter associated?
    Nope, W10 hardly relies on drive letters if at all. It can put Windows.old on a different partition or drive IME.
    No idea if they (MS) documented this somewhere though.

    I've also seen it write part of the installation files to a different drive as well.

    Cheers,
      My Computers

  10. Winuser's Avatar
    Posts : 6,987
    Windows 10 Pro Insider
       #129

    hawkman said:
    Has anyone else who has performed a clean install had thier c/users/????, (since 3 builds ago)
    changed from name - to the first 5 digits of thier MS login

    this also occurs in my enviroment variables path, even after changing hardware description back to name
    my 1st variable is Onedrive and i DONT have it installed.


    Roy
    When installing use a local account. You can switch to your MS account after the install.
      My Computers


 
Page 13 of 20 FirstFirst ... 31112131415 ... LastLast

  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 23:29.
Find Us




Windows 10 Forums