A rather odd set of circumstances.

After a main board crash I cloned Windows 11 from a laptop with a small, 117GB, SSD to a 1TB hard drive.

I installed this copy of windows on my desktop, with a new mainboard and Ryzen 5-5500 cpu.

The "C:" drive had a formatted size of 256GB and the usual windows partitions as well as 700GB sitting idle.

I use Affinity Photo to do focus stacking and initially all went according to plan. The new machine was somewhat faster than the original.

I reasoned that I should extend C: to use all the free space and accomplished this with "NIUBI' partition editor.

This is where things went pear shaped.

Most of my software seemed to run normally but the image alignment section of Affinity Photo was taking 15 minutes, and more, to align the images where it previously took between 45 seconds to a minute depending on the number of images.

I have since reduced the size of C: to 480GB, the smallest I could manage, and the performance of the image alignment is back to normal.

Why is it so?

Is this a Windows problem or Affinity Photo?

I did get  a "Corrupted file repaired" indication running "SFC"

I also ran all three iterations of DISM with no error messages.

Will go to the Drive size is too small.    You cloned corrupted data.   The Motherboard does not have the correct information as the other board was corrupted and need drivers from the Support Page.

Get your data off and then do a clean install of Win 11 on a 1TB drive.   Your attempt to so what you are doing is completely wrong.   Images that are corrupted and then transferred remain corrupted with the wrong information for a new Motherboard with out the new Chipset installed and BIOS Updates for a new M/B.

All wrong, wrong as is resizing drives. As well is the M/B setup properly for UEFI Support : https://www.windowscentral.com/how-create-windows-10-usb-bootable-media-uefi-support /11

As well when you do a clean install delete previous UEFI Partition and Recovery Partition. 

So grab your data and your Product Keys :  https://www.belarc.com/products/belarc-advisor        If no product keys oh well.!

Edited by Chris Cosgrove, 26 December 2025 - 05:05 PM.
Unwanted comment deleted

Assuming your "1TB hard drive" is mechanical, there could be bad/weak sectors in the space you expanded your C partition into, and that could cause applications to experience extreme delays or even data corruption when trying to operate on those sectors.  What I would try, after a hard disk backup, is expanding the partition again and then running the "chkdsk c: /r" command to see if it finds any bad sectors on your disk.  If it does, that drive should probably be retired.  With the bad sectors found and marked, your application may no longer experience those extreme delays with the expanded partition, but more bad spots could develop in the future, so best to retire the drive.

Increases in partition sizes on mechanical hard disk drives can usually lead to a drop in performance since NTFS likes to spread files around to prevent fragmentation leading to longer seek times, but the drop usually isn't so extreme.

Will go to the Drive size is too small.    You cloned corrupted data.   The Motherboard does not have the correct information as the other board was corrupted and need drivers from the Support Page.

 

Get your data off and then do a clean install of Win 11 on a 1TB drive.   Your attempt to so what you are doing is completely wrong.   Images that are corrupted and then transferred remain corrupted with the wrong information for a new Motherboard with out the new Chipset installed and BIOS Updates for a new M/B.

 

All wrong, wrong as is resizing drives. As well is the M/B setup properly for UEFI Support : https://www.windowscentral.com/how-create-windows-10-usb-bootable-media-uefi-support /11

 

As well when you do a clean install delete previous UEFI Partition and Recovery Partition. 

 

So grab your data and your Product Keys :  https://www.belarc.com/products/belarc-advisor        If no product keys oh well.!

 

Is this confusing : aldfort

Thanks PKShadow.

Is it confusing? Yes and no. I understand that what I have done is not the best way to go about things but it was a stop gap measure and seemed to work until I messed with the drive size.

As for corruption, There was only a single file corrupted and that was, apparently, repaired..

The bios had been reset for the new mb but The drivers certainly would have been wrong.

I have done an "in place" update of w11 and that should have fixed the drivers. 

I will do a check on them anyway.

Thanks for the response and, yes a clean install may well be necessary.

John.

P.s. Apologies for posting in the wrong spot.

Assuming your "1TB hard drive" is mechanical, there could be bad/weak sectors in the space you expanded your C partition into, and that could cause applications to experience extreme delays or even data corruption when trying to operate on those sectors.  What I would try, after a hard disk backup, is expanding the partition again and then running the "chkdsk c: /r" command to see if it finds any bad sectors on your disk.  If it does, that drive should probably be retired.  With the bad sectors found and marked, your application may no longer experience those extreme delays with the expanded partition, but more bad spots could develop in the future, so best to retire the drive.

 

Increases in partition sizes on mechanical hard disk drives can usually lead to a drop in performance since NTFS likes to spread files around to prevent fragmentation leading to longer seek times, but the drop usually isn't so extreme.

Thanks BeigeBochs

The drive is mechanical and it was fully checked a couple of times during this process and has been running fine before.

I think the advice PKS has given is pretty sound.

I'd have done it differently and done a clean install of W11 on a new drive with the new MB but I'm fairly certain I'd have had to buy a new licence if I'd done this and possibly to have had to set up a MS account as well. Then there is the pain of reinstalling all the software so I sort of understand what was attempted. 

Edited by Chris Cosgrove, 26 December 2025 - 05:07 PM.
Unneeded comment deleted

Please do not use the Quote All Box, Just type. It is never needed and if need to Quote please use the Quote Tool in the Tool Bar.

@Segref23 Not at all surprised.  And no, doing what you did does not install the Motherboard Support Drivers or the current Chipset or current "AGESA" info.

Please supply the Motherboard Make and Model.  Thanks.

EDIT : No a clean install is mandatory with what you have done.    Trying to trouble shoot this you have wasted hours that you could have got your info off and started on a clean install.

With the proper motherboard drivers installed after you have installed Windows 11

M/B setup properly for UEFI Support : https://www.windowscentral.com/how-create-windows-10-usb-bootable-media-uefi-support /11

Edited by Chris Cosgrove, 26 December 2025 - 05:09 PM.
Unneeded comment deleted

Your concept of transferring the OS from one drive to another is good.  One big problem is that your new unit is running with Windows generic drivers, not the ones specifically for that board. Try to find the mainboard drivers for that unit online and install them, as Pk already stated in post #7 above. 

From your post, as far as I can see, your main problem is with Affinity Photo. 

You said: 

 

After a main board crash I cloned Windows 11 from a laptop

How do you know it was the mainboard that caused the crash?  Did you trace down exactly what caused that crash? If anything corrupted in your original Windows install, you copied that corruption and transferred it to the new unit. Carefully check that out. 

A lot of things to answer here, so I'll do it this way.

1) The problem was definitely the resizing of the C: drive, not Affinity. Bringing C: back down to 480 MB has solved my main problem. I did not reload Affinity.

2) Given the machine is operating as expected, one would assume that all drivers, uefi partitions etc are normal.

3) A driver check has indicated all drivers are up to date.

4) I have allocated the spare space as D: and it is now my downloads folder.

5) The MSI board has automatic driver support enabled in the bios.

6) I thank all for their input and consider this item "Solved".

7) As a newbie to this forum, I apologise for any newbie mistakes and will try to do better next time,.

How do you know it was the mainboard that caused the crash?

It didn't cause the crash, it crashed.

I was replacing the cpu with better one and something went wrong. I put the old cpu back in and the MB was dead.

Did you install your UNKNOWN Motherboard Support Drivers or Branded System Drivers (LENOVO/HP/DELL)  ?

You were asked for the make and model information.

It is also something that needs to be posted all the time.

Regarding the driver check, assuming you did this in windows then it might not be true. Visit the MB makers site to download the latest drivers. Windows generic drives are OK in a fairly vanilla installation, not always so good if you use graphics software etc. 

Sorry, I've been away.

CPU is 5-5500 ryzen on B450M Pro MB