pfix v2.7 Released

This version is now deprecated, consult the downloads page for a link to the latest version.

The changes I introduced in pfix v2.4 to reduce execution time (touching /S/L/E when pfix was targeting the root partition and kextd was running instead of forced regeneration of system caches with kextcache utility) apparently causes a problem for a small number of users. From what I have been able to find out this problem only seems to effect people running with a patched (non-vanilla) kernel. There is also the potential that this may effect people who are having issues with their running kextd process for one reason or another. Despite the fact that this problem would effect only a small number of pfix users the reduced execution time (30-90 seconds) is not worth it if pfix does not work for 100% of all users. So pfix will be reverted to manually regenerating system kext caches like it did in pfix v2.3 but the other improvements and enhancements found in pfix v2.6 will not be altered.



  • Bugfix: System kext caches regeneration has been reverted to forced kextcache method.


  • – Added feature which displays numbered menu instead of requiring user to type in volume manually.
  • – User is now prompted for password (if not already authorized with sudo) prior to script execution.


  • Bugfix: Corrected kextd test, if pfix is targeting a mounted volume and not the root [/] partition system caches will be rebuilt with kextcache.


  • – When running under OS X 10.6.x pfix now tests to see if kextd is running, if so it touches /S/L/E instead of rebuilding system caches with kextcache. This significantly reduces execution time.
  • – Repairing permissions with diskutil is now optional.
  • – Minor improvements to terminal output.


  • -If target is a mounted volume execute command to enable permissions on the volume prior to running pfix.


  • -A number of alterations/additions were made to enable proper functionality of pfix when it is launched from a USB Installer or Installation DVD.
  • -Log file is no longer written to disk, the log is displayed directly in the terminal window instead. This better informs the end user of what is happening and also prevents any errors from occurring if it is launched from a read-only location such as a USB Installer or Installation DVD.
  • -Improvements made to visual appearance of log.
  • -pfix version info now displayed in terminal before running any operations.


  • -Revised function to move CustomExtensions to Extensions to ensure smooth bug-free operation.
  • -pfix version now echoed to log file and terminal.


  • Bugfix: Corrected syntax error on kextcache command under Leopard.
  • Bugfix: Corrected minor error that could sometimes cause pfix.log to not be created.
  • -pfix.log now written to root [/] partition of the system it has been run on.
  • -Changed verbosity level of kextcache to 2 for additional useful information to be written to log.
  • -All kext caches are now removed prior to rebuilding.
  • -Minor alterations to output for additional clarity.


You may review the full v2.x release notes here.

6 thoughts on “pfix v2.7 Released

  1. Conti, thank you for your reply to my question a few weeks back. To refresh, I was able to use your MyHack 1.0 RC5 to get the OSX 10.6 installed on my hard drive. When rebooting through the usb, and then sellecting the newly installed partition with SL on it, my system hung on the rotating gear. I checked to make sure the target drive was in the first SATA possition which it was. I tried your next two installers RC5.1 and RC5.2 revisions and they both failed to boot up at all from usb. I went back to RC5 and am again stuck as described above. Please advise me how I would and should proceed to narrow down my possible sticking points. Thanks

    Mike D

    • Mike Deml: Boot with -v at the chameleon prompt and try to take a picture of the output wherever it hangs. My guess is that it’s “still waiting for root device”. If so, correct by ensuring your SATA hard drive is on one of the first two SATA ports on your motherboard and your SATA controller is set to AHCI mode in the bios.

  2. Hey Conti :

    When Pfix asks if I want diskutil to run repairPermissions should I say yes or no ?

    Thanks !

    • Steve: Yes, unless you are playing with kexts and just want to do a quick build – that is why it’s optional, if you are rebooting and running pfix 10 times in a row to test different kexts there is no point in spending the time repairing all permissions on the entire hard drive each time – just do it the last time.

  3. wow, you sure are cranking out these pfix builds. Great to know you’re still on top of things Conti, thanks ^_^