Cumulative Update KB4034674 Windows 10 v1703 Build 15063.540
-
Odd. It didn't turn it off for either of the two machines I updated.
It didn't turn it off either for me. I just checked and System Restore is working just fine...Besides, 3 or 4 weeks ago, I have created a task in Task Scheduler to make an automatic Restore Point at each reboot and it has been working like a charm. I think this the best way to go with System Restore...
-
-
I dont keep many restore points but the ones I had before the update were still there, and I created one successfully after the update.
Bo
-
I just want to share this information with members of this thread having problems with system restore. Here it is:
Microsoft releases tool to hide or block unwanted Windows 10 updates | ZDNet
Hide or Show Windows Updates in Windows 10 Windows 10 Windows Update Activation Tutorials
UPDATE:
I forgot to mention that the title from the first link from ZDNet can be misleading. What I was referring to is the last paragraph in the same article, which reads as follows:
"By the way, if you find this utility intriguing I recommend one additional Windows 10 tweak. By default, System Restore has been turned off on every system I've tested throughout the preview program. If you re-enable this feature, Windows resumes the practice of automatically creating a restore point before installing each new batch of patches from Windows Update, making it easier to roll back an entire batch of updates while you investigate which one is troublesome"
Last edited by IronZorg89; 10 Aug 2017 at 14:50.
Reason: Addendum
-
Hello. This KB4034674 breaks the merc stealth keyboard software and driver. Has been reported worldwide by every merc stealth "active" user (yes, we are few people). The problem is that this is an oooold (although a very good and rock solid) keyboard and Steelseries (the brand company) has discontinued this item.
In my case, the keyboard is recognized but the software or drive associated with this doesn't work, so I can't make use of macros, special keys, weblinks, profiles... As I've said, it's clear and proved that this KB4034674 is the cause. Reverting the system to a previous state fix the problem.
We can't expect a solution by steelseries side, but maybe a revision or fix by Microsoft side?
Regards.
-
-
My experience today.....
I always set a Restore Point before doing any updates.
Allowed Cumulative Update for Windows 10 Version 1703 KB4034674 and Windows Malicious Software Removal Tool and Flash updates to apply automatically.
Since the Creators Update, ALL my PCs are running with metered network connections, whether WiFi or LAN – this one is LAN.
Cumulative Update download hung at 1% for 3 hours on metered connection. Restarted PC – same again.
Set connection unmetered – all updates downloaded and installed OK in about 15 minutes – usual restart requested, everything seems to work.
Today’s Restore Point is still there as are others from earlier Cumulative Updates plus ones that Windows had created automatically (Windows Module Installer).
Winver now 1703 OS Build 15063.540 Event Viewer showing nothing untoward
-
Cumulative Update download hung at 1% for 3 hours on metered connection. ...
Set connection unmetered – all updates downloaded and installed OK...
Yes, it's been that way since 15063.0. Seems MS haven't quite got their new update policy for 1703 working as intended :)
-
Yes, it's been that way since 15063.0. Seems MS haven't quite got their new update policy for 1703 working as intended :)

And to make it even more confusing, it's inconsistent! The previous CU (KB4032188) on August 2nd went through with the network connection set metered, as (if i recall correctly) did another of my PCs.
Don't we just love MS?
-
Yes, it's been that way since 15063.0. Seems MS haven't quite got their new update policy for 1703 working as intended :)

I think it's working great. If the DL size is too big, the update won't get downloaded over Metered Connection (does not fit the quota, whatever it is). A Virus Definition Update or system policy update is small enough and should be able to get downloaded over Metered connections.
Great that there is that kind of protection. I would not have it any other way. :)
-
I think it's working great. If the DL size is too big, the update won't get downloaded over Metered Connection (does not fit the quota, whatever it is). A Virus Definition Update or system policy update is small enough and should be able to get downloaded over Metered connections.
Great that there is that kind of protection. I would not have it any other way. :)
There is that view and thinking about it, I sort of agree but it's not actually what MS say. OK for people like us on these forums but the average user must be completely mystified!
-
-
I think it's working great. If the DL size is too big, the update won't get downloaded over Metered Connection (does not fit the quota, whatever it is). A Virus Definition Update or system policy update is small enough and should be able to get downloaded over Metered connections.
Great that there is that kind of protection. I would not have it any other way. :)
Except that it doesn't seem to work that way. A cumulative update tries to download over metered connections, but hangs - while virus definitions are apparently not 'required to keep windows running smoothly' so get blocked.