Software center "recently installed software requires a computer restart"

Question

I've no idea why I'm getting this message in the notification area. 
This message shows up a few mins after I have deployed an operating system task sequence to a laptop thin client (that uses File Based Write Filter). 
This message doesn't appear to pop-up if I have the write filter disabled. but when it's
enabled, the message comes up as described below.
If I open up Software Center, there is nothing showing anywhere, so I've no idea what is being deployed or causing this message to come up. I reboot and it goes into Service Mode, then eventually reboots and back into normal mode. 
How exactly can I tell what's going on? 

Answer 1

Did you ever figure out an answer to Service Mode right after an OSD task sequence?  I'm having the same issue myself and thought I'd check.  Thanks.
Did you ever figure out an answer to Service Mode right after an OSD task sequence?  I'm having the same issue myself and thought I'd check.  Thanks.
What I found was that the systems would go into service mode some point after re-imaging and I wasn't sure why. 
What I think has been helping so far is doing the following:
1. For FBWF settings, add the following to your file-based write filter (I've done this for HP MT41 systems running WES7. 
cmd /c fbwfmgr.exe /setthreshold 256
cmd /c fbwfmgr.exe /setpreallocation 1
cmd /c fbwfmgr.exe /setcompression 0
2. Within SCCM, make sure you have a collection created for the device you don't want to go into service mode, and ensure that the collection has as many queries as possible to ensure that the device gets put in the collection as soon as possible. 
3. On said collection, in its properties, set a maintenance window for a day of the past (like 12/2/2014 or something), and choose "NONE" for recurrence. 
I believe the above should get rid of the system going into service mode, so far a few weeks it's fixed that for me. 
Before, my systems would go into service mode, the software center would be up saying a reboot was in order, with the 15 minute or so timer on the screen, even with Windows Update completely disabled, and the file based write filter icon would be yellow.
I'd check Software Center from the Programs menu, and there was NOTHING in there. 
I checked the File Based Write Filter and there was nothing in the overlay to be committed. 
So when I checked SCCM and looked up the device that was in service mode, I used the powershell right-click tools to retrieve all Collections that the laptop was a member of, and it was not a member of the collection that had a past maintenance window, but
it was a collection of "All Systems" and "All Desktop and Server Clients", both of which had OSD Task sequences deployed to them. 
So, I'm lead to believe that, even though the Task Sequences deployed are only available via Media and PXE, that Windows Embedded systems have have a glitch where will still get the deployment signal, or it will have to disable the file-based-write-filter
(hence going into "service mode") and do nothing while it figures out how to handle the deployment. That's just a theory but I'm not sure what else to conclude.