1803 update: 4th time’s a charm


Oopsie. Something happened to my original post, it disappeared. I wrote in detail how my main system last night went all BSoD on me as I tried to install 1803 via Windows Update. After the third try (unplugging various peripherals and updating my Nivida driver, etc.), I finally decided to use the Media Creation Tool, and then it worked fine.

Some alternative combination of 0’s and 1’s? lol

Comments (21)

21 responses to “1803 update: 4th time’s a charm”

  1. ErichK

    My thread keeps disappearing...

    Just wanted to mention how last night my main system did a BSoD three times before I finally was able to successfully install 1803 via the Media Creation Tool. For some reason that worked, but Windows Update didn't.

  2. epguy40

    new problem with the 1803 update whether KB4103721 or even the new KB4284835 patch is installed:

    "Some users running Windows 10 version 1803 may receive an error "An invalid argument was supplied" when accessing files or running programs from a shared folder using the SMBv1 protocol."

    anyways who uses older devices that depend on that ancient SMBv1 protocol.

  3. Lauren Glenn

    I assume this is why I never see this problem. I always update my Windows installs using the Media Creation Tool. Windows Update either downloads the whole thing and then just fails... then keeps trying to redownload the entire thing until I just download the ISO and install setup.exe from there while in Windows. It seems to cause a lot less problems, at least for me.

  4. Brian X

    Upgrading from Insider build 17672 to 17677 resulted in 2 green screens reporting memory management issues. I've rarely managed to get my system to upgrade automatically despite following all the various advice on forums in every combination imaginable! Usually I give up and install an ISO from MS but strangely when I used a new totally blank SSD and install 17025 and them immediately allowed it to upgrade to 1803 and then 17672 it all worked. Is this a clue? Is it something on the SSD (A Crucial) that once the UEFI & Recovery partitions are fixed, updates fail? Is the UEFI partition getting full? Is it that sort of "memory" at issue?

    • jimchamplin

      In reply to Brian_X:

      There shouldn’t be anything in that partition aside from files required to boot You system. If Windows isn’t automouting it and it’s showing up in Explorer, visit Disk Manager to disable its drive letter. You don’t want anything to have access to that partition.

      But as to your question, that isn’t memory anyway, it’s storage. Memory management doesn’t deal with disks, but RAM.

  5. DavidSlade

    To me this questions the value of the Insider program. Didn't any Insider(including me) pickup theses issues? I think Paul did.

    • Angusmatheson

      In reply to DavidSlade:

      The value is finding problems early and addressing them. In this case I think they saw problems in the insider program and choose to ignore them - I think because because of the name 1803 - meant that they needed to get it out by the end of March and I think they wanted to get it out before Build so they didn’t have to talk about it and could talk about what Microsoft leadership saw as more important. I do think the success with the last few releases made them feel nothing could go wrong. What could go wrong?

  6. Paul Thurrott

    I think we're having site issues, sorry. Working on that...

  7. epguy40

    well EricHK and Paul, Microsoft has recently acknowledged some problems with the April 2018 update which are mentioned in MS support KB article 4103721


    Users with certain Intel SSDs or Toshiba SSDs should revert to the 1709 release or earlier until Microsoft issues a newer CU for the 1803 release

    • ErichK

      In reply to epguy40:

      Well the update went fine on my Asus 2-in-1, and I've yet to experience any issues there, but on my main desktop machine where I got the blue screens during the install, I'm now experiencing some blank icons on the Start screen and I can no longer print. Blank icons are not a showstopper, but I'm not happy about the printing, obviously.

      Had to print out some documents this past weekend, and it was my Mac mini to the rescue. Works perfectly there.

    • Paul Thurrott

      In reply to epguy40:

      Weird, Microsoft assured me that this release was as reliable/stable as the previous few releases. :)

  8. ErichK

    Actually, up until now, I've had no problems with Windows 10 updates, but now that I got this BSoD I'm a little nervous.

  9. goodbar

    My Windows 10 1803 update has tried to install twice, once it froze for a good 8 hours at 30% progress, and the second time it hung at 2% progress for a good 10 hours. Maybe I'll try the media creation tool route and see if that helps.

  10. Tony Barrett

    Now just imagine you're a very average user with no technical skill at all. You try to install the latest update - because MS say you have to - and you get a BSOD. That's one borked machine that may cost money to repair. You had enough skill to fix it, the vast majority won't, and this is a big, big problem with Windows 10. Most big updates have a much higher level of associated risk than previous versions, and I've seen way more failures with updates in 10 than I ever did with any previous versions of Windows, and we're not just talking system update failure's but a large list of post update problems should the update actually 'install' correctly. The Win10 update process is still very broken.

  11. lordbaal1

    The preview is a beta. There are thousand of different PC configurations. MS cannot test out all of them. You have different people using different software, different hardware, different peripherals.

    It is impossible for MS to test all of them.

    That's why they beta test them.