[SOLVED] i cannot install windows 11 beacuse:

[Palfreezy]

https://imgur.com/27eEWvu

https://imgur.com/qBYQr1Q

View: https://imgur.com/qBYQr1Q

so yeah, i am trying to change disk 0 to gpt but i cant beacuse i cant delete system reserved no matter what i do, diskpart doenst let me it says delete is not allowed on boot, system, pagefile , ect
its literrally my hardrive that windows doesnt boot on i use my disk 1 ssd to boot windows 10, and for the uefi thing and secure boot, i enabled it in bios, wtfs going on, i have asus mother board if anyone know how to help whit these 2 problems pls help

 

[Palfreezy]

https://imgur.com/27eEWvu

View: https://imgur.com/27eEWvu

sry here is the other pic

 

[Palfreezy]

if i try to convert it via advanced command prompt it says cannot find disk OS

 

[USAFRet]

so yeah, i am trying to change disk 0 to gpt but i cant beacuse i cant delete system reserved no matter what i do, diskpart doenst let me it says delete is not allowed on boot, system, pagefile , ect

While your current Windows install may be on Disk 1 (C drive), the boot partition is indeed on Disk 0.
Mess up that partition, and the whole system will become non-bootable.

 

[Palfreezy]

While your current Windows install may be on Disk 1 (C drive), the boot partition is indeed on Disk 0.
Mess up that partition, and the whole system will become non-bootable.

okay so what do i do then?

 

[Endre]

okay so what do i do then?

The way I’d do it:
I’d save all of the personal files on another drive.
Then, I’d delete all partitions, then re-create them, format, and install the OS.

But I don’t advice you to install Win11 yet!
The dev builds are buggy!
Wait for the official releases.

 

[HellfyrMN]

The way I’d do it:
I’d save all of the personal files on another drive.
Then, I’d delete all partitions, then re-create them, format, and install the OS.

But I don’t advice you to install Win11 yet!
The dev builds are buggy!
Wait for the official releases.

Yes, yes they are.

I created a fresh Gen 2 VM on my 2019 HyperV box, installed the latest version of Win10 and then did the Win11 DEV insider update.
The VM specs: 8G dedicated RAM, 4 processor cores, 100G Disk.

Installed fine (but took quite a bit of time).
Adopted all my Windows 10 settings properly for locale/network/user/general config (it did NOT carry over the Timezone for me, had to set that manually after update (CST) ).

I find it almost UNUSABLE due to severe CPU usage.
Any time you open any window the CPUs are PEGGED. And not a small amount of time, typically between 10 and 20 seconds before you see the CPU taper off again.
With these system specs it should be a blip and things are open and running.
Of the 8G RAM it is only using 4G, so has nothing todo with memory.
This is entirely some sort of issue with the Window Management System from what I can tell.

On a side note, also downloaded the Preview of Visual Studio 2022 (am a developer by trade) and it too doesn't really work at all.
It comes with the Beta of .Net 6, but if you try and write a program with it... it requests .Net 5... uh.... ok ???
Confirmed from command line that .Net 6 preview is installed and running just fine.
But the Visual Studio refuses to utilize it even though told to do so when creating a project.

Not sure what M$ is thinking here, I'd be embarrassed to release something for community preview when it can't perform basic operations properly.

Now, could it all be a result of it running in a VM ? I don't think so, not entirely. But I don't have a standalone box I am willing to sacrifice to find out.

Just my $.02 and observations... your mileage may vary.

 

[DSzymborski]

I'm not sure why any of this is surprising. It's still in the Dev channel and MS explicitly warns of "rough edges and some instability." I mean you're literally working with a beta framework on what is essentially an alpha OS (and while I agree running it virtually wouldn't be the entire problem, it's certainly an additional handicap).

 

[Isaac Zackary]

okay so what do i do then?

As others have mentioned, wait until the official Windows 11 comes out for the general public.

Think of this.

1. Windows 10 will still be up and running for the next 4 years. So you have time.
2. As others have mentioned the Windows 11 available right now is not the official build and is buggy. Just waiting a few more months won't hurt.
3. You'll want to make sure you're computer is compatible with Windows 11 before wiping disks and such. But we won't know everything until the official build is out.

So you basically have 4 years to make sure your computer is otherwise compatible, and if it is, then you got the rest of those 4 years to figure out how to install Windows 11. By then there'll probably be a hundred YouTube videos telling you how to do it. One way would be to find someone with a computer that you could connect your boot drive to, copy all files to a backup drive, then wipe the whole thing and then stick it in and use a USB with Windows 11 installation on it and repartition and go from there.