Windows 10 partitioning problem
-
@Quazz Tried that, it isn’t an option in Enterprise. I don’t know why but it isn’t.
-
Are you building the original image on a physical machine or in a VM?
-
@sudburr VM
-
What version?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@Tom-Elliott Of?
-
@Psycholiquid Fog (which you already stated was 7298).
-
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)
-
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
/offlinescanandfixPartClone 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.
-
There’s also this:
https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit -
Did you ever try [SHIFT] + [SHUTDOWN] ?
