Reboot takes more than 4 minutes!

Hello Olivier,

Thank you for the update.

I appreciate your efforts and concern.

As boot time is lesser and Windows is taking longer to shutdown before restart, please refer suggestions from

apster replied on February 24, 2010 and check if it helps.

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/windows-7-is-very-slow-to-shutdown/fb35a679-c9b8-4a97-95c4-39c60e218130

Note: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

https://support.microsoft.com/en-us/kb/322756

Please keep us posted.

Thank you

Hello,

Don't you have better advices than updating BIOS, drivers and firmwares? This is one of the first things I did and you know what? It was a complete disaster... The BIOS update broke my RAID array and I lost a lot of data as a result of that... So I have dropped RAID, it isn't stable enough with Windows...

Still my problem remains. If a backup includes a system image, then Windows takes 4 minutes to reboot...

Regards,

Olivier

Hello Olivier,

Thank you for the reply.

I appreciate your patience.

I would suggest you to update BIOS, chipset and firmware drivers from the computer manufacturer's website and check.

Refer:

https://support.microsoft.com/en-us/help/15048/windows-7-update-driver-hardware-not-working-properly

Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

Thank you

I have spent hours debugging the issue. I turned on Microsoft startup performance profited and came to the conclusion that the issue was caused by a startup routine checking partition integrity. Turning it off it definitely not something I'll do. This isn't a solution nor a viable workaround. Now Microsoft has to fix this issue...

Hello,

I already ran the sfc scanner. This is one of the first things I had attempted... Obviously, it didn't help...

To be honest, I don't think it is my job to debug Microsoft bugs. It won't work if you send me every 4 months one command to run. I expect your support to be a bit more focused and efficient. 4 months to get reply is just crazy...