Install of Server 2022 taking hours

Question

We had a corrupted OS and decided to replace the OS disk with new disks (two drives in a raid 1 setup. We installed the OS on the new drive and that seemed to go pretty will, but after the last reboot, it is spinning and does not seem to be going anywhere. There is a 16 GB secondary drive that is attached that it seems to be accessing quite heavily. Is Windows scanning/indexing this drive before completing the last few steps of the installation? We are going on over 1 1/2 hours of watching the little dots chasing themselves in a circle.

Answer 1

Hello,

Based on the information provided, it seems that the Windows installation process may be stuck or encountering an issue. It is possible that Windows is scanning or indexing the secondary drive, which could be causing the delay. However, without further information or diagnostics, it is difficult to determine the exact cause of the issue. It is recommended to wait for some more time to see if the installation progresses. If the spinning dots continue for an extended period without any progress, it may be necessary to restart the installation process.Best Regards,

Hania Lian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Hi Tim, I would suggest boot the machine first in safe mode & verify & repair the corrupted disk.

Booting in Safe Mode

1. Restart your computer.
2. Press F8 before the Windows logo appears. On some systems, you might need to press the F8 key repeatedly until the Advanced Boot Options menu appears.
3. Select Safe Mode from the list of options using the arrow keys and press Enter.
4. Check if C: [OS Disk ] is corrupted. by running the following command - " fsutil dirty"
5. If found dirty then repair the OS disk with "chkdsk C: /f /r".

Please accept the answer if this helps.

Answer 3

Thank you all for the great responses. After letting it run for almost 6 hours, it finally finished and is useable now. Looks like it is re-indexing the secondary drive and when that finally completed it was able to complete the configuration and now we have a very happy server.