Solved Windows 10 version 1607 resize issue

[AndrewG78]

I have recently upgraded my FOG from 1.4.4 to 1.5.4 to have Windows 10 support.
I can do snapshot of W10, but when I try to deploy image to the same machine I got this error on a blue screen:
Recovery
Your PC/Device needs to be repaired
A required device isn’t connected or can’t be accessed.
Error code: 0xc00000225
You’ll need to user recovery tools. If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.

Looks like it is related to partition resize function.
Any solution for this?

[george1421]

@andrewg78 I’m still thinking its bit locker that is causing your issue. When you use single disk not resizable then clone the image, you are not changing the geometry of the disk. Please read through this post and see if running the commands to disable bitlocker makes single disk resizable work better. https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43

Looking over the entire thread just for your info.

[AndrewG78]

I captured 1803 as a single disk NOT resizable and succesfully deployed it to another machine.
Looks like problem with extra partitions.
I will try to delete them through gparted on Monday and see the result.
cheers

[AndrewG78]

@george1421
Bitlocker is OFF
But I think problem might be with partitions.
I think FOG when was imaging, did not mount all 5 partitions.
Is this proper partition structure in Windows 10?

[george1421]

@andrewg78 If bitlocker is enabled (it is even if you have not enabled it) then single disk resizable will cause it pains since the act of disk resizing changes the geometry of the hard disk breaking the encryption.

[AndrewG78]

I captured without any preparation.
No driver handling. No sysprep.
Working on single machine at the moment.
I have MBR, captured as single disk resizable.
When I use Clonezilla, I do not have any issues.
I just upgraded to 1803 and I will try to capture one more time in single disk NOT resizable mode this time.

[george1421]

@x23piracy I’m still not going to rule out FOG doing something unexpected, but at least with 1607, imaging should work well. 1803 is another matter.

[x23piracy]

@george1421 correct i missed that bitlocker crap the error code 225 means inaccessible boot device. Bitlocker, missing active partition or at least a complete partition is missing.

@AndrewG78 MBR or GPT?

Regards X23

[george1421]

@x23piracy said in Windows 10 version 1607 resize issue:

lets say he just captures without any preparation, at least it should deploy to same machine without any issue.

Assuming bitlocker hasn’t been enabled and he is capturing and deploying to the same exact hardware it should work. If bitlocker is in the mix then, no way possible.

[x23piracy]

@george1421 he‘s trying to deploy to the same machine, lets say he just captures without any preparation, at least it should deploy to same machine without any issue.

@AndrewG78 how are the image settings for that host? Do you capture only single partition or all partitions?

Regards X23

[george1421]

I don’t think the bluescreen is related to FOG.

How are you preparing the golden image for image capture? Are you syspreping the golden (source) image?
Are you capturing and deploying to the same hardware model?
How are you handling drivers if your hardware is different?