Desktop will not update from 1803 to 1809 – even with

Topic

New Reply

I tried following the instructions Windows10Upgrade9252.exe for updating my home built (2015, with video hardware upgrade 2018) desktop running Win 10 Home 32 bit ver 1803, I get the message that the hardware passes, and the download proceeded. However afterwards, the system is still ver 1803 (OS Build 17134.648). Should I be concerned? Acronis weekly backups are just fine and work correctly. But so far even less ready for a Win 10 update 1903. Any suggestions or advice is welcome.

Reply | Quote

Replies

post the specs of your desktop computer by running Speccy

Reply | Quote

I have a one year old i7 8770 computer with an Nvidia card and tried to update to 1809 and it failed, and then trashed it. Luckily it is one of my dual boots which has the latest Win 10, and the other is a fully functional OS frozen at 1709.

Based on research, it seemed I had to remove the Nvidia card and run the MOBO video card, in order to install 1809. The MOBO video doesn’t come up as a device, so it can’t be disabled, which is another option. I also have some USB 2 devices that have to be removed or not attached. For some reason the computer wouldn’t boot due to fan minimal speed problem with the USB 2 card removed.

Needless to say I lost interest quickly.

Reply | Quote

I assume that you delved into your BIOS settings and checked them, whilst refering to mobo manual. It seems odd that the on-board, presumably intel, graphics wasn’t picked up during on the second attempt of installation. Even stranger that the OS didn’t identify an nvidia card on a PCIe slot. Out of interest, what is the make & model of the mobo?

Windows - commercial by definition and now function...

Reply | Quote

Maximus Hero X MOBO, the nVidia cards are causing random problems. On install, 1809 stops at the infamous 42 % and hangs.

1803 iso just required unplugging everything attached.

1 user thanked author for this post.

Microfix

Reply | Quote

Have you tried to find any Intel UEFI updates for your motherboard model just for the sake of reading the changelog documentation?

Reply | Quote

There is no chance that I will change anything, as the machine works very nicely with the 1709 boot and old bios.

You change one thing and the knock-on effect means you are chasing one thing after another, ending in disappointment.

The 1803 dual boot runs [poorly], so the 1709 can stay as it is until the 8700 dies, or is too slow. I have an 1809 VM on the 1709, so that can be used for anything that needs it.

Reply | Quote

I wasn’t going to ask or tell you to change anything, just for you to read if there might have been some chance any firmware issue affecting you.

This the changelog for your board? Your welcome. (Like always with firmware updates they don’t tell people very much.)

I have no idea about the state of Nvidia’s drivers, that may also be a problem second to Windows 10 1803 itself.

Best of luck…

Reply | Quote

Mild dramatic effect, no offense taken.

I’m sure you are right, but I’m too scared to change anything for stability reasons. Thanks for the input.

Yes, I know, it is no way to live.

Reply | Quote

I apologize for [my attitude] towards the end of that reply.

Your thought pattern is good, good sense of what not to do first. I learn the hard way years ago and subsequently read elsewhere firmware changes are the last resort to fixing issues, the process has improved but stuff happens. That neat fancy new feature may not be important.

On the other hand you might need the security fix (it may also come with a surprise feature you do not want).

Reply | Quote

All good, text communication can be tricky. No judgement on anything I read.

Reply | Quote

If you’re interested, you can try this on your 1803.  Hopefully you have a MCT USB drive with the 1809 upgrade; you’ll need it.  If so, with Windows booted in 1803 and running, plug in your USB installation media, then check File Explorer to see what drive letter Windows has assigned to it. Use that drive letter to replace X in the following command line; remember, don’t actually use X, use the drive letter assigned by Windows. Type

dism /online /cleanup-image /restorehealth /Source:X:\RepairSource\Windows /LimitAccess

and hit Enter.  Note there is a space before each “/” in the command line.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

I too am unable to coax a Lenovo desktop from 1803 to 1809.  I tried via the passive approach, by clicking on “Check For Updates.”

So far, the only thing that’s caught Windows Update’s attention is KB4489894 March Cumulative Update for Win10 v1803 for x64 Systems.  This is not what I was going for and Susan Bradley said hold back for now.  I wanted to hide KB4489894 but it is not listed in WUShowHide.

Next step is to turn off “metered connection” and see what shows up at the door.

 

Reply | Quote

Next morning:  After clicking Check For Updates and leaving Metered Connection turned off overnight, the machine went from build 17134.648 to 17134.677, but it is still on 1803.

Why is Microsoft holding back?  What are they hiding?

Reply | Quote

My personal opinion is Microsoft stopped pushing 1809 due to the original issue with data loss. If Microsoft continued to push this to users uninvited and data loss continued to occur there could be legal consequences.

Red Ruffnsore

1 user thanked author for this post.

Latka

Reply | Quote

I like your explanation, Mr. Natural.  Attorney involvement makes sense of the “hot potato” treatment Microsoft has been giving the 1809 update after user data got sucked into the great black data hole of 2018.

Reply | Quote

I have turned metered connection on again. Will wait and try again when Woody gives the all clear (or at least a DefCon 2, since Woody doesn’t believe in “all” clear literally).

Reply | Quote

I would suggest for you to give up on 1809 and try to upgrade (when its stable) to 1903 You still have 6 long months of support.

if the same thing happens with 1903, then there is something wrong.

Just someone who don't want Windows to mess with its computer.

Reply | Quote