New
#50
Cumulative Update KB3197954 Windows 10 PC and Mobile build 14393.351
-
-
-
-
New #53
DiskCleanup (maitenance cleans up some space, but yes, the space is increasing over time.
I use WiseCare to cleanup Windows Update's cache (not SoftwareDistribution's folder).
I also run this command to clean up WinSxS (but it prevents uninstalling of updates).
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Not only it decreases space usage, it also makes the next update to run more smoothly.
-
New #54
The disk clean up is odd in W10 and not that much better than W8.1
For some reason I get different behaviour between 32 and 64 bit installs which isn't a one off by the way. Once again the x64 version shows 3.99Tb to free up (go figure !) and takes around 30 minutes of presumably full CPU usage to complete. Having to go through this every couple of weeks makes W10 less than environmentally friendly imo. The x86 install flies through its clean up but frees little space. This is again consistent behaviour for me with the x86 version.
So around 1Gb freed up with x64 and around 0.1Gb for the x86
-
-
New #56
My 8 machines are now all updated. Had problems with only one: the Surface Pro 3 running RP didn't grab and install correctly until a third try (had already downloaded the Catalog item, but ended up not having to install it). It does leave another 3.99 TB worth of Windows Update files behind for cleanup
! Knowing now that it takes a while to complete that work, and that a subsequent reboot is needed to finish cleanup, I just let it run on most machines. Took almost 50 minutes on my slowest machines, over 40 minutes on my fastest ones to complete. All good now, but an interesting evening last night...
--Ed--
-
New #57
It's not exactly a bug, there really are 3.99TB of ntfs directory entries to clean up (or more, 3.99TB is probably just the highest number it can count up to). The fact that 99.9% of them are hard links that don't actually occupy additional physical disk space makes little difference, Disk Cleanup still has to delete them, hard links and all - and boy does it take its time doing it, over an hour for me this time round.
The real bug is why some cumulative updates produce an excessive number of hard links in the first place.
More explanations of the '3.99TB' here...
Cumulative Update KB3194798 for Windows 10 PC & Mobile build 14393.321...hard links (NTFS entries that allow multiple directory listings of a single physical copy of a file). These are frequently used in WinSxS to avoid having multiple copies of the same file when it is a part of several updates.
...and here in @EdTittel's blog: http://itknowledgeexchange.techtarge...m-500gb-drive/
-
New #58
Updated Cumulative Update KB3197954 which installed fine. The only issue I experienced, so far, was ie11 would not load. A reset of ie11 fixed the issue.
-
-
New #59
Lenovo W10 64bit dead with KB3197954
Lenovo laptop W10 64bit on Ethernet. Screen showed boot now or boot later, I assume that KB3197954 downloaded and installed partly and should finish installing with the reboot. Booted to the Lenovo splash screen and sat there spinning for 6 hours. Powered down by holding pwr button. After a minute I pushed pwr button - camera light came on briefly and then turned off. Screen black w/ no sign that pwr is on. Pushed pwr button and probably the laptop pwr'd off. After a minute I pushed pwr button and Lenovo splash screen appeared with additional words below that said "Preparing Automatic repair". and the spinner was spinning. After a half hour of this I called my PC guy who said he will pick up the laptop on Sunday. This is essentially the same scenario that I suffered on this laptop putting on KB3194798 and KB3199209. Computer guy then said it was fixed but...... .
Before this latest the laptop was 1607 14393.321
Installed OK on Dell desktop W10 64bit . Now at 1607 14393.351Last edited by cwr64; 28 Oct 2016 at 19:04.
Quote
Related Discussions
