New
#21
Try Hiren’s BootCD.
Perhaps it will help others to help you more if you explain just what you did to create those folders. The original size made it sound more like an installation than a set of ISO contents.
A common method of creating an installation USB from an ISO is
1 Get an existing bootable USB for re-use or make a USB bootable using Diskpart commands
2 Mount the ISO by double-clicking on it - it will then appear as a drive in File explorer
3 Drag the whole contents of the mounted ISO's drive onto the USB
You did something different. What was it?
Denis
This was 3 years ago, so it's difficult to recall all of the details. From what I can recall, I created a backup of Windows 10 using the Windows Media Creation tool and selected the USB flash drive option instead of the ISO file. I don't recall any issues at the time creating the bootable USB following the prompts in the MCT.
Later I noticed the 'bin' folder in downloads and saw these were system files but wasn't entirely sure where they originated from but assumed they may have been related to creating the recovery USB. It's entirely possible I inadvertently downloaded these to my computer but I don't remember doing so intentionally.
Had to run out for a bit....
Have to agree with Try3. That looks like a bare bones Windows installation. Minimal Windows folder and virtually empty Prog directories. Since it was a year ago, you may have difficulty recalling exactly what you where doing.
This small app is very powerful, use with caution. It will run virtually anything as user TrustedInstaller, the highest possible set of permissions on the system. Higher than Administrators, higher than System. It will allow you to run a command prompt (and other apps) as TrustedInstaller. It will allow you to delete that TMP and all inside.
Please use caution, and you should have an image backup before running.
Will check back later.
PowerRun v1.3 (Run with highest privileges)
Just to be certain about your current OS, paste this into a command window
- I imagine that it will point to C:\Windows, which is to be expected.Code:echo %windir%
- If it points to anything else, such as the set of folders that this thread is about, then the probem is much more complicated.
I don't want to scare you. It is just something that needs to be checked that will probably turn out to be alright.
Denis
Drop a shortcut to cmd.exe [or the cmd.exe file itself] onto the PowerRun{_x64}.exe file and it will open with System privileges that should allow you to do what you want.
If not then re-read the PowerRun webpage about setting it to TrustedInstaller 'identity' which should do the job.
Denis
OK, so I dropped cmd.exe into PowerRun and when I open that in PR, it shows the following:
C:\Users\mhan\Downloads\PowerRun>
What is the proper command to fully delete the 'bin' folder and all its subfolders/files?
I tried rmdir /s/q bin but that did not find the specified path. I apologize if this seems obvious but I don't use cmd very much at all .
Hi,
I recently had success removing a stubborn file using FILEASSASSIN?