Windows 10: Windows 10 notifications and event viewer indicate damage in system disk/partition/NTFS...

Hello.First of all, I contacted Microsoft tech support and they kept insisting that I needed to try a clean install. I don't need tech support to tell me this, since, besides being unprofessional from their part, I already knew of that being a possible solution before contacting them. But I don't want to go through that hassle unless I absolutely have to. They didn't ask me for any specific information or give me any alternative solution.So here I am, with two computers running Windows 10 21H2 updated, a desktop that I built myself, and that's the one currently with the problems, and a laptop

:)

 

Move Win7 64 image from a partition NTFS to a new drive

EDIT: After reading your first post again, is there any reason that you would now need GPT? Are you just trying to move the windows install to a new disk or is there a new motherboard involved?

If you are already booting to an NTFS partition, then it makes me wonder if after copying to the new drive, the partition isn't getting marked as Active.

Following the same steps I posted above for startup repair, you can get to a command prompt and use diskpart to see if this is the case.

Code: In the command prompt: diskpart list disk select disk 0 (disk number may be different if you have other disks connected.) list partition select partition 0 (partition number number may vary, but you want to see the boot partition which is the same as your windows partition according to the screenshot on the OP) detail partition (This should have Active: Yes or No. If it says no, since we have the partition selected, you can just use the following command in diskpart) active[/quote]

 

Installing Windows Vista/7 on a GUID Partition Table

I've never tried multiple partitions so this is a shot in the dark...

At step #10, I would try setting the size parameter (it is in mebibytes) to how large you want the partition windows is installed on to be, then go ahead and install windows. This will leave the rest of the drive raw instead of consuming it into the OS partition (C drive). Once you successfully boot into Windows, you should be able to use Computer Management -> Disk Management to create partitions in the raw space.


If you really wanted to do it with diskpart before Windows is installed, you basically repeat the following lines making sure to specify a size if you don't want it to consume all remaining space:

• create partition primary size=size in mebibytes here
• format quick fs=ntfs label="appropriate name here"
• assign letter=C thru Z here

Obviously, you can use quick formatting or leave it out for full format. Leave off the size parameter when you reach the final partition that should consume all the remaining space. Also remember that the order you do this in goes from the outside of the disk (where it is fastest) to the inside of the disk (where it is slowest). Because of this, it is recommended to put EFI (e.g. size=300), then MSR (e.g. size=300), then Windows (e.g. size=30000), then Applications (e.g. size=70000), then Storage (e.g. no size parameter).

If I'm right, the above example would look like this:

• diskpart
• list disk
• select disk <id>
• online disk
• attributes disk clear readonly
• clean
• convert gpt
  
• create partition efi size=300
  
• create partition msr size=300
  
• create partition primary size=30000
• format fs=ntfs label="Windows"
• assign letter=C
  
• create partition primary size=70000
• format fs=ntfs label="Applications"
• assign letter=D
  
• create partition primary
• format fs=ntfs label="Storage"
• assign letter=E
• exit

 

what is this problem?

Event viewer will list it yes. Random guess: NTFS problem, could be hardware (disk, network) related.