Windows 10: Cumulative Update for Windows 10 Version 1511 KB3140743

FYI:

Windows 10 release information






Source: https://technet.microsoft.com/en-us/...s/release-info

 

Just done mine all good so far

 

Just upgraded all of my personal Win10 current branch machines, still have my son's & wife's computers left to go. So far, so good. Hope the impact of day-to-day use lives up to the promises of the changes and improvements.
--Ed--

 

Downloaded and updated in less than five minutes. I haven't seen any problems yet but it's annoying that MS still haven't fixed the bug that causes four event log errors ID 7031 at every sutdown of the PC. The last I heard on this was around a month ago when they said they were still working on a fix.

 

rebooted after backup now version 1511 OS build10586.122 and so far working fine

 

Updated without any issues *Biggrin

 

yeah, they don't seem to fix any of the bugs I notice. Lots of updates but I couldn't tell you the difference between when I first got my machine in October to now.

 

Edit: glad to see update worked for you after 2nd try. *Biggrin

@thegeriatric WU installs KB3139907 first then WU tells you a restart is required while cumulative update KB3140743 is waiting to be installed.

After a restart both should be installed and can be verified by checking WU history.

 

No problems on my pc, but it fails on reboot on my dad's pc :/ I tried a few times (and also with the one on the update catalog) so I guess it's a problem with an update. More like a 'problem' because his pc is a 7-year old laptop, so I guess it's driver/hardware related. If it doesn't work in a month or so I'll do a reset.

 

Although the Redstone preview has addressed this issue, and SFC /SCANNOW comes back clean on those versions, the current cumulative update still shows "corruption" galore in the Windows system files owing to a mismatch between MS and Nvidia versions of these files. It's looking increasingly like that fix won't come into the current branch until the current branch moves over to Redstone later this year.
--Ed--

Here's a CBS.log snippet, by way of illustration:
Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-01 15:18:29, Info CSI 000050f8 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

 

Mine to was stuck at 6%, I stopped all unwanted items in taskbar (printer ink levels etc.) which got mine to 90%, I always switch off Avast once downloads start, I ran RegHunter to clean registry fixed about 20 errors, and when I returned to updates window it had completed and second update had reached 50%.

Re-booted and updated completed in about 10 minutes, the usual 3 phase process. No nasty surprises all seems good so far.
Will post if I find any Easter Eggs or problems.

 

Interesting, so much talk about this here and when it will be fixed or if ever...ongoing saga.

 

Running this with a WIM based ISO fixes it, but it will come back next build. Soooo, it's a temp fix which doesn't really do much.

1. Mount the .ISO file.

2. Open 'Windows Powershell' or 'Command Prompt' with Admin privileges.



3. DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

--------------------------------> Note: replace "X" with the drive letter of mounted ISO.


4. Now repair any damage in the system files.


5. sfc /scannow

 

Or what i find reinstalling the NVIDIA Driver brings back right opencl.dll, because if you run SFC and DISM after driver update it will rewrite the Opencl.dll to MS one. I had done that for other reasons before what you listed i am familiar with use of WIM file, long story here..........
SFC some corrupt files can not be fixed

 

Thanks for the info. *Smile