[SOLVED] Slow boot, looks for a drive for a long time.

Mar 8, 2019
4
0
20
Hello, I have a Windows 10 on SSD and also 1TB HDD. few months ago I disconnected SSD and connected a drive with windows 8.1 from a laptop (without disconnecting my HDD)
After I copied data from disk I connected my SSD back I found out the Windows 8.1 changed a lot of on my HHD - for example all shortcuts, games were not working because Win 8 changed permissions. I easily found solution to restore everything with a single command and it works fine. But after switching drives Windows 10 on SSD takes forever to load. The LED on tower is not even blinking, it's dark for like 5-10 minutes. I see a spinning circle on a BIOS background (Click BIOS 4, MSI Z87-G43 Gaming) and then it loads in few seconds. It wasnt a big problem until now when I have to reset my PC a lot and have to wait every time.
It works fine when Fastboot is on. But I dont want to "hibernate" my PC. I want to shut it completly everytime.
So far I tried to disable fastboot, restore default bios options, update bios, run in safe mode, select disk manually from Boot Menu (F11 when booting) But nothing helped.
 
Solution
Sorry for a long break, I had no time. I spent all day looking for a fix. It turned out that it was related to Windows 10 update 1803. After updating to newest (1809) problem fixed itself.
Now it boots in 20 seconds.
that doesn't seem right. If you put hdd in another PC and copy things on to it and then move it back, for example, which is essentially the same as what you did, it should have no effect to permissions as its 2 different environments, changes made by win 8 shouldn't be seen by win 10 as the ssd with win 10 wasn't connected at the time. The hdd doesn't record permissions, thats all on whichever drive windows is on.

can you take hdd out and see if slow boot caused by it or bios not finding what its looking for on the ssd, What is top choice in boot order in bios?
 
Boot order:
#1 - UEFI Hard Disk: Windows Boot Menager
#2 - Hard Disk ADATA SU800

So I browsed my history and this is what the problem was:
The Recycle Bin on D:\ is corrupted. Do you want to empty the Recycle Bin for this drive?
and the solution was "rd /s /q D:\$Recycle.bin"
after that if I remember correctly I had to run ICACLS * /T /Q /C /Reset
or with similar arguments to restore HHD to work again with my SSD.
Because I couldn't run games or install anything on HDD.

So I tried to select disk manually from Boot Menu (F11 when booting)
first i picked Windows Boot Menager (P0: ADATA SU800) - but nothing changed - it was loading/looking for windows for a long time
then i selected SATA1: ADATA SU 800 - here I got a message "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"
Then I unplugged HDD and when it booted I saw a "Preparing autmatic repair" (on BIOS screen) and then it showed blue windows screen with message:
Automatic repair couldn't repair your PC
Press "Advanced Options" to try other options to repair your PC or "Shut Down" to turn off your PC
LogFile: C:\Windows\System32\Logfiles\Srt\SrtTrial.txt
So then I pressed Advanced option and opened CMD and run three CMDs:
bootrec /RebuildBcd
I got "Total identified Windows installations: 0"
bootrec /fixMbr
The operation completed succesfully
bootrec /fixboot
Access is denied.
Of course I could reinstall Windows, but it's last thing I want to do. I hate when people say "reinstall" as a solution to every single problem.

Startup Repair diagnosis and repair log
---------------------------
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 359 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot critical file c:\efi\microsoft\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x57
Time taken = 984 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x57
Time taken = 797 ms

---------------------------
---------------------------
 
LogFile: C:\Windows\System32\Logfiles\Srt\SrtTrial.txt

I dislike that file name, often I end up having to tell people the advice you don't want me to jump to. I tend to try to fix windows before saying that...

windows boot manager makes sense if hdd is formatted as GPT. the reaction when you try the ssd by itself also makes sense if its formatted as GPT. WBM should have the partition number and GUID (Global Unique ID) of the boot drive stored

you appear to have done some of the command on here but see if it helps anyway - https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508
 
Sorry for a long break, I had no time. I spent all day looking for a fix. It turned out that it was related to Windows 10 update 1803. After updating to newest (1809) problem fixed itself.
Now it boots in 20 seconds.
 
Solution