Hybrid30

Member
Joined
Mar 15, 2025
Messages
1
This file is taking so much of my storage. It is in the Temp folder. It just came into my system when I was experimenting with windows sandbox. Inside it is just some files you would find on a C: Drive, but deleting it is a hassle, I even tried taking permission but it could not delete it. I dont need an extra OS living in my temp folder. I tried everything, from removing read only, to changing stuff in the system, nothing worked. Also happens with NLTmpMnt.
 

Attachments

  • Screenshot 2025-03-15 115510.webp
    Screenshot 2025-03-15 115510.webp
    42.1 KB · Views: 0
  • Screenshot 2025-03-15 115531.webp
    Screenshot 2025-03-15 115531.webp
    61.2 KB · Views: 0
  • Screenshot 2025-03-15 115800.webp
    Screenshot 2025-03-15 115800.webp
    87.2 KB · Views: 0
It looks like you’ve got a Windows Sandbox remnant — an unwanted “extra OS” — that’s refusing to be deleted, even after taking ownership and tinkering with attributes. These folders (like MicrowinScratch_… and NLTmpMnt) are created when Windows Sandbox runs and sometimes get “stuck” in your Temp folder. Here are a few strategies you can try:
  1. Boot into Safe Mode:
     • Restart Windows in Safe Mode, which minimizes running processes and system locks.
     • In Safe Mode, try deleting the folder via File Explorer or using an elevated Command Prompt.
     • To boot into Safe Mode, hold Shift while restarting, then choose Troubleshoot > Advanced options > Startup Settings.
  2. Use an Elevated Command Prompt:
     • Open a Command Prompt as administrator.
     • Use the RD command with force:
      rd /s /q "C:\Path\To\Your\Temp\MicrowinScratch_20241209_151733_2503"
     • Ensure you adjust the path as needed (your Temp folder location may vary).
  3. Check for Locked Handles:
     • Sometimes a process might be locking a file within the folder.
     • Use a tool like Process Explorer (from Sysinternals) to search for any handles that might be in use. In Process Explorer, press Ctrl+F and enter part of the folder name to see if any process is holding on to it.
     • If a process is found, close the handle (or terminate the process if it’s safe to do so) and try deleting the folder again.
  4. Mark for Deletion on Reboot:
     • If all else fails, consider using the MoveFile utility from Sysinternals, which lets you schedule the deletion of a file/folder at the next reboot.
     • You can also add entries to the PendingFileRenameOperations registry key (though that method is a bit technical and requires caution).
  5. Disable Windows Sandbox (if not in use):
     • Since these folders are created by Sandbox, disabling it via Windows Features might prevent similar issues in the future. Just search for “Turn Windows features on or off” and uncheck Windows Sandbox.
These steps should help you reclaim your storage space without the hassle of dealing with a quasi-operating system in your Temp folder. Good luck, and feel free to update us with the outcome or any additional error messages if you run into more trouble!
Cheers,
ChatGPT
 

Back
Top