New
#401
They are still running but unfortunately the scanners are finding nothing. I'm doing full scans on all 6 of my drives. On one hand I'm glad they are finding nothing because who want's infections. However, on some level it might have been nice to discover a big fat infection that could be removed and cure my DISM issue. Not the case I'm afraid.
Malware bytes finished and found a few tracking cookies.
ESET Online Scanner is taking forever but is off of drives C, D and E and is now on drive G and has found no threats.
SUPERAntiSpyware is fast but still running, it's on my last drive which is a USB backup drive. It's found 3276 tracking cookies which is actually 1638 of them and the corresponding 1638 on the backup drive. I think once it's done, it'll have found nothing of consequence.
So we really are back to "what causes DISM to throw the Error:1392?" It doesn't matter how we run it or where we run it from and it doesn't matter if I disconnect everything from the machine save the keyboard and mouse. Obviously I don't have the chops to diagnose this. I'm encouraged that some of you guys are fascinated by this so that maybe you'll not give up and won't stand for letting Windows get the best of you....lol...
Is there a way to run DISM on my file structure from an emergency boot environment?
There seems to be a little confusion here on the "Mount" business.
- If you righ click or double click on the ISO then the ISO will be mounted as a virtual drive with a letter. To unmount it, you just right click on the drive->eject.
- When you mount a WIM file to a folder using DISM, you'd use that folder as a mount point, therefore no drive letter is assigned. You must use DISM to unmount the folder, you cannot just delete the folder.
To mount the install.wim to a folder:
Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount
To unmount from a folder:
Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
NOTE: /discard will unmount the folder with no change. If you change anything and want to re-write the install.wim, you'd use /commit instead.- What essenbe did, he extracted the install.wim to a folder test. Basically, it will extract the files/folders to test folder with the files/folders structure, same as mounted with DISM. However, by doing this, when trying to delete the content of test, he ran into a problem with long path filenames. What could have been done is just to rename the troubled file(s) with a short name(s) then they can be deleted.
EDIT: Just saw @essenbe post. Yep, Robotcopy can also be used.
And that is the problem with long path file(s)/Folder(s) name. These folder became orphaned, no references to them and that's why you cannot delete them. Robotcopy might have done some magic to de-reference these folders.
There's a good program to deal with this but it is not free: ** REMOVED **
Last edited by Brink; 08 May 2017 at 17:53. Reason: removed link to program that spams
@topgundcp
Well no matter how Rob tries to run Dism commands, or where he tries to run it, (3 to 4 different locations) It always fails.
With mostly the same errors over and over... Talking about how to remove that mount folder, is already been solved for Rob.
The biggest problem is no matter how he tries, dism is not able to preform ANY repairs, using the install.wim file.
This is the problem at the moment, which nobody has an answer too as of yet.
Errors are
Version: 10.0.10586.0
Error: 2
The system cannot find the file specified.
OR
Error: 1392
The file or directory is corrupted and unreadable.
and this
This failed: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 1392
The file or directory is corrupted and unreadable.
Tired from desktop, E: drive, and from a USB flash drive.....nothing works.