Windows Cumulative Update KB3194496 Installation Issues

Although the install appears to stop it's still working. It will jump to a higher percentage suddenly rather than slowly increase the number.

I experienced the same thing, more or less. Took forever to install.

or try this

https://www.neowin.net/news/heres-a-workaround-to-get-the-failed-update-to-windows-10-build-14393222-installed

Oh good...something else to look forward to...

Just spent the last 4 days getting into my Niece's machine [laptop] which gets no further than a cmos password no-one actually ever set....eventually finding the correct jumper to short - hiding behind the CPU cooler tube link...

Got it finally to install again...after accessing the win key used, downloading the media...and convincing it to reformat etc....there was no user data on it...just a borked win 10 install....[surely not....never happens... ]

And now finally I'm twiddling thumbs as the 'update' stalls at 85%...

Even before that a reboot locked me out...claimed my password I'd just installed was wrong....and it wasn't...cos when I brute-forced that one it popped up as I had set it...so I reset it to the SAME again....rebooted and it was fine.

Win 10 is a really good OS...

IF/WHEN it works....;p

Well....Niece's machine is now behaving....all updates done OK.

....but I have an older Laptop of my own...similar spec....which has failed the AU update....with similar symptoms...

Clearly has 'lost' the HD [mostly] and all key options get you to a password for bios which definitely was never set by me.  Looks like the update fucks the bios....kinda clever.

So.... it's time to open her up and find a jumper to short on this one as well, as I can't boot into any external recovery option.

Now...let's look at Microsoft's Win 10 track record....

1 out of 5 updated to Win 10 without issue.

1 out of 4 updated to AU without issue. [NOT the same one]

2 out of 5 required BIOS resets to access the system at all.

1 out of these 2 couldn't get past 'auto recovery'.

The other got past the Win logon and no further.

So....in short...

2 out of 5 required skill outside of 'the average user' to get the machines working again.

Microsoft....you are inept.

Didn't Microsoft fire their entire QA department recently? lol

From what I read in The Register, they are now looking for someone thick skinned enough to handle this mess (i.e.; become the boss of their Windows Update department). Requirements are 'ability to reduce chaos, stress'.

Seriously, check it out (lol) HERE.

Microsoft has become the joke of the Industry. It would be funny too - if so many people didn't depend on them.

https://forums.wincustomize.com/479789/page/1/#3651549

Now going to update 7, 8.1 like W10. Because it's so obviously a great way to do things. Idiots.

lol...

Usually I jump to the latest version on Windows pretty quickly, if only because I need to make sure Winstep software is working properly on it. The best way to do that still is to run it on the latest Windows version 24/7.

But not this time. I absolutely hated Win 8.x, and Windows 10 gives me the creeps. Instead I'm relying on two Virtual Windows 10 machines and a physical, secondary, Windows 10 PC. The Windows 10 VMs allow me to test Winstep software from my main Windows 7 production machine. One of the VMs is setup with all the development tools I need so I can debug the code directly on it, the other is used to actually test releases on a 'clean' installation.

My Windows 7 development PC is already over 4 years old, but it still is a high end machine even for today's standards: a i7 Ivybridge CPU running at 4.5 Ghz, 16 GB of RAM, two 256 Samsung 840 SSDs in RAID 0, nVidia 980 gtx ti graphics card, three 30" 2560x1600 monitors, etc...

However, I am already planning on an upgrade, and this normally means a new PC. Samsung just announced the new 960 PRO M.2 NVMe SSD drives, and my current motherboard (an Asus P8Z77-v Deluxe) does not really support those. At least not in a way I can boot from it without having to patch the motherboard's UEFI BIOS.

My RAID 0 array already gives me over 1,000 MB/s read throughoutput, but even that pales in comparison to the 3,500 MB/s offered by a *single* 2TB 960 Pro NVMe drive. I'm salivating.

So, I'm going to need a new motherboard, and that implies a new CPU, DDR4 RAM, etc... Basically a new PC. It also implies installing Windows from scratch, and, if I am going to do that, I might as well go with Windows 10.

My guess is that it will still take me a few months to take the plunge, so I'm praying for MS to get their sh*t together in the mean time. Yeah, dream on.

I'm the type of person who leaves their system on 24/7 with lots of different windows open and applications running, normally only rebooting to install Windows updates. But when I do reboot my system, *I'm* in control, I decide when and how. Under Windows 10, Windows decides for me.

I can already imagine it: busy coding for hours, getting up to grab a coffee only to find the system rebooting itself by the time I get back, with all the stuff I haven't saved yet gone forever. Good one, MS!

So far the death toll here is 2 laptops out of 3 needing reformat and reinstall....and only after resetting the bios.

Quite a successful record for a Microsoft Update....

Almost prefer the heady days of ME when MS was trying to make 'system restore' a thing....;p

Update: Microsoft has issued a fix for Windows 10 users caught in the KB3194496 installation loop:

http://www.eweek.com/enterprise-apps/microsoft-fixes-windows-10-update-install-loop-bug.html

Windows now meets the definition of malware.

Never thought I'd say it, but I think I'm beginning to miss Balmer.

Windows has been skinned since it was knee high to a grasshopper. Figures, in its adolescence, it would need SD products to pull it up by its boot straps.

Start8 has made Win8.1 actually usable for me. It's too bad the SD products don't fix the glaring privacy holes - among other issues in Win10. Have to go elsewhere for those, sometimes to new and untrusted sources

Of course that is why I am still running W10 on only one test machine that has nothing important on it. Missed getting it for free on more than a few computers due to too many issues I have with it personally.

I think I may be the lucky one. Updated perfectly and everything running perfectly. I used to have freezing issues but all gone now!

Technically it's the best/most mature OS Microsoft has made....it's just the execution that's at fault.

If it works it's brilliant.  When it doesn't it's a dog.

Oh, I agree about the actual operating system itself, it is all the choices MS has made in regards to updates, privacy, and general shenanigans* that is making me more than a little hesitant to migrate.

*shenanigans mostly meaning every time there is an update means going back through and checking all of your privacy settings which have probably been reset to the way MS wants you to have them. Of course that may not matter as who knows if MS is actually honoring those settings or just sending your data to them regardless.

I don't worry about the data being sent....provided it does not facilitate targeted advertising.

The scenario once mooted that you could be having a conversation about a death of your child [or similar] only to have some fucking advertising for Undertakers R US dot Com.

The concept of forced updating so everyone is on the 'same' system is sound in an OS management sense...but not in a real-world sense.

The ONLY way cock-ups can be averted is if there were a STRICT automatic compensation/penalty clause set so Microsoft was required to pay 'someone' dearly every time they get it wrong....with no avenue for appeal.

Perhaps something like 100 million to the poor/starving/cure for cancer...whatever.

Something BIG enough to actually make them think twice before releasing a less than perfectly tested update.

But hey.....you didn't pay for 10 so how can you complain?

Yeah, riiiight...;p