Trying to Re Image my computer with problems

This had been a very informative and educational thread.

whs said:

Now if you have a combined (system, active, boot) partition I'm not sure that the process would work.

The Macrium imaging works. I have, however, not tried to restore from that image. So I am not certain whether that would work.

I have the latest Macrium version so I still don't understand why the error on the 100MB system reserved partition.

Of course you can take a Macrium image of the ordinary system reserved partition - do it all the time.

whs said:

Try to image the 100MB partition with

WBADMIN START BACKUP -backupTarget:x: -include:y:

and see whether that may work.

wbadmin is for windows command line execution of Windows imaging not Macrium imaging.
The problem I describe is with Macrium. Windows allows attaching the 100 MB system reserved vhd. Macrium won't image it. See screenshot in my post #43.

By the way wbadmin still wants the same folder and file structure as seen in [WindowsImageBackup]. It's main advantage as I see it is for writing your own imaging scripts.

Yes, wbadmin is the same thing - most will prefer the windows sys img gui.

Macrium message looks like there isn't enough space on 100mb mounted volume to create volume snapshot -if that's the case , then it is a microsoft VSS issue really.

Haven't checked recently, but Macrium used to have alternate drivers to use when VSS fails - not sure if they do now.

Paragon has alternate drivers for just such a case.

Might sound odd - but also check you have enough shadow storage space on your current drive (C or whatever you are booted into )

Worth checking Macrium log - because it might be something else.

SIW2 said:

Macrium message looks like there isn't enough space on 100mb mounted volume to create volume snapshot -if that's the case , then it is a microsoft VSS issue really.

When the windows imaged 100MB system reserved is mounted it does have an occupancy greater than 50MB. Windows imaging requires the 50MB free shadow copy space for it's imaging.
I do not expect this shadow copy space to be of relevance to making a Macrium image.

PS: I'm not sure at this stage where the extra rubbish comes from in the mounted system reserved. It isn't there in the original.

That seems to indicate - unless you can get macrium own pssnap.sys I think it is - can't recall now - to take over - then you can't image the 100mb thing with macrium.

No biggie - just use a different imaging app. - or don't bother imaging the 100mb - you would only mount vhd and do this in extremis - so it's not an issue if you need to run startup repair a couple of times after restoring the main windows partition as Active.

As you have the macrium pe plugin -you could even try the macrium boot corrector and see if that does the job instead of startup repair.

Most people won't have the macrium pe tho.

ps What is the extra stuff in the 100mb?