📎 AI Summary:
The thread discusses how a system-generated Temp folder, related to Windows Sandbox, was consuming significant storage and was difficult to delete. The original poster seeks solutions for removing persistent Sandbox remnants, and ChatGPT provides troubleshooting steps such as booting into Safe Mode, using command-line tools, checking for locked handles, and disabling Windows Sandbox. Ultimately, the user resolves the issue by running DISM, confirming that the problem was successfully fixed.
Hybrid30

Hybrid30

Member
Member details
Joined
Mar 15, 2025
Messages
2
Thread Author #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
    Microsoft Defender: No threats detected Scan details
  • Screenshot 2025-03-15 115531.webp
    Screenshot 2025-03-15 115531.webp
    61.2 KB · Views: 0
    Microsoft Defender: No threats detected Scan details
  • Screenshot 2025-03-15 115800.webp
    Screenshot 2025-03-15 115800.webp
    87.2 KB · Views: 0
    Microsoft Defender: No threats detected Scan details
Solution
WindowsForum AI
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:
  • 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.
  • Use an Elevated Command Prompt: • Open a Command Prompt as administrator...
Sort by date Sort by votes
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
119,004
#2
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:
  • 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.
  • 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).
  • 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.
  • 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).
  • 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
 
Upvote 1 Downvote
Solution
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
119,004
#4
It looks like the "MicrowinScratch_20241209_151733_2503" folder is related to Windows Sandbox. Sometimes, these folders remain in your Temp directory as remnants when Windows Sandbox is used, and they can indeed take up considerable space. Here's how you can try to regain that storage space:
  1. Boot into Safe Mode:
    • Restart your Windows in Safe Mode to minimize running processes.
    • Once in Safe Mode, attempt to delete the folder using File Explorer or with an elevated Command Prompt.
  2. Use an Elevated Command Prompt:
    • Open Command Prompt as an administrator.
    • Use the RD command with force to delete the folder:
      rd /s /q "C:\Path\To\Your\Temp\MicrowinScratch_20241209_151733_2503"
    • Ensure to adjust the path as needed for your Temp folder location.
  3. Check for Locked Handles:
    • Use a tool like Process Explorer to search for any handles that might be in use. Close any that are locking the folder, and then try deleting it again.
  4. Mark for Deletion on Reboot:
    • Consider using MoveFile utility from Sysinternals to schedule the deletion of the folder at the next reboot.
  5. Disable Windows Sandbox:
    • If you're not using Windows Sandbox, you might want to disable it via Windows Features to prevent similar issues. Just search for “Turn Windows features on or off” and uncheck Windows Sandbox.
These steps should help you deal with the folder without affecting system functionality. If you encounter more issues, feel free to ask for further assistance!
 
Upvote 0 Downvote
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
119,004
#6
Great to hear that running DISM fixed the issue and removed the folder! 🚀 If you run into any more hiccups with storage or Windows Sandbox, feel free to drop back in. Happy computing!
 

Upvote 0 Downvote
You must log in or register to reply here.