Windows takes two hours to boot every reboot. Goes to spinning circles

RobH2 said:

Yes, gotta savor the small successes. However, it's sort of like, ok, I got my hubcap back on but my car still won't start. I noticed before that the rescue disk was chock full of handy stuff.

I like the way you said that Rob.....lol hopefully at some point in time we can get that dam car running!! :)

RobH2 said:

Running malware scans now.

Later...

Hate to say it, but would be interesting if their was something found....

essenbe said:

I'm having the same/similar problem Rob is having. It is a folder I created yesterday and extracted the install.wim to. It will not delete. The folder shows as empty even with 'show hidden folders' Properties shows 0 files and 9 folders. I have tried the Win10PESE and will not delete even with that. This is the error message

Attachment 72566

This is the properties window

Attachment 72567

I'll keep playing with it and see. I have taken ownership several times.

essenbe said:

This is an excellent online scanner too http://www.eset.com/us/online-scanne...S-BR-C-Other|B

Agreed. It will find things others miss.
@essenbe, even File Assassin won't get rid of it?

Nope, but I managed. I cheated. But, it's gone. Terminated with extreme prejudice.

essenbe said:

Nope, but I managed. I cheated. But, it's gone. Terminated with extreme prejudice.

Sounds like maybe you used a image backup .....

Nope, nothing that drastic. I deleted it with command prompt, Robocopy and 7Zip.

There seems to be a little confusion here on the "Mount" business.

1. 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.
2. 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.
3. 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.

topgundcp said:

There seems to be a little confusion here on the "Mount" business.

1. 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.
2. 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.
3. 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.

The folder showed empty even with hidden files set to be shown. The properties showed 9 folders though.

essenbe said:

The folder showed empty even with hidden files set to be shown. The properties showed 9 folders though.

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 **

@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.