Windows 10: Cumulative Update KB4034674 Windows 10 v1703 Build 15063.540

I have just finished installing KB4034674 on both of my PCs. Everything went flawlessly smooth and faster than ever






Still no joy, However, with regard to "Advanced Settings" in Windows Firewall & network Protection. See my post #39 in KB4032188, the previous CU:

Cumulative Update KB4032188 Windows 10 v1703 Build 15063.502

 

Installed in the office on 5 systems with no issues so far.

WEK

 

I got new update everything running fine so far. *Thumbs

 

Installed via Update on gaming MSI laptop....found it impossible to get Logitech MX Master mouse to work.
Did a System Restore, spent ages trying again to reinstall mouse, eventually managed to install another Bluetooth mouse which seemed to fire up the MX mouse although trying to control pointer speed proved almost impossible.
Reinstalled this latest Cumulative update which then restored things back to normal...what a kerfuffle.

 

Downloading the update now. Thanks Brink.

 

Somehow it installed. Unfortunately the update procedure (or rather preparation for it) started right after logging in this evening. You guessed it already: that meant a lot of waiting for scanning, downloading, unpacking etc. Windows should wait 15 min or so with checking for updates after booting, in my opinion. Would make the whole process a lot faster. And it would avoid a rather stupid ESENT 508-warning. Because of the fact that it took 28 seconds to write something to "C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log" Windows suspects a hardware error of 'some device'. Duh. When harddisk usage is around 100% for some time because of unpacking / updating and scanning (the malicious software tool got an update and started to get busy ALSO) it just 'might' take some time before something gets written completely. Windows update is obviously not even recognizing its own activity during updating. Sigh. Anyway, saw this event id 508 on another system also now and then , for example during an Office update directly after logging in. Why on earth not waiting those 15 minutes and give some breathing space right after logging in???

 

Had the standard 35-40 min turnaround time with no apparent problems

 

Downloaded and installed this CU fine, although interestingly, after it notified me to restart the system I ran Windows Update again after the restart and the same update appeared again and it downloaded and installed what appeared to be a second time, but this time with no reboot required.

Thanks Shawn!

 

System Rebooted even though I did the no automatic reboot workaround back in the Anniversary Edition but probably got overwritten when I did a in-place upgrade of Creators Update back in early June 2017. The system never rebooted on it's own. My last reboot was on August 5, 2017 and it seems like KB4032188 failed to install as it probably required a reboot to do it but seems like KB4034674 installed successfully per the updates history.

 

aww crap, arabic is my second language....

 

Update installed on multiple systems with no issues *Smile

 

Looks like a very old Windows 10 problem re-appeared after this update. SPP-errors during the creation of a manual restore point. What seems to help is switch off system restore and then on again. Right now restoring an image, saw some more weird things. Hopefully re-installing the updates will give a better result :-/

 

It seems that KB4034674 turned System Restore off. I just checked and my System Restore was turned off. However I had a restore point for 8/8 when KB4034674 was installed, plus a few earlier ones.

 

I think system restore is very unreliable anyway. I create restore points out of some automatism. While actually knowing the chance of a successful restore is not that big. Anyway, besides the SPP-errors I also saw an ESENT-warning regarding possible hardware problems. Nonsense of course, because it was just about a file write that took way too long. Logical, because of the update preparations that were running. I think. But together with the restore point errors I prefer to play on safe. Which means I will lose once again a large part of a working day on trying to tame Windows 10. *Sad

 

Further to my earlier post #17....this update does seem to have affected Bluetooth mouse settings.
Having had problems with my MSI gaming laptop....find it also affected my Surface Pro 4 with a different Logitech M535 Bluetooth mouse.
Thankfully did not have to do a System Restore this time to sort it out.