New Windows 10 Insider Preview Fast+Skip Build 18941 (20H1) - July 18 Insider

Page 10 of 28 FirstFirst ... 8910111220 ... LastLast

  1. Posts : 3,954
    64-bit Win10 Pro Insider Build 19569
       #90

    - the updates are presumably structured to cover most system set-ups..
    - there must be something unique in your case..

    - I'd get on to the techs at MS directly, if I were you..
    - I'm sure they'd like to hear from you..
      My Computers


  2. Posts : 92
    Win10Pro_64; Win10Pro_64 insider
       #91

    I’ve got also the c1900101 fault. So I decided to try a clean install of 18941 and that went very well. No storage driver problem. So the storage driver which is causing the c1900101 fault is already in 18932 and 18922 (I’ve installed an image of that build and couldn’t update to 18936).
      My Computer


  3. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #92

    I seem to be a little late to the party, but duties sometimes get in the way, as they have this past week. Writing tutorials for senior citizens new to computers or Windows 10 isn’t the easiest thing in the world . . . ask me and I’ll tell you.

    OK, so a couple days ago Build 18941 was released and this morning is the first time I’ve been made aware of it. A Skype friend told me neither 18936 nor 18941 would install on his machine. I immediately checked my Insider Fast/Skip Ahead partition and saw that 18936 had successfully installed, so what’s up with that?

    For the most part, I read the first post on any new Build release, so I settled down to read this one too. There were the standard (paraphrased) warnings about painful bugs, etc., so don’t install Insider Previews on your production machine. As always, there are links for further reading.

    As I read, I noted the What’s new section, which had some stuff about the Korean IME which I’m not interested in, since I don’t speak Korean. However, since Microsoft releases updates worldwide, it looks to me like that should be included.

    Then there was the changes, improvements and fixes section that had some interesting fixes. I’m sure that anyone whose issue was taken care of by one of these fixes could care less that there’s some Korean and/or Japanese stuff included. Just a thought.

    Next was the Known Issues section which I always read; the usual gaming/anti-cheat, Realtek SD card readers, etc. are there. I think Tamper Protection is new; at any rate, I will be sure to turn that on. And of course, the Japanese IME doesn’t affect me because, well, I only speak English.

    The one that stood out to me the most was the issue of Builds 18936 and 18941 not installing on a small number of machines. Reading here, I think small is inaccurate. Be that as it may, now I’m ready to see what’s what … but first, Microsoft’s c1900101 Update Issue:

    A small number of Windows Insiders attempting to install Build 18936 and Build 18941 may experience install failures with error code c1900101 due to a compatibility bug with a storage driver on their device. The PC will attempt to install, fail, and successfully roll back to the currently installed build on the PC. Attempted re-tries to install the build, either manual or automatic, will not bypass this issue. A fix is forthcoming, but there are no known workarounds currently.
    Of note is that UUPDump as an alternative did bypass the issue for some, and for some it did not.

    As stated above, I did indeed install Build 18936, so logically Build 18941 should install, since the two builds seem to be included in the same issue. However, if Build 18936 had not installed, at this point I would forego any attempt at installing Build 18941! Does that mean Build 18941 will or will not install? I will find out shortly.

    So, here I go … will it or won’t it install? Only the Shadow knows …
      My Computer


  4. Posts : 2,667
    Windows 11 21H2 (22000.593)
       #93

    Winuser said:
    It's not unheard of to have bugs in any new Insider Build releases but to have two builds back to back that some users can't even get to install is ridiculous.
    Sorry, but no, it's not ridiculous. Ridiculous was the 2nd build from last year not being released because it affected tens of millions of installs. With Insider Preview builds, you cannot ever expect 100% reliability - ever. You already know this. Everyone in here that uses an Insider Preview build knows this. If there are 1, 2, or even 5 builds that don't work for a small number of systems, then the program is accomplishing what it set out to achieve - we're one big ẞeta test for future versions of Windows. Not current, future. Not released to the general public, but something you have to actively sign up for, install, and maintain.

    If you're not ready to test (and more importantly, if you're not ready for things to break) you really should not be using Insider Preview builds at all.

    I'm not trying to be a dick, though I am coming across that way, but it is a matter of fact. No matter how many employees Microsoft has, and how many testbeds they have, things will slip by when you take into account just how many lines of code are incorporated into the OS. But, instead of having things slip by in final versions, now, we Insiders, are the 'second line of defense' to (hopefully) stop major bugs from slipping past. Obviously, even this system is not foolproof - last year's October build proved that.

    But complaining about ẞeta builds that don't work - that is not really cool. You know it may not work.

    I worked with a user last year (or 2017, forgotten which) for a long time trying to get a particular set of builds working on a system very similar to my own - I was able to install each upgrade flawlessly, and he was not. Same chipset, same generation CPU, similar RAM. He ended up finally upgrading his machine. Meanwhile I had 0 issues for the entire time he was having issues (this went on for 3-4 months, IIRC).

    BugMeister said:
    - the updates are presumably structured to cover most system set-ups..
    - there must be something unique in your case..

    - I'd get on to the techs at MS directly, if I were you..
    - I'm sure they'd like to hear from you..
    This. Instead of complaining, start writing to folks, asking questions, gathering data for bug reports. That's what we're supposed to be doing as Insiders.
      My Computers


  5. Posts : 11,247
    Windows / Linux : Arch Linux
       #94

    Hi there
    @johngalt

    I agree with most of your comments -- BUT :

    Yes agreed these sorts of builds are probably not even beta status - but alpha software -- and I think those who use them can't expect 100% reliability -- that's what testing etc is for -- I see some on these boards are moaning because they try and use these as "production quality" builds and grumble when something fails.

    What irritates me is that when something has worked in earlier builds and fails in these --especially when the release notes say problem has been fixed and it isn't at all shows that there's no sign at Ms (or there doesn't seem to be) that people shipping these builds out of the door have any idea about regression testing.

    The last build that I can get the display language stuff to work properly is the 18362.1006 build and on the standard 1903 build is the 239 one.

    Not good !!!!!!

    Might be a trivial issue to some but if you have a feature that works and the release notes actually say it's been "improved" !!! then IMO it should work as least as well as it does in the release it replaces / updates. I don't think that's being at all unreasonable.

    Cheers
    jimbo
      My Computer


  6. Posts : 7,128
    Windows 10 Pro Insider
       #95

    Wynona said:
    True, but to Microsoft's credit, they did tell us it's a known issue. At that point, it's up to the user to decide whether to go forward or stay put.
    They know about the problem and decided not to fix it before they released a new build. How can one go forward if the darn thing won't even install?
      My Computers


  7. Posts : 19,518
    W11+W11 Developer Insider + Linux
       #96

    Winuser said:
    They know about the problem and decided not to fix it before they released a new build. How can one go forward if the darn thing won't even install?
    Well, even negative result is some result. Maybe test to see on which computers it would install and where not and even why. This is second or third one that installed without a hitch.
      My Computers


  8. Posts : 7,128
    Windows 10 Pro Insider
       #97

    johngalt said:
    Sorry, but no, it's not ridiculous. Ridiculous was the 2nd build from last year not being released because it affected tens of millions of installs. With Insider Preview builds, you cannot ever expect 100% reliability - ever. You already know this. Everyone in here that uses an Insider Preview build knows this. If there are 1, 2, or even 5 builds that don't work for a small number of systems, then the program is accomplishing what it set out to achieve - we're one big ẞeta test for future versions of Windows. Not current, future. Not released to the general public, but something you have to actively sign up for, install, and maintain.

    If you're not ready to test (and more importantly, if you're not ready for things to break) you really should not be using Insider Preview builds at all.

    I'm not trying to be a dick, though I am coming across that way, but it is a matter of fact. No matter how many employees Microsoft has, and how many testbeds they have, things will slip by when you take into account just how many lines of code are incorporated into the OS. But, instead of having things slip by in final versions, now, we Insiders, are the 'second line of defense' to (hopefully) stop major bugs from slipping past. Obviously, even this system is not foolproof - last year's October build proved that.

    But complaining about ẞeta builds that don't work - that is not really cool. You know it may not work.

    I worked with a user last year (or 2017, forgotten which) for a long time trying to get a particular set of builds working on a system very similar to my own - I was able to install each upgrade flawlessly, and he was not. Same chipset, same generation CPU, similar RAM. He ended up finally upgrading his machine. Meanwhile I had 0 issues for the entire time he was having issues (this went on for 3-4 months, IIRC).



    This. Instead of complaining, start writing to folks, asking questions, gathering data for bug reports. That's what we're supposed to be doing as Insiders.
    Yes, I do agree that we will run into bugs when running Insider builds. The whole idea about being Insiders is to allow us to be free testers for MS. How can we test new builds if we can't even get them to install? The problem has been reported and MS list it as a known problem. There has also been many of updates to the general public that have caused some very major problems. That is the main reason that except for security updates I'm against automatic updates. Also to your statement "If you're not ready to test (and more importantly, if you're not ready for things to break) you really should not be using Insider Preview builds at all." #1. I like testing new builds. I can't do this if I can't get it to install. #2. It's my computer and I'll run any build or OS I want.
      My Computers


  9. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #98

    What has Stranger Things have to do with this Insider Preview???

    I know they use SurfaceBooks there but...still... (wrong Netflix series) why confuse OS release notes with other promotions? ....or is this quiz thing going to be a built in feature in next major release? If so, I think I might switch completely to something that keeps my focus on the things that gets work done and not stuff for personal or company amusement.
      My Computers


  10. Posts : 7,128
    Windows 10 Pro Insider
       #99

    CountMike said:
    Well, even negative result is some result. Maybe test to see on which computers it would install and where not and even why. This is second or third one that installed without a hitch.
    The last two builds installed on my laptop without me doing anything except restarting my laptop when I saw the notice. Both time the laptop was in sleep mode when it updated. I have no idea of the length of time it took .I just know they installed without a problem. For what ever reason my desktop will not update. I don't even get a error message. All I get is a black screen and no activity at all. The second try I watched the complete process and if I remember correctly it froze at 73% before going to the black screen. The reset button doesn't even work. I have to hold the power button in until the desktop shuts off. This is not the first time that two builds back to back wouldn't install on my computer. I almost forgot to mention that the first try was with a ISO made from UUPDump and the second try was with Windows Update.
      My Computers


 

  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 17:47.
Find Us




Windows 10 Forums