New
#600
Post # 41 in this link:
Cumulative Update KB4497934 Windows 10 v1809 Build 17763.529 - May 21
Post # 41 in this link:
Cumulative Update KB4497934 Windows 10 v1809 Build 17763.529 - May 21
Just a thought....
I also have an older pc, that doesn't show the option to boot to a USB drive in the bios.
Hitting F8 at the point during the boot process that I would hit delete to enter the
bios brings up a boot selection menu that allows me to boot to the USB drive.
Can't hurt to try.
peace
wanna
Last edited by Wannagofast; 27 May 2019 at 17:29.
I tried all of the methods for this upgrade (Note all were an update in place). On my little tablet I tried "Setup.exe" from the MCT Created USB - No go (Also in the end I had to remove the SD card). I ended up just trying "Windows Update Assistant", all went well it was happy. On my Laptop I decided to try mounting the ISO image downloaded via MCT, It upgraded with no issues. The third machine is my desktop (has lots of Drives, memory etc.) I copied the contents of the ISO to an Internal SSD. First I copied the ISO Contents to a SUB DIRECTORY on that drive. That was a no go, Setup complained about not being able to create a temp directory (???). I believe he didn't like not being in the Root directory. Finally copied the ISO Contents to the Root directory, ran Setup and in 41 minutes, Windows 10 1903 was alive and well.
You can tick it to remove 32.9 GB and gain in storage space. Make sure to make a system image backup after in case you want to roll back.
https://www.howtogeek.com/223821/wha...you-delete-it/
Just stopped by to say I started a clean install on a spare drive this morning and it works. Landed on 1903 in less than 20 minutes.
Now I've installed all the same hardware, all the same intrusive software, device drivers and everything and it continues to run fine. I'm making Macrium images along the way and when I feel ready, I'll clone it to my M2 disk.
Just a shame. Something tiny in my old system is kicking out of an inplace upgrade. Sad thing is, I would have been done by now.
I think they need to rethink these installers, maybe make them more robust. Just my two cents.
Thanks everyone for the suggestions. I finally got there. And at least I know it's not my hardware.