Hello,

I need to transfer a content of entire system without altering a source software and data from bootable MBR HDD to new HDD which has been initialized as GPT. System will be set from BIOS to UEFI mode. Then, new GPT HDD will be used instead the old one on the same system.

Simple cloning through ghost will substitute GPT with MBR.

I don't want to mess with standard deployment and installation procedures using  sysprep, diskpart, imagex, WinPE (WinRE), bootable flash, etc.

I am able to boot another win8.1 OS on external HDD and see both source and target HDDs.

• May I just create a wim image of entire source MBR HDD and then "pour" it into a target GPT HDD, so it will be ready for boot and use?
• If yes, what are expected correct steps, checks, and right tools to do so?

From what I know about wim images I can guess that this file-based format might be a right native solution that will adapt a content to the different disk format.

I never used wim format to do such transfer before.

If this question has been raised before, consider giving a links to corresponding topics in right order as an answer.

Thanks.

• Edited by Vladimir Amir Tuesday, June 23, 2015 11:10 PM clarification

Hi Vladimir,

I'll try to answer.

1. wim format

wim format is similar to .zip, .rar, or .bkf "formats", ie it is "file format", not a file system. You create "wim archive" by using programs:
 ImageX.exe - if you are using older Windows AIK
 Dism.exe - if you are using newer Windows ADK

2. May I just create a wim image of entire source MBR HDD and then "pour" it into a target GPT HDD...
See 1. above. wim file is archive of files captured from a certain volume. It can be "applied" to a target volume. So you cannot capture a HDD, but a volume. Also, you cannot apply it to a target raw disk, but to a formatted volume. You can capture files from the volume which has not been "sysprepped". Also, you can apply "unsysprepped" files. However, this is not considered deployment. Microsoft also recommends using "Windows Image Backup", rather then wim for the scenario that you describe.

3. So, the steps ar basically:
a) capture contents of a volume to a wim file.
b) store a wim file (on the network share, another volume, another local disk, external disk etc).
c) Bring in a new disk or a new computer.
d) Wipe the contents of the new disk (may be on a new computer). You can do this with diskpart.exe.
e) Create volume(s) on the target disk. You can do this with diskpart.exe.
f) Apply contents of the wim file to a target volume. You can do this with Imagex.exe or DISM.exe
g) Fix boot environment. You can do this with bcdboot.exe

• Edited by Les52 18 hours 23 minutes ago
• Marked as answer by Vladimir Amir 11 hours 8 minutes ago

Hi Vladimir,

I'll try to answer.

1. wim format

wim format is similar to .zip, .rar, or .bkf "formats", ie it is "file format", not a file system. You create "wim archive" by using programs:
 ImageX.exe - if you are using older Windows AIK
 Dism.exe - if you are using newer Windows ADK

2. May I just create a wim image of entire source MBR HDD and then "pour" it into a target GPT HDD...
See 1. above. wim file is archive of files captured from a certain volume. It can be "applied" to a target volume. So you cannot capture a HDD, but a volume. Also, you cannot apply it to a target raw disk, but to a formatted volume. You can capture files from the volume which has not been "sysprepped". Also, you can apply "unsysprepped" files. However, this is not considered deployment. Microsoft also recommends using "Windows Image Backup", rather then wim for the scenario that you describe.

3. So, the steps ar basically:
a) capture contents of a volume to a wim file.
b) store a wim file (on the network share, another volume, another local disk, external disk etc).
c) Bring in a new disk or a new computer.
d) Wipe the contents of the new disk (may be on a new computer). You can do this with diskpart.exe.
e) Create volume(s) on the target disk. You can do this with diskpart.exe.
f) Apply contents of the wim file to a target volume. You can do this with Imagex.exe or DISM.exe
g) Fix boot environment. You can do this with bcdboot.exe

• Edited by Les52 Wednesday, June 24, 2015 12:55 PM
• Marked as answer by Vladimir Amir Wednesday, June 24, 2015 8:10 PM

Thanks for a quick reply.

I think I got the point and will definitely consider whether "Windows Image Backup" or "Fix boot environment" options.

I've also found another new interesting feature "Windows Image File Boot (WIMBoot)" (https://technet.microsoft.com/en-us/library/dn594399.aspx).

I'll try to understand it deeper and see if it can simplify my task. From now it looks like convenient "factory" solution to address GPT disks; especially due to shiny intriguing phrases like "with fewer compression/decompression steps" or "for UEFI-based PCs running in UEFI mode" for instance. Maybe I'll give it a try (maybe just to give it a try and practice).