Announcing Windows 10 Insider Preview Build 14257 Insider

Page 8 of 25 FirstFirst ... 67891018 ... LastLast

  1. Posts : 591
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon
       #70

    Ztruker said:



    Anyone tried regedit, see if it's fixed yet?
    Yes, I have tried it, sorry it is not fixed. I have already reported it.
      My Computers


  2. Posts : 3,080
    W10 Pro + W10 Preview
       #71

    Joanne said:
    Yes, I have tried it, sorry it is not fixed. I have already reported it.
    I think it is done deliberately by M$ as it is a work in hand.
      My Computers


  3. Posts : 2,155
    Windows 11 Beta channel
       #72

    Hmm, I'm still getting lock ups in GTA V occasionally. Think I may try a clean install.
      My Computer


  4. Posts : 22,741
    Windows 10 Home x64
       #73

    Still no issues so far.

    Can't wait to see what's coming along.
      My Computer


  5. Posts : 357
    Release (17134.471) + Insider Preview Fast Ring (18298.1)
       #74

    BunnyJ said:
    Still no issues so far.

    Can't wait to see what's coming along.
    Unfortunately most of these changes so far are "under the hood" changes; changes to OneCore and the kernel to better optimize the OS between the various devices that Windows 10 is running on. It will still be a while till we see outward physical changes, especially like extension support for Edge.
      My Computer


  6. Posts : 22,741
    Windows 10 Home x64
       #75

    rogerwilco91 said:
    Unfortunately most of these changes so far are "under the hood" changes; changes to OneCore and the kernel to better optimize the OS between the various devices that Windows 10 is running on. It will still be a while till we see outward physical changes, especially like extension support for Edge.
    That sort of what I was talking about.
      My Computer


  7. Posts : 56,064
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #76

    dencal said:
    I think it is done deliberately by M$ as it is a work in hand.
    Odd, though, that 10586.71 fixed it for RTM so they must know the issue, and the fix. Must be a long walk from one side of Redmond campus to the other!
      My Computers


  8. Posts : 3,080
    W10 Pro + W10 Preview
       #77

    f14tomcat said:
    Odd, though, that 10586.71 fixed it for RTM so they must know the issue, and the fix. Must be a long walk from one side of Redmond campus to the other!
    What I was thinking ( purely conjecture) was that all recent insider updates were concentrating on optimisation and bug clearing.
    What I meant by a work in hand was, maybe now they are concentrating on adding extras.
      My Computers


  9. Posts : 3,245
    Windows 10 and windows insider
       #78

    waltc said:
    Build 14257...This is the second consecutive build that will not install on my machine...14251 wouldn't either...I haven't had this much trouble with installing Windows builds since I signed into the program in 10/1/2014--the pre-Win10 launch builds never gave me as much trouble. I reported this problem a week back and yet it isn't mentioned anywhere in the list of known or fixed bugs in 14257.

    My system @ home:
    MSI 970 Gaming motherboard, latest bios, M.4
    AMD FX-8320e @ stock speeds
    8GBs (2x4) running @ stock 2133MHz
    Samsung SSD 850 EVO 250GB (boot)
    2 x ST3500418AS HDs
    2 x WDC WD10EZEX HDs
    AMD R9 380 4GB GPU running the Crimson 16.1.1's

    Last successful build 11099



    When doing the internal "flight" install through WU, everything is fine through the "copy files" portion of the install--it hits 100% and the system auto reboots to continue the install...and then *WHAM* suddenly I have a blue screen failure INACCESSIBLE_BOOT_DEVICE...upon reboot, even if I hit F11 and manually select the boot drive--it does not matter, the system fails to boot and I am restored to my last fully working build 11099...! Thank goodness the "restoring previous build" function has worked perfectly each time.

    My SSD drive is fine of course and the "previous build" I have is located there as well--so the error is clearly a build problem & bug and it would be NICE if it was acknowledged somewhere. The only time I have ever seen this error under normal operating conditions is when the system tries to boot with the IDE driver installed instead of the AHCI driver--the SSD *requires* the AHCI driver and will not function with the IDE driver. All the Win10 builds I've tested since 10/2014--all of them--successfully carried the AHCI settings over to the next build. (Except 14251 and 14257.)

    I ran across one person in Feedback who had the same error I did, INACCESSIBLE_BOOT_DEVICE, and he reported that disconnecting all the drives in his system except for his c:\ boot drive got him past the error and allowed him to install. Didn't work for me.

    Ideas, suggestions, anyone?
    wish I had a suggestion. I have been able to update my laptop to build 14251 and now to 14257 ( updating) but my desktop will not update. Nothing has changed in terms of machine hardware/software but it keeps reporting that it is up to date and, like you, it is stuck at 11099. Don't know what to do, maybe just drop it from the insider program. I have my laptop to play with.
      My Computer


  10. Posts : 17,831
    Windows 10
       #79

    Something odd...


    Just wondering about something with Windows 10 in general:

    Many 'Proper Titles' are not all capitalized in the new UI, whereas, in previous versions of Windows, they always were.
    Which is proper?

    Announcing Windows 10 Insider Preview Build 14257-000008.jpg Announcing Windows 10 Insider Preview Build 14257-000007.jpg
      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 05:41.
Find Us




Windows 10 Forums