I did some setting of FBWF after enabling it. Then, I restarted the Windows and did some DELETION and copying at some FBWF-protected and write-through folders. After I restarted the system, I got SCREEN of unsuccessful startup as attached file. How come. The setting I did to the system is:
   fbwfmgr /enable
   fbwfmgr /addvolume C:
   fbwfmgr /addexclusion c: %WTHRU_DIR%
   fbwfmgr /addexclusion c: %WORK_DIR_P%

What I did to the files/folders at each restarting cycle is as follows:
      del /s /f /q %WTHRU_DIR%
      call :isempty %WTHRU_DIR%
      if !errorlevel! neq 0    (
         echo "write-through" deleted failed
            echo write-through delete fail >> %LOGFILE%
         GOTO :failure_exit
      )
      del /s /f /q %WPROT_DIR%
      call :isempty %WPROT_DIR%
      if !errorlevel! neq 0    (
         echo "write-protected" deleted failed
            echo write-protect delete fail >> %LOGFILE%
         goto :failure_exit
      )
      call :cpdir %REF_DIR%    %WTHRU_DIR%
      call :cmpdir %REF_DIR%    %WTHRU_DIR%
      if !errorlevel! neq 0    (
         echo "write-through" copy failed
            echo write-through copy fail >> %LOGFILE%
         goto :failure_exit
      )

Is it normal to have such successful startup screen after such operations to FBWF-enabled system?

[recovering disk space, attachment deleted by admin]An FAE of Microsoft's agent gave me the answer and it's approved by me:
The file bootstat.dat in \Windows folder was set protected, but it must be updated to record the last boot state. When it can't be updated for any reason, it causes abnormal startup screen. This was stated in Microsoft web: http://msdn.microsoft.com/en-us/library/aa940810%28v=winembedded.5%29.aspx