Windows 10 partitioning problem

[Psycholiquid]

OK so I have done some investigating and here is the issue.

When you mount the Windows 10 drive into anther machine in order to use DISM to inject drivers it does something to the partition and marks it as dirty. this causes FOG to not capture the image due to this. However the drive is fine even though FOG (Partclone) thinks it isn’t. I have run chkdsk /f to clean the partition and rebooted twice but the real problem lies in the way it shuts down then your preform a shutdown in windows 10 it actually doesn’t shutdown it hibernates. I am attempting to fix this but the dirty partition problem remains, is there a way we can get around this.

[sudburr]

I haven’t starting building Windows 10 images yet, but have you tried “shutdown -s -t 0” from a CMD prompt?

[Psycholiquid]

@sudburr Yes, it isn’t helping, plus I want to use the oobe command to call my unattend.xml file which can be reboot or shutdown. I get the shutdown isn’t a real shutdown in windows 10 but a hibernate, so I choose reboot but that is the same result.

I know if I do it in MDT it seems to help, but I am not real sure how to inject drivers that way, Reading up on it now. Unless someone knows exactly how it works.

[Quazz]

@Psycholiquid Turn off Fast Boot in power options to disable the hibernate shutoff.

[Psycholiquid]

@Quazz Tried that, it isn’t an option in Enterprise. I don’t know why but it isn’t.

[sudburr]

Are you building the original image on a physical machine or in a VM?

[Psycholiquid]

@sudburr VM

[Tom Elliott]

What version?

[Psycholiquid]

@Tom-Elliott Of?

[Tom Elliott]

@Psycholiquid Fog (which you already stated was 7298).

[Psycholiquid]

I was able to get past this. I guess it is a Windows 10 thing but you have to run the chkdsk scan from within Windows and then let it reboot. It will tell you it is dirty as soon as you do it and will correctly. FOG working great again (Not that it wasn’t stupid Windows)

[sudburr]

It’s not a Windows 10 thing. A chkdsk + reboot prior to uploading is something I’ve been advocating hereabouts since Win95. It’s just good file system health management. It’s an easy and painless way to eliminate one avenue of problems for capture / deployment whether you’re mastering on virtual or physical.

On Windows 7- you’d property the partition and schedule a chkdsk at next reboot.

For Windows 8+ you CMD: chkdsk /offlinescanandfix

PartClone and Windows are both a bit twitchy about that. Especially when WinPXE booting to access the partition/drive. Adding files from a WinPXE can seriously fubar and ultimately poison the file system and OS if you’re not careful.

If you never encountered this before, you were lucky.

[Wayne Workman]

There’s also this:
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

[sudburr]

Did you ever try [SHIFT] + [SHUTDOWN] ?