Question Warnings when cloning up SSD to new SSD on Macrium Reflect v8.1.8325

[errrmum]

Hi,
I tried to clone a smaller ssd to a larger one using macrium reflect and it says it's successful but in the event viewer for the clone I get warnings, how can I resolve them? I've tried online solutions such as turning off anti virus, enabling volume shadow copy in services, and icacls C:\ /grant system:f in cmd but to no luck.

I got 9 warnings like:
Type: Warning
Event: 12348
Source: VSS

Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{7da7feee-d446-447b-a7f2-efba5c6df2fe}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly. Check security on the volume, and try the operation again.

Operation:
Removing auto-release shadow copies
Loading provider

Context:
Execution Context: System Provider

Type: Warning
Event: 12348
Source: VSS

Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{4df996f0-b25c-4a33-bbad-7546d9137581}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly. Check security on the volume, and try the operation again.

Operation:
Automatically choosing a diff-area volume
Processing EndPrepareSnapshots

Context:
Execution Context: System Provider

also is there a way to tell what the problem is based on whats inside the {}? thanks

 

[Lafong]

"it says it's successful"...........

Does the cloned drive do what you want it to do? Boot the drive or whatever you intended?

Event Viewer can and will occupy 100 percent of your waking hours from this day forward if you let it.

 

[BFG-9000]

You can avoid this by using a bootable cloning tool instead, like Macrium's Rescue Media. That way, Windows is not even running so it cannot change any files during the clone.

Making a clone from within running Windows requires asking Windows to make a Shadow Copy snapshot of any locked files--copies from this snapshot are what's cloned instead of the ones in use which can change at any time. If the Volume Shadow Copy Service is denied access to any files, then no snapshot of them can be taken and they will simply be missing from the clone.

 

[errrrnum]

You can avoid this by using a bootable cloning tool instead, like Macrium's Rescue Media. That way, Windows is not even running so it cannot change any files during the clone.

Making a clone from within running Windows requires asking Windows to make a Shadow Copy snapshot of any locked files--copies from this snapshot are what's cloned instead of the ones in use which can change at any time. If the Volume Shadow Copy Service is denied access to any files, then no snapshot of them can be taken and they will simply be missing from the clone.

So I tried this and followed the instructions here on another post on the steps to cloning the drive, but when I tried to boot with only the new SSD plugged in, my PC kept restarting until the automatic repair thingy showed up. I tried to do startup repair but that failed and said "Startup Repair couldn't repair your PC Press "Advanced options" to try other options to repair your PC or "shut down" to turn off your PC. Log file: C:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt" but when I chose the shutdown option, and started my PC normally using the power button, it started fine. I checked SrtTrail.txt and:
Test Performed:
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 25594 ms

Test Performed:
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Fallback diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.

Repair action:
Result: Failed. Error code = 0x32
Time taken = 234 ms

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x57
Time taken = 1140 ms

do you think that everything is okay with this clone or should I try recloning it?