Forum Discussion

Blackddreams's avatar
Blackddreams
Copper Contributor
Sep 04, 2023

Fresh Windows 10 install on nvme SSD

Hello,

 

 I would like to ask for some advice following the problem I am encountering.

 

 After multiple searches I was unable to find a case exactly like mine.

 

 I have just put together a new computer on which I installed Windows 10 via a bootable USB key (provided by Windows a few years ago) on a Samsung 980 Pro nvme SSD.

 

 The installation went smoothly and I accessed the desktop normally but when the PC was shut down and restarted, it was impossible to boot from the Windows partition.

 

 I remain on a black screen with the logo of the brand of the motherboard (Asrock B760 Pro RS). The red BOOT LED on the motherboard as well as the VGA LED remains lit.

 

 The hard drive is well recognized and has first priority in the bios.

 

 When I restart a Windows installation I can clearly see the partitions created by the first installation.

 

 I've tried restarting, formatting and reinstalling multiple times and I always get to the same point.

 

 I would have to try again but it seems to me that if the PC is restarted instead of shut down, the startup works correctly.

 

 What bothers me is that I can access Windows normally after the first installation following a format, so I would tend to rule out a hardware problem.

 

 Has anyone encountered a similar case or is at the beginning of a trail?

 

 I hope I have provided enough information.

  • When you were in Windows, did you make sure all the updates were made?

    Also, have you tried to do a in-place upgrade with the Media Creation Tool on aka.ms/winup?

    So, you are saying if you press restart it will work all fine?

    I am not sure but I think if you force shut down and turn it on, it will eventurally do the auto repair thing and able to get to cmd via the advanced troubleshooting.

    Could you get a DMP files?

    Thanks,
    Shawn
    • Blackddreams's avatar
      Blackddreams
      Copper Contributor

      Hello and thanks for your answer.

      After many tests, the issue has been solved by desactivating fast booting on the Windows side in the parameter.

      I had checked on the Bios side but i didn't know this parameter exist in Windows too. 

      Hoping this could help someone else. 

       

      • Deleted's avatar
        Deleted
        Oh!! that's nice!

        have a great day!

        Shawn

Resources