Updated Windows 10 Machine Not Capturing to FOG Server

[ftgjason]

Running Version 1.4.2
SVN Revision: 6072

I have 2 different types of machines that we are using FOG for this summer. Dell Latitude e6400 and e6420. Both machines are up-to-date with Windows 10. The e6400 captures and deploys with no problem. The e6420, after updating, does not capture. The error…
Any help or suggestions appreciated. I have approx 200 of these model of machines that I need to have imaged.

[Tom Elliott]

You need to shutdown the machine outside of “Fast boot” (Hold Shift when choosing shutdown)

[ftgjason]

@Tom-Elliott
Ok…thanks for that…I got passed that issue…now it is giving me this error and reboots.

[Tom Elliott]

@ftgjason There’s a problem with your disk. it’s finding corrupt data.

[x23piracy]

i know that problem and i solve it with:

shutdown -s -t 0 -f

please try this.
This can also happen with some sucky notebooks where you have only milliseconds to press the network boot button and accidentally press strg+alt+del in the wrong moment because the damn thing is booting the os again while you wanna image.

Also Windows 10 has an option where its not shutting down the way we may suggest, some kind of powersaving state.

https://answers.microsoft.com/en-us/windows/forum/windows_10-files/win-10-leaving-dirty-ntfs-partitions/8b9be760-7003-48de-97b2-06bdf497085c

This is for the unclean disk state the inode error seems to be a bad sector on your hdd or something like that. Try to run chkdsk or similar tools to check filesystem integrity and bad sectors.

[ftgjason]

Ok…well not sure why or how I had a couple of machines showing that same error…but I started rebuilding a different machine from the OS up and it captured with no problems. Thanks for your help.