Cumulative Update KB4041676 Windows 10 v1703 Build 15063.674

Well... Updated just today, I have a USB Type C connector but I'm unsure if I should have problems or not (is not in use... what can use that connector anyways? XD) I've rebooted a couple of times and shuted down the machine, all is perfect... Not even slowdowns, BUT, seems now windows is using less RAM? O_O

Glad it's not just me. Oops, sorry, that didn't sound right.

Since I did this update, my machine won't wake up from sleep. When the mouse if moved, sometimes the screen will flash on for an instant then go back to dark. I can press Win+L and get the lock screen and all is OK. Problem is, I have to enter a password, which is aggravating. Hope that's fixed soon, I use sleep mode.


First ever Win 10 update or patch failure.

Sorry to those who had issues, but FYI, today I've updated 2 very under-powered Win10 Pro desktops, 1 well-specced W10 Home laptop and finally 1 hi-spec W10 Pro desktop.

Did all of them (in series) over a 4 hour period, checking each one as I went.

All now on Winver 1703 (OS Build 15063.674)

Everything worked first time on all systems -all Event Logs clean.

My main PC did the whole process in 20 minutes and also proved to me for the first time that setting Quality updates to "Deferred for 4 days" works. (I'm on Current Branch for Business on my main machine) The CU was recognised but didn't download until I set it back to 0 days just as it should.

This was the fastest and easiest update since I went to 1703 - beer time!

This update has Failed to Install 14 times (!) in the last two days, twice of those, today -- and all without any error message indicating why.

But NOW, the desktop shows Up to Date -- even though the last update failed (like all the others).

So, does this indicate that MS has pulled this update now?

The CU installed to 15063.674 just fine in both machines but an old issue cropped up in my laptop. I use a wireless MS mouse and have the touchpad disabled but since the Oct 10 CU the touchpad keeps re-enabling it's self. If I go to settings and re-enable it, then turn it off, and then restart it disables but on the next boot will it will re-enable on it's own. When I then go thru settings to look it is still disabled(and "Leave touchpad on when a mouse is connected" is still not ticked). Device manage does not show a driver to roll back to. The mouse did not come with a driver and is now using a MS driver version 10.0.15063.0 which is the same it has had since 15063 came out so I think the driver was not changed during the install of the October CU. This causes me issues typing text for emails or even this post if I accidentally touch the touchpad while typing. I fixed this issue which originally began after installing creators update by disabling the touchpad but also had to disable taps thru the additional settings for touchpad. My laptop specs are listed at left of my posts and it has a precision touchpad. Thanks in advance for any ideas to fix this.

Mark Phelps said:

This update has Failed to Install 14 times (!) in the last two days, twice of those, today -- and all without any error message indicating why.

But NOW, the desktop shows Up to Date -- even though the last update failed (like all the others).

So, does this indicate that MS has pulled this update now?

Just a thought - if you do a "Winver" does it show 1703 (OS Build 15063.674)?

If it does, the CU HAS actually installed - even if it says it hasn't.