(Windows Home) I just checked and I’m on Windows 1809 and it says my system is up to date. 1903 came out in May 2019. Why am I still on 1809? What is preventing my automatic upgrade to 1903? I'm getting error code 0x8e5e0408. Should I try to upgrade to 1903? Thx,
Last edited by m3110w; 07 Oct 2019 at 03:01.
You can upgrade to version 1903 using Windows 10 Media Creation Tool.
https://www.microsoft.com/en-us/soft...load/windows10
When are you seeing this error?I'm getting error code 0x8e5e0408
a. any attempt at Windows update incuding 1809 CUs
b. attempt to upgrade to 1903
?
Your post is not clear on this and suggests there could be two questions:
a. Why is Windows update failing
b. Why have I not been offered 1903
Please post a screenshot of your Update History.
To post a screenshot please use the Insert Image icon above your post.
Meanwhile this suggests the error number can be associated with Store updates:
FIX: Windows Store and Apps Error Code 0x8e5e0408
Thanks for the clarification.
Yay! I was able to upgrade to 1903. Took about 2.5 hours and 3gb. Wow. After lots of restarts my system seems to be working fine. It was recommended I change the registry item
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
and this change seemed to finally allow the upgrade to happen. I'm very happy it went smoothly.
That's good. May we ask what the change was, so that others might benefit?
Now's the time to create a new base disk image before something goes wrong.. e.g. Macrium reflect (free/paid)
Last edited by dalchina; 07 Oct 2019 at 10:57.
The Windows 10 Update Assistant appears at the top of the "Download Windows 10" page.
It, too, can be helpful when trying to upgrade from an older version of Windows 10 when Windows Update itself reports everything is current and OK. I used it myself this weekend, when updating a 1-year-old Lenovo X380 Yoga laptop I bought on eBay. It came with 1803 installed, and for that build, WU professed itself OK without offering the upgrade. Windows Update Assistant got me to 1903, after which I joined the Fast ring Insider group on that machine. It is now happily running Build 18995.1, as shown:
--Ed--
Sure, for that reg key I just changed it from 1 to 0 as was recommended. Then the upgrade (finally!) completed.
And I just now completed a Casper full image of my drive. I'm fanatical about keeping everything backed up.
- - - Updated - - -
- - - Updated - - -
Hello Tittel, Yes, that's the page I went to to start the 1903 upgrade process. Cheers,
Last edited by m3110w; 07 Oct 2019 at 22:07.
I thought I'd reply to this thread since I found it during a search when I was having problems updating my Lenovo Yoga 900 (2017 model).
I was on the 1803 version of Windows 10, and it wouldn't update to either 1809 or 1909. The computer tried to do it itself automatically several times, but it always came back with an error message. My manual tries were no better. I forget the error code, but a Google search of the number suggested it might be a storage space issue, which was certainly not the case with me.
The machine would get hung up on a dark screen after the install and "final" restart, and the hard disk would be spinning like mad but I couldn't see anything happening on the screen, even if I left it alone for several hours (which I did once). So each time I had to do a hard reboot. That really made me uneasy, but each time it automatically went back to the old version (after several nervous minutes). Then I found this thread.
I tried to use the RegEdit approach, but that didn't help since there were many subdirectories under the folder "Control" and I didn't whihc key was to be reset to "0". I then used EdTittle's approach, but still no good.
Then I read a trouble shooting thread from Microsoft, and one item they listed was "remove all peripherals." I am using a Targus docking system and dual monitors along with wired external keyboard and mouse, so I unplugged the Targus from the computer (which turned off all peripherals) and then used the "EdTittle approach" again. It worked, so it must have been the peripherals. I suppose I should have been more suspicious of this sooner. Anyways, I am now updated to 1909.
Thanks to all of you who contributed to this thread. Although I didn't find the specific solution here, it kept me going -- I was about to say to heck with it. After all, I had tried doing the update 5 times at least (in addition to the machine's automatic attempts) over a period of a few months.
Quote
