New
#11
Plug56...... can you give us that Disk Management screenshot, please? MiniTool or Aoemi or similar would be better.
Plug56...... can you give us that Disk Management screenshot, please? MiniTool or Aoemi or similar would be better.
Since you already have a drive letter assigned to the System Reserved partition, open Disk Cleanup, select that drive letter, and run the cleanup.
When you're done, remove the drive letter.
Please run:
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.
LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.
V2 and DM: BSOD - Posting Instructions - Windows 10 Forums (tenforums.com)
How to Upload and Post Screenshots and Files at Ten Forums
For share links please use one drive, drop box, or google drive
1. Disc cleanup has zero effect on this problem. Tried it anyway, it sees NOTHING to be cleaned up.
2. The longer I think about it, the more sure I am that this is some sort of unseen logging into the SRP. There is out there a small set of commands, probably PowerShell, that remove the log and recreate it back at normal size. And one of the commands lets you check the size. The log is hidden in a way that even showing hidden files in Explorer does not work.
3. This is not fixable with DISM.
4. No idea if SFC would check an invisible log.
5. THe disk management screen looks normal except that I assigned drive letter Z to SRP. Yes, it opens in Explorer. You can explore it in a tree size utility, and it shows maybe 50MB in use, which is quite acceptable. But it is lit up all red when you look in Explorer at your drives, warning only 4MB free.
When you post the above results help can be provided.
Which results? None of these are connected to the problem. Partitions are normal. It's not an issue with system images. Disc clean doesn't fix this. It's a known problem. People enlarge their SRP to deal with it but that's not a fix. MS tells you to delete font files but that's just a short term fix. It is something that I recall being a log that on SOME systems just keeps growing completely out of sight. I had this once before in trying to get Windows Backup working. It uses the SRP as a temp space to organize, so when SRP fills it stops WB from running. The problem is that without the right tool you can't see or fix it. And rebuilding SRP from scratch is very dangerous.
When you want help please post the results for post #13.
Assigning a letter to SRP was not needed.
There is no problem with the SRP.