Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  V

  @Tom-Elliott When searching for a solution I recall seeing a related post on GitHub but that was not me. Today I created a new VM that was 70GB with 2GB EFI partition and after sysprep and it yielded the similar resize error during capture.

  I then tried Windows 11 25H2 June 2026 Build 26200.8655 with 60GB VM and it generated the resize error. 25H2 with 60GB VM and 2GB EFI also generated the resize error after sysprep during capture.

  The AI suggested defrag C : /X

  I ran the defrag before sysprep and capture was succesful.

  The pre optimization total fragmentation was 22% and post defragmentation it was also 22%

  To my understanding the /X flag consolidates free space. How was this the solution to my issue?

  Per the FOG Project wiki I found that defrag is recommended before sysprep:

  "…
  Before Running Sysprep
  Other steps to consider are:

  Run Chkdsk /f /p prior to imaging
  Defrag the drive
  Make sure 2gb of disk space is free or the NTFSresize will fail
  Make sure the FOG service is installed and properly configured
  Update your hostnamechange.dll file
  …
  "
  https://wiki.fogproject.org/wiki/index.php/Client_Setup

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184 Topics

  825 Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  T

  @Cpasjuste if you have github you likely have ability to have copilot to help read the repo and help you build the README if you find it lacking.

  Just thoughts, but thanks for this.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  V

  Hello everyone,

  I am currently testing the FOG Project working-1.6 branch on a fresh installation of Debian 13 (Trixie) and encountered a fatal error during the installation script. I wanted to share the bug and a proposed fix.

  The Issue

  During the package installation phase, the installer fails with the following error:

  Installing package: sysv-rc-conf............................Failed! (Will try later) ... sysv-rc-conf:amd64=0.99-10 is selected for install sysv-rc-conf:amd64 Depends on sysvinit-core

  Because Debian 13 uses systemd, trying to install sysv-rc-conf forces the package manager to attempt installing sysvinit-core, which conflicts directly with systemd-sysv. The OS prevents this to avoid breaking the system, causing the FOG installation to halt.

  The Cause

  In /lib/ubuntu/config.sh, the variable sysvrcconf is hardcoded for all Debian versions:

  bash if [[ $linuxReleaseName_lower == +(*bian*) ]]; then sysvrcconf="sysv-rc-conf"

  Proposed Fix

  Since sysv-rc-conf is completely obsolete on modern Debian systems, we should exclude it for Debian 13 (and newer). I modified /lib/ubuntu/config.sh on my machine as follows, which allowed the installation to finish successfully:

  if [[ $linuxReleaseName_lower == +(*bian*) ]]; then # Exclude sysv-rc-conf for Debian 13 and newer if [[ "$OSVersion" -ge 13 ]] 2>/dev/null; then sysvrcconf="" else sysvrcconf="sysv-rc-conf" fi elif [[ $linuxReleaseName_lower == +(*ubuntu*|*mint*) ]]; then

  I hope this helps anyone else trying to deploy FOG on the upcoming Debian releases, and perhaps this check could be merged into the repository for future compatibility.

  Thanks for all the great work on FOG!