I would recommend finding the lines in the client logs that show the action running (search on the action ID) and see what exit code was given. Typically its something like 3010 indicating a soft reboot is needed. A pending restart would make the fixlet be deemed as “Fixed” until the restart has occurred.
If the system is missing a recent SSU then that patch may fail to install. As @JasonWalker suggests, you need to also check the Windows event logs as the underlying installation is done by the Windows Update Agent and any issues or CBS corruption that impeded the file rename operations that occur after the reboot could trigger a rollback which then makes the fixlet applicable again.
Incidentally, you only need to apply the most recent CU, so the Feb one in your case. Trying to install both Jan and Feb CU is wasted cycles.