cloned OS drive "System Reserved" partition Not 100% afterwards.

Anonymous
2024-06-24T15:29:41+00:00

Hi,

I cloned my OS drive twice to move to a newer hardware. But the last time, it seems the "System Reserved" partition of the drive had some issues.  1st: it is not showing "System Reserved" on that partition.  2nd: the following attributes "system, Active, MBR" are not on it and shows only "Primary".  My PC still boots up, but the whole purpose of this exercise was to get compatible to install Windows 11 and upgrade the OS drive with new and faster hardware.  My questions are:

Is there anything I can do to fix it other than re-installing the OS? 

Is this going to cause any issue with upgrade to Windows 11? 

See below properties of this partition.  

Device SCSI\Disk&Ven_NVMe&Prod_CT2000T705SSD3\5&2384875e&0&000000 was not migrated due to partial or ambiguous match.

Last Device Instance Id: SCSI\Disk&Ven_Samsung&Prod_SSD_870_QVO_1TB\4&fa535c2&0&000000

Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}

Location Path:

Migration Rank: 0xF000FF001001F020

Present: false

Status: 0xC00007196/15/2024 10:51:31 AM Device not migrated

6/15/2024 10:51:31 AM Device configured (disk.inf)

Device SCSI\Disk&Ven_NVMe&Prod_CT2000T705SSD3\5&2384875e&0&000000 was configured.

Driver Name: disk.inf

Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}

Driver Date: 06/21/2006

Driver Version: 10.0.19041.4355

Driver Provider: Microsoft

Driver Section: disk_install.NT

Driver Rank: 0xFF0007

Matching Device Id: GenDisk

Outranked Drivers:

Device Updated: false

Parent Device: PCI\VEN_C0A9&DEV_542B&SUBSYS_2B00C0A9&REV_00\4&2ec11bf&0&000A

6/15/2024 10:51:31 AM Device started (disk)

Device SCSI\Disk&Ven_NVMe&Prod_CT2000T705SSD3\5&2384875e&0&000000 was started.

Driver Name: disk.inf

Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}

Service: disk

Lower Filters:

Upper Filters:

Thank you.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Ramesh 181.8K Reputation points Volunteer Moderator
2024-07-11T15:15:35+00:00

You're welcome, Givi. Glad to have helped. 👍

You may close this thread by marking helpful posts as answers if there are no further questions. How to mark Your question as "Answered".

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

56 additional answers

Sort by: Oldest
  1. Ramesh 181.8K Reputation points Volunteer Moderator
    2024-07-06T16:44:42+00:00

    Givi,

    WinRE is now located in the OS partition, even though a dedicated recovery partition exists. This happened because the recovery partition does not have sufficient free disk space. The partition size needs to be 750 MB or more.

    Anyway, we can fix that anytime later. Let me know how the Windows 11 upgrade goes.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-07-06T16:45:50+00:00

    Thank you.

    Givi

    Was this answer helpful?

    0 comments No comments
  3. Ramesh 181.8K Reputation points Volunteer Moderator
    2024-07-06T16:49:19+00:00

    Thanks.

    We can do the following later (after the upgrade).

    1. Move EFI to Partition 1.
    2. Delete the existing EFI partition
    3. Shrink C drive by 80 MB
    4. Create a Recovery partition in the unallocated space and configure WinRE.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-07-06T18:37:02+00:00

    Ramesh,

    For some reason I am getting Error when I select "How to run an in-place upgrade in Windows 11". I am in US, Florida. Let me know please.

    Go to Windows 11 website: https://www.microsoft.com/en-us/software-download/windows11

    Under Download Windows 11 Disk Image (ISO) select Windows 11 (multi-edition ISO)

    Image

    See below Error message:

    Thank you.

    Givi

    Was this answer helpful?

    0 comments No comments