Personally, I skipped right over 8 and 8.1 but it seems things started badly there and 10 is just an evolution of those but still has so many problems. The problems many have had with this update showing the OS to be akin to playing Russian roulette, you just don't know what's going to happen. Personally I think trying to wedge the whole 'apps' into it and make it a hybrid mobile/desktop OS has made life difficult for the OS. Not to mention it's too cloud and MS account orientated so your at the mercy of MS servers behaving themselves. Things would be better if they had separate OS for desktop and separate OS for their mobile devices. Windows 7 was a terrific OS and patch Tuesday was always more reliable - imagine how mature and stable the OS would of been if they stuck with 7 and focused on improving that rather than trying to make us forget it ever existed. We've lost DVD playback, much better photo gallery in-built software and things like movie maker and DVD maker. We've lost what was a much better start menu and gained a store and native apps of questionable reliability and functionality. Edge is unpredictable and far less functional than IE11 or chrome/Firefox so it feels like a backwards step. It changes default programs without asking and even disables certain programs it doesn't like. Securom (as annoying as it was) has been disabled knocking out half my optical games library. We've gained more bugs than an English country garden on a hot summers day and gained a measure of unpredictability, so many people struggle with native apps breaking and no easy fix with the powershell fix in danger of making the damage even worse. Repair installs at an all time high. So seeing some of the carnage this latest cumulative update has just caused even more dissapointment. Trouble is there is no escaping 10 - I really hope it improves and the anniversary update makes things better but for now it's unpredictable nature has tested my enjoyment of computing.
to be honest I didn't even see the point in this latest cumulative update with anniversary update due on 2 Aug. It seems to be quite a big update which will be totally redundant soon anyway. Obviously security flaws need patching but given the size they seem to of changed more than that.
Last edited by Scottyboy99; 14 Jul 2016 at 18:07.
yesterday, i updated using IE download standalone(offline) method so i can installed my both desktop & laptop.. takes about 2 hour & work perfectly smooth.
1. cumulative update (KB3172985)require restart, 2. adobe flash (KB3174060)
3. window stack (KB3173428).
before apply this 10586.494 update must created system restore point then turn off antivirus proctection & firewall to prevent installation block by antivirus.remember set to automatic on window update services.
finally ready to install those update it will restart after it done then type winver on search box check latest 10586.494 updates that had installed.
Last edited by cayzios; 15 Jul 2016 at 07:59.
I made some major corrections to problems with win 10 early on, august 2015 and have had little to no os conflicts whatsoever. Everything issue has been solved through personal knowledge, solutions from this website or answers found on the web. No calls to MS or any other help desk. Rock solid windows 10 here. SFC /SCANNOW and DISM repair procedures should be mastered by all as a matter of principle. Kind of like knowing how to driving a manual shift automobile. IMO.
I did not have any problems with updating to the new version 494. update on my two laptops and download of the files from the catalog on my desktop went smooth like a 30 year old whiskey and all at the same time (on update tuesday). downloads and installs went rather fast I have to say....
Unfortunately, this last update of the existing version of Win 10 Pro, has NOT gone all that well.
I have experienced a spate of MS Edge where it just stops working for absolutely no reason at all. Then other packages such as Adobe reader have failed to re-configure properly. I have detected conflicts with Windows Defender updates that now also fail.
Not a good sign at al!
Smells of a rushed attempt by MS to get through some outstanding mods to the OS BEFORE the big update month, and these mods have NOT been properly tested beforehand .......
Last edited by Geoff Daniell; 15 Jul 2016 at 14:24.
NEW Cumulative Update for Windows 10 Version 1511 (KB3172988) - July 14 - 2016
Windows 10 Cumulative Update KB3172985 Fails to Install, Downloading Freezes
New update, old problems: KB3172985 issues once again
KB3172985 is the most recent Windows 10 cumulative update released by Microsoft for version 10586, and just like it's happened so many times before, it’s also experiencing issues on a number of devices.
If you’re a long-time Softpedia reader, you've probably noticed that we post news about cumulative updates that fail to install every time Microsoft releases a new one, and this is because the same issues are being experienced over and over again by a number of users running Windows 10.
And KB3172985 makes no exception to the rule, as the same bugs are being reported right now on several Microsoft online communities, including Redmond’s very own support forums.
Basically, Windows 10 cumulative update KB3172985 just fails to install, so you download it, your system reboots, the installer launches, and then, all of a sudden, you get an error telling you that “We couldn’t complete the update. Undoing changes.” The PC is then restored, and you’re brought back to your desktop, with no update installed whatsoever.
Downloading freezing before completion
Windows Update then re-attempts to download the same update, and your PC needs a reboot to complete the install, so the device is pushed in an infinite loop because of this faulty bug.
Additionally, there are reports that the downloading process of this update freezes at various moments before completion, and although it was initially believed that everything was caused by a server overload since everyone was getting the patch, it turns out this isn’t the case. There are users who are complaining about the same issue several hours after the update was published, so it might be a good idea to wait a bit longer and then try again later.
For the moment, there are no workarounds for the aforementioned issues, but the good thing is that Microsoft is already keeping an eye on all reports, and fixes might be in the works as we speak.
Last edited by Adriaan Jansens; 15 Jul 2016 at 07:28.