Original Spring update (1803.1) appears to be updating to new version

jimbo45 · 01 May 2018

Hi there

just a note to those who tried the original Spring Creators update (from the Ms site - legal one) before Ms pulled the release --although the esd files still on the ms servers yesterday.

I'm not on any insiders ring.

I did check for updates and it seems to be updating -- quite a big update too.

here's what I started with

Original Spring update (1803.1) appears to be updating to new version-upd1.png

and here's what I'm getting now

Original Spring update (1803.1) appears to be updating to new version-upd2.png

will update this post to see what version after the update.

cheers
jimbo

Samuria · 01 May 2018

I got the same I thought it may be a quick update but it's done a full update total time 3 hours

slicendice · 01 May 2018

I've seen a lot of reports of this behaviour. I think it has to do with a change of build ID and there might be a few configuration differences between this build and the previously leaked one.

jimbo45 · 01 May 2018

Hi folks

on last 2% (98% updated) seems to take a long time

BTW make sure your Windows partition is large enough to accommodate windows.old (prev install) and V.S.S otherwise you'll fail during update. After update you can delete extraneous files and shrink partition -- my preference is Linux live distro and run GPARTED but any bootable partition manager should work.

Cheers
jimbo

slicendice · 01 May 2018

jimbo45 said:

Hi folks

on last 2% (98% updated) seems to take a long time

BTW make sure your Windows partition is large enough to accommodate windows.old (prev install) and V.S.S otherwise you'll fail during update. After update you can delete extraneous files and shrink partition -- my preference is Linux live distro and run GPARTED but any bootable partition manager should work.

Cheers
jimbo

Most of Windows.old is just a bunch of junction points or similar and does not take up much space at all. Allthough my Windows.old is usually around 25-30GB, in reality it only takes about 5-8GB disk space.

jimbo45 · 01 May 2018

slicendice said:

Most of Windows.old is just a bunch of junction points or similar and does not take up much space at all. Allthough my Windows.old is usually around 25-30GB, in reality it only takes about 5-8GB disk space.

Hi there. @slicendice

It does matter though if you've only allocated about 60 - 70 GB for Windows originally and no other HDD space available for Windows.

The actual space used isn't also the issue -- it's when the update process asks for an allocation and can't get the size it wants - even if it won't use all of it.

There's a load of temporary rubbish that's also using HDD space during the update plus of course the V.S.S for locking so you can continue working while the update is processing.

After all the This is done you can delete extraneous files and shrink partition to a small size again if you want.

Cheers
jimbo

slicendice · 01 May 2018

jimbo45 said:

Hi there. @slicendice

It does matter though if you've only allocated about 60 - 70 GB for Windows originally and no other HDD space available for Windows.

The actual space used isn't also the issue -- it's when the update process asks for an allocation and can't get the size it wants - even if it won't use all of it.

There's a load of temporary rubbish that's also using HDD space during the update plus of course the V.S.S for locking so you can continue working while the update is processing.

After all this is done you can delete extraneous files and shrink partition to a small size again if you want.

Cheers
jimbo

Yep, true.

Windows needs about 8.5GB of free space in order to successfully being able to upgrade. having 16GB or more free space is better though, so the update goes a bit faster and there is absolutely no risk of running out of space.

Also during Windows Upgrade, it does not matter where this free space is located. If you have a secondary partition or another HDD, that will be sufficient. Windows is intelligent enough to use any free space available on the system for SWAP space.

I tested this on a VM. Installed Windows 10 Pro 1709 on a 20GB system drive(4GB free after install), and then I assigned a second 16GB drive, and upgraded to 1803, without any issues.

BRKKAB · 01 May 2018

I was in the same exact scenario as you on my older pc. Same old Windows SCU that was supposed to be the RTM version.
This is where the scenario changes, though.
My old pc uses wi-fi and has a ssd which Windows is on.
My internet speed on my main pc has a 120-030 m.b.p.s. download speed. It's wired directly to my router.
My old pc uses wi-fi and has a 20-30 m.b.p.s download speed.
Through Windows Update my old pc took roughly 45 minutes to download the update and around 45 minutes to 1 hour for the actuall Windows 10 April 2018 Update to install.
Either you have issues with your pc or a really slow internet connection and Windows is on a h.d.d. and not a ssd.
It could be any number of things.
I keep my pc's ssd's and h,d,d's extremely clean and pretty much check for driver and software updates at least once a day Monday-Friday. On Saturdays & Subday's it's just software updates or malware definitions.
I als restart my pc's after every update and when I close any web browser, I at least do a cleanup with CCleaner.
Once, I knew both my pc's were fine and everything made it through the April 2018 Update with no issues, I got rid of the Previous Version of Windows on both pc's and haven't had any issues.
MAKE SURE YOU RE-CHECK ALL YOUR SETTINGS AND RE-APPLY ANY REGISTRY TWEAKS (IF YOU USE ANY) PRONTO, JUST TO BE SURE YOUR PC IS THE WAY YOU LIKE IT AND HAD IT SETUP BEFORE.

slicendice · 01 May 2018

The upgrade speed vary a lot between devices with similar specs. For some it takes 45minutes from hitting "Check for updates " in WU dialog to be back on upgraded Windows desktop, for others this can take 3-4h. There are a lot of factors that influence this huge speed difference.

Barman58 · 01 May 2018

MIne, (updates whilst in use) took between 50 Minutes to two hours dependant on system, from hitting go to working desktop, but of course that was before the RTM rush