Jump to content

I am currently running windows 10 on my computer and am trying to update to windows 11.

Yesterday I completely built a new computer, but I used my M.2 drive from the previous build that I had. This had caused issues booting that I was able to solve but are potentially relevant to my current issues.

As of today when I want to update windows from 10 to 11 I got the error that "windows cant be installed because this pc has an unsupported disk layout for uefi". To solve this I changed the format of my C drive from MDR to GPT as I had read online. I ran the update again and it said it had failed at the end. When I went to restart my computer I was prompted with a blue screen that asked for me to choose my operating system either windows 10 or 11 when I pick windows 10 I am brought to my normal desktop, choosing windows 11 just black screen or loads the gigabyte logo indefinitely. As I opened to computer it then said windows 11 setup had failed because "DOWNLEVEL phase with an error during PREPARE_FIRST_BOOT operation". I lastly tried to use the installer one more time which gave me the newest error that an instance/update was currently running. If the recommendation is a clean install of windows 11 that is fine as I have another SSD that I can save files on it is just not preferred as I'd rather just maintain my current data.

I attached a picture, it is like that but with windows 10 on top and windows 11 on the bottom.

Im hoping to resolve this issue, upgrade to windows 11, and hopefully fix any issues related to my drives and I have been messing with the partitions and diskpart a lot recently.

 

Thanks!!!

 

7800x3D

Gigabyte A620i AX  Version F31 BIOS

2080 Super FE

850 Watt CoolerMaster SFX

Samsung 970 EVO Plus 1TB

Windows 10 Pro x64

 

picture.jpg

Link to post
Share on other sites

I ran into a similar issue when moving from Windows 7 to 10. (I know you just used the screenshot as an example). At this point, I recommend making sure all the important stuff is backed up and just doing a clean install. I remember getting past this error doing a sfc /scannow but it was still borked.

 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×