If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#31
|
|||
|
|||
Windows folder excessively large
Rene Lamontagne wrote:
On 08/27/2018 8:15 PM, Ken Springer wrote: On 8/27/18 12:35 PM, Ralph Fox wrote: On Mon, 27 Aug 2018 07:08:00 -0600, Ken Springer wrote: Ran some of the typical clean up programs, found nothing. Virus scan, SuperAntiSpyware, Adware Cleaner, and Malwarebytes. Not a single issue found. What about the built-in Windows Disk Clean-up? I'm looking for ideas as to how to discover what is using up the space, or at least telling W10 the space is in use. Run Windows Disk Clean-up, click the button "Clean Up System Files", and while in "Clean Up System Files" check the space used by (for example) "Windows Update Clean-up". To run Windows Disk Clean-up (a) Right-click on the drive in Windows Explorer and choose "Properties". On the Properties pop-up, "General" tab, click the button "Disk Clean-up". or, (b) Click on the search magnifying glass icon on the taskbar and type "Disk Clean-up". Hi, Ralph, Disk Cleanup of System Files was one of the first things I did. :-) Why is disk cleanup so cussedly slow when you tick the windows update cleanup box. I know there are a lot of compressed files to do but this is really slow, Any way to do a manual delete of this stuff, not knowing where its stored? Rene This doesn't answer your question, but it kinda hints at what might be involved. https://www.techrepublic.com/blog/wi...dows-7-and-8x/ The claim is, cleaning up Windows Update either deletes files or it compresses files. Installed programs on your computer, may have dependencies on WinSxS contents. The Windows Update function, knows what software is on the computer, and knows the dependencies. It may be using a "manifest" file which is part of the installed program itself. Scanning all the packages takes time. In the example, WinSxS has 58000 files. Comparing the files to the scanned results could take time. I think I've found compressed files in the past from this operation, but it's hard to say if the three hours it took to make those, is purely a function of the compression operation. I thought in the past, I could squeeze about 30NB/sec out of NTFS compression, so to compress 3GB of content should not take 3 hours (based on compression alone). Knowing how evil this stuff is, I would blame the Windows Update subsystem itself for the delay. I tried to reproduce this, but as the article says, the "option" to do this is only offered if content is found. And I wasn't able to generate a scenario that made rubbish appear. And if, by using an older OS, I trigger an OS Upgrade and not a Windows Update Cumulative, it might wipe the state of that stuff anyway (the system would conclude the freshly upgraded OS was in an optimal state). Also, lots of this stuff is single threaded. So it's not like buying a 32-core processor makes all maintenance go faster. The best you could do, is buy a 5GHz processor and rely on the tiny speed bump, "to make it seem you were winning" :-) Paul |
Ads |
#32
|
|||
|
|||
Windows folder excessively large
On 08/28/2018 8:39 PM, Paul wrote:
Rene Lamontagne wrote: On 08/27/2018 8:15 PM, Ken Springer wrote: On 8/27/18 12:35 PM, Ralph Fox wrote: On Mon, 27 Aug 2018 07:08:00 -0600, Ken Springer wrote: Ran some of the typical clean up programs, found nothing.Â* Virus scan, SuperAntiSpyware, Adware Cleaner, and Malwarebytes.Â* Not a single issue found. What about the built-inÂ* Windows Disk Clean-up? I'm looking for ideas as to how to discover what is using up the space, or at least telling W10 the space is in use. Run Windows Disk Clean-up, click the button "Clean Up System Files", and while in "Clean Up System Files" check the space used by (for example) "Windows Update Clean-up". To run Windows Disk Clean-up Â* (a)Â* Right-click on the drive in Windows Explorer and choose "Properties". Â*Â*Â*Â*Â*Â* On the Properties pop-up, "General" tab, click the button "Disk Clean-up". or, Â* (b)Â* Click on the search magnifying glass icon on the taskbar and type Â*Â*Â*Â*Â*Â* "Disk Clean-up". Hi, Ralph, Disk Cleanup of System Files was one of the first things I did.Â* :-) Why is disk cleanup so cussedly slow when you tick the windows update cleanup box. I know there are a lot of compressed files to do but this is really slow, Any way to do a manual delete of this stuff, not knowing where its stored? Rene This doesn't answer your question, but it kinda hints at what might be involved. https://www.techrepublic.com/blog/wi...dows-7-and-8x/ The claim is, cleaning up Windows Update either deletes files or it compresses files. Installed programs on your computer, may have dependencies on WinSxS contents. The Windows Update function, knows what software is on the computer, and knows the dependencies. It may be using a "manifest" file which is part of the installed program itself. Scanning all the packages takes time. In the example, WinSxS has 58000 files. Comparing the files to the scanned results could take time. I think I've found compressed files in the past from this operation, but it's hard to say if the three hours it took to make those, is purely a function of the compression operation. I thought in the past, I could squeeze about 30NB/sec out of NTFS compression, so to compress 3GB of content should not take 3 hours (based on compression alone). Knowing how evil this stuff is, I would blame the Windows Update subsystem itself for the delay. I tried to reproduce this, but as the article says, the "option" to do this is only offered if content is found. And I wasn't able to generate a scenario that made rubbish appear. And if, by using an older OS, I trigger an OS Upgrade and not a Windows Update Cumulative, it might wipe the state of that stuff anyway (the system would conclude the freshly upgraded OS was in an optimal state). Also, lots of this stuff is single threaded. So it's not like buying a 32-core processor makes all maintenance go faster. The best you could do, is buy a 5GHz processor and rely on the tiny speed bump, "to make it seem you were winning" :-) Â*Â* Paul OK Paul. here is the story I just did a couple days ago, My C: drive had grown from about 28GB to about 39.6 GB so I decided to run disk cleanup and see if I could shrink it back, In disk cleanup system files I found about 250 MB plus 4.5 GB in windows update cleanup.So I ticked its box and let er rip (slowly) and then went for dinner and a game of cribbage with my Son. When I got back I ran it up tothe analyse mode and it showed that That windows update cleanup was now down to 11 MB, So it did OK, Did a cold boot on the System and Checked C: drive and it was at about 38.1 GB!!! Crap! I only gained about 1.5 GB instead of the 4.7 I thought I would. This was just an exercise to see what was happening, I don't need the space There is at least 60 GB free on the SSD. Rene |
#33
|
|||
|
|||
Windows folder excessively large
Rene Lamontagne wrote:
On 08/28/2018 8:39 PM, Paul wrote: Rene Lamontagne wrote: On 08/27/2018 8:15 PM, Ken Springer wrote: On 8/27/18 12:35 PM, Ralph Fox wrote: On Mon, 27 Aug 2018 07:08:00 -0600, Ken Springer wrote: Ran some of the typical clean up programs, found nothing. Virus scan, SuperAntiSpyware, Adware Cleaner, and Malwarebytes. Not a single issue found. What about the built-in Windows Disk Clean-up? I'm looking for ideas as to how to discover what is using up the space, or at least telling W10 the space is in use. Run Windows Disk Clean-up, click the button "Clean Up System Files", and while in "Clean Up System Files" check the space used by (for example) "Windows Update Clean-up". To run Windows Disk Clean-up (a) Right-click on the drive in Windows Explorer and choose "Properties". On the Properties pop-up, "General" tab, click the button "Disk Clean-up". or, (b) Click on the search magnifying glass icon on the taskbar and type "Disk Clean-up". Hi, Ralph, Disk Cleanup of System Files was one of the first things I did. :-) Why is disk cleanup so cussedly slow when you tick the windows update cleanup box. I know there are a lot of compressed files to do but this is really slow, Any way to do a manual delete of this stuff, not knowing where its stored? Rene This doesn't answer your question, but it kinda hints at what might be involved. https://www.techrepublic.com/blog/wi...dows-7-and-8x/ The claim is, cleaning up Windows Update either deletes files or it compresses files. Installed programs on your computer, may have dependencies on WinSxS contents. The Windows Update function, knows what software is on the computer, and knows the dependencies. It may be using a "manifest" file which is part of the installed program itself. Scanning all the packages takes time. In the example, WinSxS has 58000 files. Comparing the files to the scanned results could take time. I think I've found compressed files in the past from this operation, but it's hard to say if the three hours it took to make those, is purely a function of the compression operation. I thought in the past, I could squeeze about 30NB/sec out of NTFS compression, so to compress 3GB of content should not take 3 hours (based on compression alone). Knowing how evil this stuff is, I would blame the Windows Update subsystem itself for the delay. I tried to reproduce this, but as the article says, the "option" to do this is only offered if content is found. And I wasn't able to generate a scenario that made rubbish appear. And if, by using an older OS, I trigger an OS Upgrade and not a Windows Update Cumulative, it might wipe the state of that stuff anyway (the system would conclude the freshly upgraded OS was in an optimal state). Also, lots of this stuff is single threaded. So it's not like buying a 32-core processor makes all maintenance go faster. The best you could do, is buy a 5GHz processor and rely on the tiny speed bump, "to make it seem you were winning" :-) Paul OK Paul. here is the story I just did a couple days ago, My C: drive had grown from about 28GB to about 39.6 GB so I decided to run disk cleanup and see if I could shrink it back, In disk cleanup system files I found about 250 MB plus 4.5 GB in windows update cleanup.So I ticked its box and let er rip (slowly) and then went for dinner and a game of cribbage with my Son. When I got back I ran it up tothe analyse mode and it showed that That windows update cleanup was now down to 11 MB, So it did OK, Did a cold boot on the System and Checked C: drive and it was at about 38.1 GB!!! Crap! I only gained about 1.5 GB instead of the 4.7 I thought I would. This was just an exercise to see what was happening, I don't need the space There is at least 60 GB free on the SSD. Rene To study it here, I need the "right kind of messed up VM", and I'm still trying to find one :-) My Easy Bake Oven doesn't bake these things very fast. Paul |
#34
|
|||
|
|||
Windows folder excessively large
Rene Lamontagne wrote:
Why is disk cleanup so cussedly slow when you tick the windows update cleanup box. I know there are a lot of compressed files to do but this is really slow, Any way to do a manual delete of this stuff, not knowing where its stored? Rene I finished my first test run, and it took maybe 1 hour 15 minutes. The ProcMon trace was 55GB in size. I ran out of space several times, so it took a while to get a good run. And the trace, if you start examining it, has "holes" with not a lot going on. These are periods of time where not a lot of traceable material shows up in ProcMon. My guess is, the time is spent "thinking" rather than "compressing". I can find a section of the trace, where it processes 3 files per minute. Which isn't a particularly good rate, if there are thousands of files. I see a lot of TiWorker running, using one core. The same sort of activity you see on an older OS, when Windows Update is railed :-/ It's pretty hard to compare the file logs and spot trends. But one thing I noticed, is when checking some "WofCompressed" entries in the "after_cleanmgr" file, the file in question was also "WofCompressed" in the "before_cleanmgr" file. Somehow, I'm going to need to process the two text files, and see if there are any instances of compression (during cleanmgr run) at all. Paul |
#35
|
|||
|
|||
Windows folder excessively large
On 08/30/2018 12:59 AM, Paul wrote:
Rene Lamontagne wrote: Why is disk cleanup so cussedly slow when you tick the windows update cleanup box. I know there are a lot of compressed files to do but this is really slow, Any way to do a manual delete of this stuff, not knowing where its stored? Rene I finished my first test run, and it took maybe 1 hour 15 minutes. The ProcMon trace was 55GB in size. I ran out of space several times, so it took a while to get a good run. And the trace, if you start examining it, has "holes" with not a lot going on. These are periods of time where not a lot of traceable material shows up in ProcMon. My guess is, the time is spent "thinking" rather than "compressing". I can find a section of the trace, where it processes 3 files per minute. Which isn't a particularly good rate, if there are thousands of files. I see a lot of TiWorker running, using one core. The same sort of activity you see on an older OS, when Windows Update is railed :-/ It's pretty hard to compare the file logs and spot trends. But one thing I noticed, is when checking some "WofCompressed" entries in the "after_cleanmgr" file, the file in question was also "WofCompressed" in the "before_cleanmgr" file. Somehow, I'm going to need to process the two text files, and see if there are any instances of compression (during cleanmgr run) at all. Â*Â* Paul Thanks for the research Paul, I guess in the future I will only clean up that item when it is too big and I have time to spare. Rene |
#36
|
|||
|
|||
Windows folder excessively large
In article
Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Nathan |
#37
|
|||
|
|||
Windows folder excessively large
On 8/30/18 3:07 PM, Nomen Nescio wrote:
In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. I shrunk up the pagefile size, and made it a fixed size. There were no Windows.old folders, that's one of the things I looked for. I'll have to go and read the DISM stuff, to figure out which command may fix that. WinDirStat is downloaded. Big problem now, is, I can't seem to get my friend interested in doing this. 2 email about it have gone unanswered. :-( -- Ken Mac OS X 10.11.6 Firefox 59.0.1 (64 bit) Thunderbird 52.6.0 "My brain is like lightning, a quick flash and it's gone!" |
#38
|
|||
|
|||
Windows folder excessively large
On 8/27/18 8:51 AM, Big Al wrote:
On 08/27/2018 10:46 AM, Rene Lamontagne wrote: On 08/27/2018 9:12 AM, Keith Nuttle wrote: On 8/27/2018 9:08 AM, Ken Springer wrote: And his hard drive is just 120GB, an SSD.Â* The drive in my computer is just over 20GB. Check the temp folders,Â* and the softwaredistribution folder in Windows, Nearly every thing can be deleted in these folders except those that belong to the OS system You might like Windirstat or Treesize among others. Rene +1 treesize free https://www.jam-software.com/treesize_free/ +1 C:\windows\SoftwareDistribution. When I have issues installing a new update or build I delete softwaredistribution totally and it usually clears things up. I find nearly 7+ gigs in there. Deleting all the files may not be a good solution. Yesterday, I discovered I have the same space issue on my W7 system. Decided to try your solution, but discovered Windows permissions really get in the way. Ran a Linux live CD, deleted the first 204 files. Rebooted into W7, and Avast would not run. Solved that by uninstalling, then reinstalling Avast. Was that issue related to my removal of the files? I don't know, but think I'll use the DISM solutions I've found. -- Ken Mac OS X 10.11.6 Firefox 59.0.1 (64 bit) Thunderbird 52.6.0 "My brain is like lightning, a quick flash and it's gone!" |
#39
|
|||
|
|||
Windows folder excessively large
On 9/1/18 1:47 PM, Ken Springer wrote:
On 8/30/18 3:07 PM, Nomen Nescio wrote: In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. I shrunk up the pagefile size, and made it a fixed size. There were no Windows.old folders, that's one of the things I looked for. I'll have to go and read the DISM stuff, to figure out which command may fix that. WinDirStat is downloaded. Big problem now, is, I can't seem to get my friend interested in doing this. 2 email about it have gone unanswered. :-( My friend got back to me, and I logged in via Teamviewer. We've got some preliminary work to do, such as copying his files to a safe location so we don't lose them. Then, we'll tackle the problem. Tried WinDirStat and Tree Filesize. Love those programs! -- Ken Mac OS X 10.11.6 Firefox 59.0.1 (64 bit) Thunderbird 52.6.0 "My brain is like lightning, a quick flash and it's gone!" |
#40
|
|||
|
|||
Windows folder excessively large
In article
Ken Springer wrote: On 8/30/18 3:07 PM, Nomen Nescio wrote: In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. That's a typo... SVI... home to System Restore. C:\windows\SoftwareDistribution... don't touch that unless you see software that is no longer installed. It would be worth running Win's "Disk Cleanup" (as Administrator) to see what Win things is safe to remove. WinSxS I just cleared 10GB of junk in WinSxS/PendingRenames... In a command window... Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore followed by... Dism.exe /online /Cleanup-Image /StartComponentCleanup hxxps://www.techsupportalert.com/content/how-check-size-and-reclaim-disk-space-winsxs-windows-81.htm Nathan |
#41
|
|||
|
|||
Windows folder excessively large
Nomen Nescio wrote:
In article Ken Springer wrote: On 8/30/18 3:07 PM, Nomen Nescio wrote: In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. That's a typo... SVI... home to System Restore. C:\windows\SoftwareDistribution... don't touch that unless you see software that is no longer installed. It would be worth running Win's "Disk Cleanup" (as Administrator) to see what Win things is safe to remove. WinSxS I just cleared 10GB of junk in WinSxS/PendingRenames... In a command window... Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore followed by... Dism.exe /online /Cleanup-Image /StartComponentCleanup hxxps://www.techsupportalert.com/content/how-check-size-and-reclaim-disk-space-winsxs-windows-81.htm Nathan That suggests your PendingRenames never worked properly since the last OS Upgrade. My PendingRenames has 0 bytes in it, the PendingDeletes has 200MB (91 files). Maybe there's a Component Based Servicing (CBS) log with details of the failure ? When you run "winver", is the OS version current, or does that indicate a jam-up too ? Look in the Windows Update history and see if there's an update that failed, that never succeeded on later attempts. You would think a Cumulative could clear that, but I don't know that for sure. Paul |
#42
|
|||
|
|||
Windows folder excessively large
On 9/3/18 10:04 AM, Nomen Nescio wrote:
In article Ken Springer wrote: On 8/30/18 3:07 PM, Nomen Nescio wrote: In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. That's a typo... SVI... home to System Restore. C:\windows\SoftwareDistribution... don't touch that unless you see software that is no longer installed. It would be worth running Win's "Disk Cleanup" (as Administrator) to see what Win things is safe to remove. That's been run already, but not as administrator. I'll put it on the list for our next get together. WinSxS I just cleared 10GB of junk in WinSxS/PendingRenames... In a command window... Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore followed by... Dism.exe /online /Cleanup-Image /StartComponentCleanup hxxps://www.techsupportalert.com/content/how-check-size-and-reclaim-disk-space-winsxs-windows-81.htm Nathan DISM as administrator? -- Ken Mac OS X 10.11.6 Firefox 59.0.1 (64 bit) Thunderbird 52.6.0 "My brain is like lightning, a quick flash and it's gone!" |
#43
|
|||
|
|||
Windows folder excessively large
Ken Springer wrote:
DISM as administrator? Why not ? You're changing OS files. That sounds like a perfect job for an administrator. If you don't, chances are a UAC prompt will appear. At least some commands on Windows, I notice they're smart enough to request elevation. Paul |
#44
|
|||
|
|||
Windows folder excessively large
On 9/3/18 10:04 AM, Nomen Nescio wrote:
In article Ken Springer wrote: On 8/30/18 3:07 PM, Nomen Nescio wrote: In article Ken Springer wrote: I've got a friend with Windows 10 on a recent Dell laptop. He's currently on the road, so as of this writing, I can't get you the latest and greatest info about the system. I do know the latest W10 update is not installed due to insufficient space. His Windows folder is just over 70GB in size! And his hard drive is just 120GB, an SSD. The drive in my computer is just over 20GB. First, I'd look in SVT for orphaned system restore files and in Advanced Settings for page file size, and /WinSxS/Temp, /Local/Temp for stuff gumming up the system. Obviously Win.Old folders holding rollback files can contribute bad stuff. Then I'd scan using the free, portable Wise Disk Cleaner and examine the results it finds. I might also run DISM to reset the base of updates in case they are holding a massive file store. WinDirStat can be helpful as well. Hi, Nathan, SVT, as it relates to this issue, is a new one on me. That's a typo... SVI... home to System Restore. C:\windows\SoftwareDistribution... don't touch that unless you see software that is no longer installed. It would be worth running Win's "Disk Cleanup" (as Administrator) to see what Win things is safe to remove. WinSxS I just cleared 10GB of junk in WinSxS/PendingRenames... In a command window... Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore followed by... Dism.exe /online /Cleanup-Image /StartComponentCleanup hxxps://www.techsupportalert.com/content/how-check-size-and-reclaim-disk-space-winsxs-windows-81.htm Nathan I thought I'd try this on my W10 system, even though the drive has no problem with free space. My SXS folder only had 9.6 GB of files. It took 5 tries to the get the component cleanup to successfully finish, but I regained just over 3 GB of space!!! I opened the command window as an administrator. Real eyeopener for me! I'm going to have to find out if this can be done in Windows 7! G Thank you very much, Nathan! -- Ken Mac OS X 10.11.6 Firefox 59.0.1 (64 bit) Thunderbird 52.6.0 "My brain is like lightning, a quick flash and it's gone!" |
#45
|
|||
|
|||
Windows folder excessively large
Ken Springer wrote:
.... I'm going to have to find out if this can be done in Windows 7! G Nope: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7601.23403 Error: 87 The analyzecomponentstore option is not recognized in this context. For more information, refer to the help. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log -- Quote of the Week: "For example, the tiny ant, a creature of great industry, drags with its mouth whatever it can, and adds it to the heap which she is piling up, not unaware nor careless of the future." --Horace, Satires, Book I, I, 33. Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly. /\___/\Ant(Dude) @ http://antfarm.home.dhs.org / http://antfarm.ma.cx / /\ /\ \ Please nuke ANT if replying by e-mail privately. If credit- | |o o| | ing, then please kindly use Ant nickname and URL/link. \ _ / ( ) |
Thread Tools | |
Display Modes | Rate This Thread |
|
|