Build 18908 & 18912: WU uses excessive amount of memory during the update (officially a bug now)

A health check went fine but sfc /scannow failed the first time at 30%. Tried in safe mode and failed again. Then during the restart, I got messages about Windows updating and 2 restarts when in fact the update was hours ago. The last restart ended up with the infamous black screen / spinning dots, something that I've never experience before, ever!

Ran hardware diagnostics and virus/malware scans and everything passed so I have to assume that there's something definitively amiss with this build or the update process.

edit: also, Windows Security turned itself OFF without intervention after the last restart.

I watched my SP4 (Intel i5 6300 with 4GB memory, SSD 120GB) as it installed and it ran at about 1200MB max (WU) while installing with no problems, It did get to 92% overall memory use though

I can't say about Hyper-V as it was done remotely

During my attempts to update a 32bit Insider fast PC to 18908 I also experienced high Memory, Disk and CPU usage. This is not the first time I have had this with 32bit builds.

At one point I had Very high Memory usage (2.9MB of only 3.1MB,  SSD Disk usage from 50 - 70%, CPU up to 50% at my max

 of 3.40GHz

Eventually the install Failed again with 0x80070003

Ran hardware diagnostics and virus/malware scans and everything passed so I have to assume that there's something definitively amiss with this build or the update process.

edit: also, Windows Security turned itself OFF without intervention after the last restart.

Not showing any of these symptoms. You may be correct with your assumption of the update process as I did a total clean install via ISO and an upgrade from 18362.145 offline. Appears some others had no issue installing this way.

Never did like using WU since they changed to uup files from the esd file for upgrading. Just takes too long.

Never did like using WU since they changed to uup files from the esd file for upgrading.

Just takes too long.

I couldn't agree more. The WU process is too slow, cumbersome and very susceptible to failures.

What I hate the most is the extra download if the update fails. If UUP dump script can verify checksum and only download corrupted or missing files, why can't WU do the same instead of downloading the whole thing all over again? I sure miss W7 updates and having TOTAL control over it.

I use WU just for testing purposes, check for bugs, failures and such but I always restore my backup image afterwards and re-install using the ISO from UUP dump.

I feel better and more confident of the outcome performing a fast and straightforward update that way.

How's your wife doing?

I use WU just for testing purposes, check for bugs, failures and such but I always restore my backup image afterwards and re-install using the ISO from UUP dump.

That makes two of us. Miss the W7 style of total control. Seems in all MS wisdom of removing and hiding everything, may be great for non-tech savvy users, sure not for the rest of us. Been over a year since I used WU for a major upgrade. Good concept if only it worked for everyone.

She coming along, eating well, but still in pain. Silly girl moved a heavy mattress by herself and now popped something out of place. Had to give her s**t over that as she is only skin and bones. Lost over 35 lbs and she a small woman to begin with.

Seems in all MS wisdom of removing and hiding everything, may be great for non-tech savvy users, sure not for the rest of us.

Actually, I think it's pretty bad for them too because regular users get easily frustrated when WU fails and more often than not, the failure error message (if any) doesn't help much.

Glad she's doing well, best wishes! 

 Those cryptic hex error codes certainly don't help novices, and the rest of us have to know how to plow through searches, event logs, and these forums.  If MS really wants to give us something we need, they could work on providing plain text messages explaining these instead of giving us a whole lot of silly stuff most of us have no use for.  But there I go wasting my keystrokes again!  :(

Agreed, you would think that MS could give a proper brief explanation of what went wrong instead of these hex error codes. Must be their method of driving us to use Search for ad revenue :-)